[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (CMIS-102) Clarify therepositoryRelationship attribute on a workspace.
[ http://tools.oasis-open.org/issues/browse/CMIS-102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=10224#action_10224 ]
Al Brown commented on CMIS-102:
-------------------------------
Clarified in 61
> Clarify the repositoryRelationship attribute on a workspace.
> ------------------------------------------------------------
>
> Key: CMIS-102
> URL: http://tools.oasis-open.org/issues/browse/CMIS-102
> Project: OASIS Content Management Interoperability Services (CMIS) TC
> Issue Type: Bug
> Components: REST/AtomPub Binding
> Affects Versions: Draft 0.50
> Reporter: Ryan McVeigh
> Assignee: Ethan Gur-esh
> Priority: Minor
> Fix For: Draft 0.61
>
>
> In the description of the Atom Service Document (REST) it says that the workspace will have a cmis attribute for repositoryRelationship. This is an enum, and its values are described in part 1 in the enums table (self, replica, peer, parent, child, archive). This seems to be described (vaguely) in part 1, page 19 where it says the relationship "MAY" be returned, and the name is opaque to cmis, and it gives some "suggested/example values". So if the values are opaque and suggested and optional, why does the REST Service document require it and constrain the value in an enum?
--
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]