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

URL to id mapping

    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

      Add uritemplate to workspace element as defined below:

      <xs:simpleType name="enumUriTemplateType">
      <xs:restriction base="xs:string">
      <xs:enumeration value="entrybyid" />
      <xs:enumeration value="folderbypath" />
      <xs:enumeration value="query" />
      <xs:enumeration value="other" />
      </xs:restriction>
      </xs:simpleType>

      <xs:complexType name="cmisUriTemplateType">
      <xs:sequence>
      <xs:element name="template" type="xs:string" />
      <xs:element name="type" type="cmisra:enumUriTemplateType" />
      <xs:element name="format" type="xs:string" />
      <!-- extension -->
      <xs:any processContents="lax" namespace="##other" minOccurs="0"
      maxOccurs="unbounded" />
      </xs:sequence>
      </xs:complexType>
      <xs:element name="uritemplate" type="cmisra:cmisUriTemplateType" />

      Example:
      <uritemplate>
      <template>http://www.example.com/id/

      {rep}

      /

      {objectid}

      </template>
      <type>entrybyid</type>
      <format>application/atom+xml;type=entry</format>
      </uritemplate>

      Define in the rest binding each type of uri template provided by ecm. include the variables for each template. If uri templates are not included in the workspace element then uri templates are not available by the implementation.

      This does not impact the ws binding.

      Show
      Add uritemplate to workspace element as defined below: <xs:simpleType name="enumUriTemplateType"> <xs:restriction base="xs:string"> <xs:enumeration value="entrybyid" /> <xs:enumeration value="folderbypath" /> <xs:enumeration value="query" /> <xs:enumeration value="other" /> </xs:restriction> </xs:simpleType> <xs:complexType name="cmisUriTemplateType"> <xs:sequence> <xs:element name="template" type="xs:string" /> <xs:element name="type" type="cmisra:enumUriTemplateType" /> <xs:element name="format" type="xs:string" /> <!-- extension --> <xs:any processContents="lax" namespace="##other" minOccurs="0" maxOccurs="unbounded" /> </xs:sequence> </xs:complexType> <xs:element name="uritemplate" type="cmisra:cmisUriTemplateType" /> Example: <uritemplate> <template> http://www.example.com/id/ {rep} / {objectid} </template> <type>entrybyid</type> <format>application/atom+xml;type=entry</format> </uritemplate> Define in the rest binding each type of uri template provided by ecm. include the variables for each template. If uri templates are not included in the workspace element then uri templates are not available by the implementation. This does not impact the ws binding.

      Description

      reported in various discussions during the PlugFest in Basel, my interpretation may be off.

      Currently there is no way to map document and folder ids to urls on the client side.
      This will either lead to a large number of additional roundtrips or to very stateful clients
      that rely on the stability of that mapping (which i am not sure if this would be legal).

      So it would be great if there was a simple mapping from id's to URLs for both folders and
      documents.

        Attachments

          Activity

            People

            • Assignee:
              albertcbrown Al Brown (Inactive)
              Reporter:
              david@day.com David Nuescheler (Inactive)
            • Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: