Need to include the rationale/use cases for the various names uses for types and properrty defintions

XMLWordPrintable

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

      Applies to both type and property definitions:
      id "1 - Opaque/Unique
      2 - used for service calls; if property, id is used instead of name
      3 - specified for base object types and properties used in cmis specification"

      Name "1 - <Native repository name>
      2 - remove prefix support; e.g., field is opaque
      3 - no unique requirements by CMIS"

      namespace Optional

      queryName sql-92 compliance

      displayName User friendly name for editing UI

      • BaseTypeName property -> BaseTypeId (and any other field that refers to names)
      • Query & filter use queryName
      • Specification specifies id and queryName
      Show
      Applies to both type and property definitions: id "1 - Opaque/Unique 2 - used for service calls; if property, id is used instead of name 3 - specified for base object types and properties used in cmis specification" Name "1 - <Native repository name> 2 - remove prefix support; e.g., field is opaque 3 - no unique requirements by CMIS" namespace Optional queryName sql-92 compliance displayName User friendly name for editing UI BaseTypeName property -> BaseTypeId (and any other field that refers to names) Query & filter use queryName Specification specifies id and queryName

      As it currently stands there are no fewer than 4 names specified for types - name, queryName, displayName and globalUniqueName. This is confusing to those folks who know the spec, nevermind the newcomer. We need to document why we have these and describe what they help address.

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

              Created:
              Updated:
              Resolved: