Uploaded image for project: 'OASIS Content Management Interoperability Services (CMIS) TC'
  1. OASIS Content Management Interoperability Services (CMIS) TC
  2. CMIS-260

Query XML Document is confusing.

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: REST/AtomPub Binding
    • Labels:
      None
    • Proposal:
      Hide

      Clarify:
      1. If non-join scenario, then the result set must include self + edit link relation. the client must get the self link to retrieve the full representation of the object. implementations MAY include additional information.
      2. the result set returned will be a set of atom entries, one per row, with the cmis object filled with the columns from the select clause contained in a feed.

      Show
      Clarify: 1. If non-join scenario, then the result set must include self + edit link relation. the client must get the self link to retrieve the full representation of the object. implementations MAY include additional information. 2. the result set returned will be a set of atom entries, one per row, with the cmis object filled with the columns from the select clause contained in a feed.

      Description

      The query xml document has an element for repositoryId. However, the way the service document is set up and the fact that some repositories don't support query (or support it differently) makes me assume that the Query collection is expected to be per-repository. So what happens if you post a query document to one repository's query collection, and the document contains a repositoryId for a different repository?

      Proposal: Quit using this WS document for ReST. Query should be a GET, which takes a statement as a query param (with a reasonable default, like "SELECT * FROM Document").

      I realize the query GET issue has come up more than once, but it keeps coming up internally for a reason, and this is another example.

        Attachments

          Activity

            People

            • Assignee:
              albertcbrown Al Brown (Inactive)
              Reporter:
              ryan.mcveigh Ryan McVeigh (Inactive)
            • Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: