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

cmisra:content vs base64 inconsistency

    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

      Update 3.4.1.3.6 with:
      This element specifies the content of the atom:entry element. This element MUST have a cmisra:mediatype and a cmisra:base64 child element.
      This element MUST take precedence over atom:content on submission of an atom entry to a repository. The content of the cmisra:base64 element is base64 encoded and represents the content of the entry. The cmisra:mediatype element specifies the MIME media type of the content of the entry.

      Show
      Update 3.4.1.3.6 with: This element specifies the content of the atom:entry element. This element MUST have a cmisra:mediatype and a cmisra:base64 child element. This element MUST take precedence over atom:content on submission of an atom entry to a repository. The content of the cmisra:base64 element is base64 encoded and represents the content of the entry. The cmisra:mediatype element specifies the MIME media type of the content of the entry.
    • Resolution:
      Hide

      Fixed in 1.0

      Show
      Fixed in 1.0

      Description

      The spec 1.0cd04 says, l.5128:

      3.4.1.3.6 cmisra:content
      This element specifies the content of the atom:entry element. The content is base64 encoded.

      This implies having the base64-encoded content directly inside the cmisra:content element.

      However CMIS-RestAtom.xsd has:

      <xs:element name="content" type="cmisra:cmisContentType"/>
      <xs:complexType name="cmisContentType">
      <xs:sequence>
      <xs:element name="mediatype" type="xs:string" />
      <xs:element name="base64" type="xs:string" />
      <xs:any processContents="lax" namespace="##other" minOccurs="0"
      maxOccurs="unbounded" />
      </xs:sequence>
      </xs:complexType>

      Given that cmisra:content's goal is to override atom:content, it has to be able to do all that atom:content does, in particular define the media type of the content. So the XSD seems the correct choice.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              florent.guillaume Florent Guillaume (Inactive)
            • Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: