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] Commented: (CMIS-164) Usage of <content>across multiple implementations



    [ http://tools.oasis-open.org/issues/browse/CMIS-164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=10676#action_10676 ] 

Ethan Gur-esh commented on CMIS-164:
------------------------------------

TC review -- accepted.

> Usage of <content> across multiple implementations
> --------------------------------------------------
>
>                 Key: CMIS-164
>                 URL: http://tools.oasis-open.org/issues/browse/CMIS-164
>             Project: OASIS Content Management Interoperability Services (CMIS) TC
>          Issue Type: Bug
>          Components: REST/AtomPub Binding
>    Affects Versions: Draft 0.61
>            Reporter: David Nuescheler
>            Assignee: Al Brown
>
> reported by Ugo Cei during the PlugFest in Basel in keywords, so my interpretation may be off.
> Currently there are various different ways on how the implementation refer to the "enclosed" binary.
> Some use the <content> element someuse various link relations, this became particularly apparent when testing
> with various server implementations.
> It seems that the specification could be clear about how to use <content> possibly with an example.

-- 
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]