Application Scenario ID is overloaded and maybe overspecified

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Major
    • None
    • Affects Version/s: Working Draft
    • None
    • Environment:

      This issue apples to wd4

    • Hide

      NEEDS DISCUSSION, but:

      Make the ID be an identifier that is appropriate for inclusion of the Application Scenario in a registry or catalog and being locatable via that ID. This need not be descriptive, but it should be relatively easy to use (like JIRA issues, for example).

      Add Application Scenario ID to the terminology/nomenclature if appropriate.

      Consider what the ID must be unique relative to. Can this be described without saying who has the authority over assignment of IDs? (I suggest that this be indirect. See separate issue on this.)

      Separate Submitter as an information unit distinct from ID. Add Submitter to the terminology/nomenclature. I suggest that the authority of the submitter to make a submission to a particular collection of application scenarios is one reason for having an identified individual or organization. (In the case of the OIC, the IPR requirements require submissions from individuals via the two avenues for that. I suppose other arrangements could be made, probably via OASIS officials.)

      Show
      NEEDS DISCUSSION, but: Make the ID be an identifier that is appropriate for inclusion of the Application Scenario in a registry or catalog and being locatable via that ID. This need not be descriptive, but it should be relatively easy to use (like JIRA issues, for example). Add Application Scenario ID to the terminology/nomenclature if appropriate. Consider what the ID must be unique relative to. Can this be described without saying who has the authority over assignment of IDs? (I suggest that this be indirect. See separate issue on this.) Separate Submitter as an information unit distinct from ID. Add Submitter to the terminology/nomenclature. I suggest that the authority of the submitter to make a submission to a particular collection of application scenarios is one reason for having an identified individual or organization. (In the case of the OIC, the IPR requirements require submissions from individuals via the two avenues for that. I suppose other arrangements could be made, probably via OASIS officials.)

      In Section 3.1, the ID concept is collapsed with the concept of submitter.

      These concepts should be separated.

      Also, the means of identifying a submitter is perhaps over-specified. (E.g., the use of underscore, no provision for name disambiguation, and the cultural and internationalization assumptions that are latent in the assumptions about the form of names).

            Assignee:
            Bart Hanssens (Inactive)
            Reporter:
            Dennis Hamilton (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated: