[OASIS Issue Tracker] Created: (CMIS-59) MergeenumRelationshipDirection and enumIncludeRelationships, remove "none"

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

Merge enumRelationshipDirection and enumIncludeRelationships, remove "none"
---------------------------------------------------------------------------

                 Key: CMIS-59
                 URL: http://tools.oasis-open.org/issues/browse/CMIS-59
             Project: OASIS Content Management Interoperability Services TC
          Issue Type: Improvement
            Reporter: Florent Guillaume


Contingent to CMIS-41 being resolved in favor of keeping enumIncludeRelationships, then I propose that it and enumRelationshipDirection be merged into one enum with values: "source", "target" and "either".
The value "none" of enumIncludeRelationships is redundant because the attribute includeRelationships is always nillable in the schemas.

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