wd19 .doc Use of the term 'optional'.

XMLWordPrintable

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Minor
    • wd23
    • Affects Version/s: None
    • Component/s: spec
    • None
    • Environment:

      Anne Hendry

    • Hide

      Strike the sentence "A Sequence may optionally include a Lineage."
      Either remove the term 'optional' from tables, use a different term,
      or put in conformance section (rules). Strike line 300 or use differnt term.
      Cardinality/multiplicity will show up in UML, etc.

      Show
      Strike the sentence "A Sequence may optionally include a Lineage." Either remove the term 'optional' from tables, use a different term, or put in conformance section (rules). Strike line 300 or use differnt term. Cardinality/multiplicity will show up in UML, etc.
    • Hide

      Removed almost all instances of reserved word optional from the specification. Directed the reader to the schema for all issues of cardinality, including cardinality of 0..

      Show
      Removed almost all instances of reserved word optional from the specification. Directed the reader to the schema for all issues of cardinality, including cardinality of 0..

      Line 300
      "All elements in the tables not marked as 'optional' are mandatory" ...

      'OPTIONAL' is an RFC2119 keyword (used instead of 'MAY') for conformance clauses.
      'mandatory' is not an RFC2119 keyword.

      In tables 5-9, 5-10, 7-17, 10-26, 11-27 is 'optional' intended to specify
      conformance or to indicate a cardinality/multiplicity ('0..x')?
      Further confused by using the word 'optionally' in
      Table 13-29 "A Sequence may optionally include a Lineage."
      but 'Lineage' (Table 13-30) definition does not state it is 'optional'.

            Assignee:
            Toby Considine (Inactive)
            Reporter:
            Anne Hendry (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: