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 |
REPLY TO: |
Dr. James David Mason (ISO/IEC JTC 1/SC 34 Secretariat - Standards Council of Canada) Crane Softwrights Ltd. Box 266, Kars, ON K0A-2E0 CANADA Telephone: +1 613 489-0999 Facsimile: +1 613 489-0995 Network: jtc1sc34@scc.ca http://www.jtc1sc34.org |
VariantSchema
oneOf -> delete
InternalOccurrenceSchema
minExclusive -> looks like it is complex -> should be deleted
* . Merge Internal and External Occurrence into one structure
Association
Discussion of SchemaID -> let's have it
AssopciationSignature is too complicated, it promotes bad ontology. delete Association signature
RoleSchema
OneOf requires additional investigation
ExistsAtLeast
Investigate integration with TMQL, clarify scope matching
Introspection
Delete section. TMCL-Schema will have standard Topic Map-based representation. Introspection will be achievable using regular TMQL.
TopicMapSchema
Notification is useful concept but current approach is too heavy.
Alternatives:
Diagnostic Item
It should exists at syntax level only
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
ConflictItem, NotificationItem
Consider to have only one type of ConflictItems with additional attributes, such as mode