Details

    • Proposal:
      Hide

      Repository info URL: repository specific
      (Repository info provides <rootFolderUrl> and <unfiledUrl>.)

      Referencing an object by path: <rootFolderUrl>/<path>
      Example: http://myrepository/cmis/repository/123/myFolder/myDocument

      Referencing an object by id: <rootFolderUrl>?objectId=<id>
      Example: http://myrepository/cmis/repository/123?objectId=0192018282
      or
      Referencing an object by id: <unfiledUrl>?objectId=<id>
      Example: http://myrepository/cmis/repository/123-unfiled?objectId=0192018282

      All read operations (without side effects) MUST be use HTTP GET. In order to tell the repository which operation should be performed, a parameter "selector" is added to the URL.

      Examples:
      GET /cmis/repository/123/myFolder/myDocument?selector=object
      GET /cmis/repository/123?objectId=0192018282&selector=object
      GET /cmis/repository/123/myFolder/myDocument?selector=content
      GET /cmis/repository/123/myFolder/myOtherFolder?selector=children
      GET /cmis/repository/123/myFolder/ myOtherFolder?selector=descendants

      If the "selector" parameter is absent, the following operations are performed:

      • For documents: getContentStream
      • For folders: getChildren
      • For relationships: getObject
      • For policies: getObject

      All other operations MUST use HTTP POST. Instead of a "selector" parameter an "action" parameter MUST be passed. (There is no default.)

      Examples:
      POST /cmis/repository/123/myFolder/myDocument?action=delete
      POST /cmis/repository/123?objectId=0192018282&action=update
      POST /cmis/repository/123?objectId=0192018282&action=checkin
      POST /cmis/repository/123/myFolder/myOtherFolder?action=create

      Show
      Repository info URL: repository specific (Repository info provides <rootFolderUrl> and <unfiledUrl>.) Referencing an object by path: <rootFolderUrl>/<path> Example: http://myrepository/cmis/repository/123/myFolder/myDocument Referencing an object by id: <rootFolderUrl>?objectId=<id> Example: http://myrepository/cmis/repository/123?objectId=0192018282 or Referencing an object by id: <unfiledUrl>?objectId=<id> Example: http://myrepository/cmis/repository/123-unfiled?objectId=0192018282 All read operations (without side effects) MUST be use HTTP GET. In order to tell the repository which operation should be performed, a parameter "selector" is added to the URL. Examples: GET /cmis/repository/123/myFolder/myDocument?selector=object GET /cmis/repository/123?objectId=0192018282&selector=object GET /cmis/repository/123/myFolder/myDocument?selector=content GET /cmis/repository/123/myFolder/myOtherFolder?selector=children GET /cmis/repository/123/myFolder/ myOtherFolder?selector=descendants If the "selector" parameter is absent, the following operations are performed: For documents: getContentStream For folders: getChildren For relationships: getObject For policies: getObject All other operations MUST use HTTP POST. Instead of a "selector" parameter an "action" parameter MUST be passed. (There is no default.) Examples: POST /cmis/repository/123/myFolder/myDocument?action=delete POST /cmis/repository/123?objectId=0192018282&action=update POST /cmis/repository/123?objectId=0192018282&action=checkin POST /cmis/repository/123/myFolder/myOtherFolder?action=create
    • Resolution:
      Hide

      included in schema proposal 0.2

      Show
      included in schema proposal 0.2

      Description

      In order to keep browser binding clients as simple as possible we should introduce fixed URL patterns.

        Attachments

          Activity

            People

            • Assignee:
              melahn Gregory Melahn (Inactive)
              Reporter:
              fmueller Florian Müller (Inactive)
            • Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: