[OASIS Issue Tracker] Commented: (CMIS-223) Direct inclusion of theschema in the spec is cuase for duplication, confusion

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

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

Al Brown commented on CMIS-223:
-------------------------------

The XSD is a way of describing the XML format.  I do not think it hinders us.  If you look at the browser binding, json, it leverages a different format (JSON) .  I do not believe having xsd's normative in p1 caused that proposal any trouble.

I am also not sure moving the schema out of p1 to p1.5 and then creating a dependency on rest/atompub and ws bindings on p1 and p1.5 does anything really useful.

We can always change it in a future version.

Do you see problems today with the schema in p1?

> Direct inclusion of the schema in the spec is cuase for duplication, confusion
> ------------------------------------------------------------------------------
>
>                 Key: CMIS-223
>                 URL: http://tools.oasis-open.org/issues/browse/CMIS-223
>             Project: OASIS Content Management Interoperability Services (CMIS) TC
>          Issue Type: Bug
>          Components: Domain Model
>    Affects Versions: Draft 0.62
>            Reporter: Ryan McVeigh
>            Assignee: Ethan Gur-esh
>
> Line 4505 (elsewhere?) - I noticed that the schema in the spec does not match the schema file included with the zip package (cmisPermissionDefinitionType vs cmisAccessControlPermissionType). Already, things are out of sync due to duplication.
> The presence of schema in the Domain Model and in the Normative section of the Domain Model makes this doucment now much more than a data model.  This also seems to llimit (or make severely difficult) the ability to define non-xml (or non-xsd) based bindings.
> Also, there are several cases where the spec calls out, for example, valid values for a property. Then that very same information is again called out in xsd format. Seems that if the spec says what the valid values are, that should be enough, and the xsd shouldn't be needed to further specify this.

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