Direct inclusion of the schema in the spec is cuase for duplication, confusion

    • Type: Bug
    • Resolution: Applied
    • Priority: Major
    • None
    • Affects Version/s: None
    • Component/s: Domain Model
    • None
    • Hide

      remove snippets

      Show
      remove snippets

      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.

            Assignee:
            Ryan McVeigh (Inactive)
            Reporter:
            Ryan McVeigh (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: