ISO/IEC JTC 1/SC 34N0645

ISO/IEC logo


Information Technology --
Document Description and Processing Languages

TITLE: Amsterdam 2005 meeting notes for CD 19756: Topic Maps -- Constraint Language
SOURCE: Mr. Steve Pepper
PROJECT: CD 19756: Information Technology - Topic Maps - Constraint Language (TMCL)
PROJECT EDITOR: Mr. Dmitry Bogachev; Mr. Graham Moore; Ms. Mary Nishikawa
STATUS: Meeting notes
ACTION: For information
DATE: 2005-05-26
DISTRIBUTION: SC34 and Liaisons

Dr. James David Mason
(ISO/IEC JTC 1/SC 34 Chairman)
Y-12 National Security Complex
Bldg. 9113, M.S. 8208
Oak Ridge, TN 37831-8208 U.S.A.
Telephone: +1 865 574-6973
Facsimile: +1 865 574-1896
Network: [email protected]

Mr. G. Ken Holman
(ISO/IEC JTC 1/SC 34 Secretariat - Standards Council of Canada)
Crane Softwrights Ltd.
Box 266,
Telephone: +1 613 489-0999
Facsimile: +1 613 489-0995
Network: [email protected]

TMCL Comments

TMCL Schema comments

  1. TMCL should provide ability to specify exceptions when we use "for every X" construct.
  2. Schema has "include" property now. Should it be in TMCL model or outside (syntax only)?
  3. TopicIdentification. Add constraint that only one topic should be returned.
  4. ScopePattern. Clarify relationship with TMDM implementation
  5. SchemaID. Clarify what is that. Also clarify how we find parent of a schema item.
  6. Clarify in schema description what is a selector and what is a constraint. For exaample, type, scope, association template are selectors. Need clear notation for expressing this as well as description in prose.
  7. BaseNameSchema
    1. dataType -> delete
    2. oneOf -> delete
  8. VariantSchema

    oneOf -> delete

  9. InternalOccurrenceSchema

    minExclusive -> looks like it is complex -> should be deleted

    * . Merge Internal and External Occurrence into one structure

  10. OneOfSchema -> replace with topicset as property
  11. PlayRoleSchema -> delete otherPlayers
  12. Clarify meaning of a scope in schemas: is it selector or constraint?
  13. Association

    Discussion of SchemaID -> let's have it

    AssopciationSignature is too complicated, it promotes bad ontology. delete Association signature

  14. RoleSchema

    OneOf requires additional investigation

  15. ExistsAtLeast

    Investigate integration with TMQL, clarify scope matching

  16. Introspection

    Delete section. TMCL-Schema will have standard Topic Map-based representation. Introspection will be achievable using regular TMQL.

  17. TMCL-Rules comments

  1. TopicMapSchema

    Notification is useful concept but current approach is too heavy.


    1. Topic Map Schema level
    2. Topic Schema + modes
    3. pattern + modes
  2. Diagnostic Item

    It should exists at syntax level only

  3. ContextItem

    Requires simplification.

    Replace ContextItem with expression with free variables. It is a selector.

    Consider to look at message section as "return" section in TMQL.

    In this case it can return XML, strings and Topic Maps

  4. ConflictItem, NotificationItem

    Consider to have only one type of ConflictItems with additional attributes, such as mode

Additional constraints

  1. Add super-type - sub-type constraints (as constraints, not facts)
  2. Add uniqueness constraints for names, occurrence and associations. Example: capital should be unique
  3. Add reification constraints
  4. Ignore idea of external resources constraints.
  5. Add disjoint constraint.
  6. Investigate "Same subject" constraint
  7. Describe schema->model>schema transformation
  8. Add section "Detecting schema conflicts"

Main tasks for next draft

  1. Port Schemas to UML and Infoset
  2. Provide formal schema interpretation based on basic constraints