|
If you were logged in you would be able to see more operations.
|
|
|
| Proposal: |
Feed returned is comprised ofatom entries that contain only the cmis property bag. Only the bare minimum atom entry links and fields are required to be set. If the query is non join and an underlying object is identifiable for the property bag, then a repository MAY include a full representation of that atom entry.
Feed returned is comprised ofatom entries that contain only the cmis property bag. Only the bare minimum atom entry links and fields are required to be set. If the query is non join and an underlying object is identifiable for the property bag, then a repository MAY include a full representation of that atom entry.
|
|
The Query response example in part II (AtomPub) implies cmis:object is rendered for documents matching query criteria (there's a comment in the example). This mapping is probably ok for queries without join, as the implication is that objects of a single type are queried.
However, queries with joins don't map well to object oriented result sets.
It seems we're missing a row/col mapping. In fact, this may be the primary mapping (with an optional injected cmis:object, or link to object where applicable).
We may also want to consider including inline query meta-data, or a link to query meta-data.
|
|
Description
|
The Query response example in part II (AtomPub) implies cmis:object is rendered for documents matching query criteria (there's a comment in the example). This mapping is probably ok for queries without join, as the implication is that objects of a single type are queried.
However, queries with joins don't map well to object oriented result sets.
It seems we're missing a row/col mapping. In fact, this may be the primary mapping (with an optional injected cmis:object, or link to object where applicable).
We may also want to consider including inline query meta-data, or a link to query meta-data. |
Show » |
|
Bug
Closed
Major
Query result set AtomPub binding is ambiguous and implies object mapping, not row mapping
That would be consistent with what is there, just more text in the document is required to explain the behavior.