OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

cmis message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: [OASIS Issue Tracker] Created: (CMIS-601) cmisra:content vs base64inconsistency

cmisra:content vs base64 inconsistency

                 Key: CMIS-601
                 URL: http://tools.oasis-open.org/issues/browse/CMIS-601
             Project: OASIS Content Management Interoperability Services (CMIS) TC
          Issue Type: Bug
          Components: REST/AtomPub Binding
    Affects Versions: Committee Draft 04
            Reporter: Florent Guillaume
            Assignee: Al Brown

The spec 1.0cd04 says, l.5128: 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:element name="mediatype" type="xs:string" />
                        <xs:element name="base64" type="xs:string" />
                        <xs:any processContents="lax" namespace="##other" minOccurs="0"
                                maxOccurs="unbounded" />

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.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]