Property Definitions: A property definition should not ever say READONLY + REQUIRED

XMLWordPrintable

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Trivial
    • None
    • Affects Version/s: None
    • Component/s: Domain Model
    • None
    • Hide

      The spec should explicitly state that if a property is READONLY, then its definition SHALL NOT say it's required.

      Show
      The spec should explicitly state that if a property is READONLY, then its definition SHALL NOT say it's required.
    • Hide

      We will clarify via use of the word "SHOULD", as per Al's comment on 4/19.

      Show
      We will clarify via use of the word "SHOULD", as per Al's comment on 4/19.

      Currently in the CMIS spec we have the following 2 attributes on a property definition:

      • updateability: Where you can say a property is readonly (i.e. the app can never set it)
      • required: Where you can say that a property is required.

      BUt it's not clear/obvious what it would mean to have a property that is read-only and required... what is an application supposed to do in that situation?

            Assignee:
            Ethan Gur-esh (Inactive)
            Reporter:
            Ethan Gur-esh (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: