[sc34wg3] Draft Reference Model

Ann Wrightson sc34wg3@isotopicmaps.org
Fri, 29 Nov 2002 08:32:15 -0000

Hi folks - good to see a more detailed RM draft coming out well in time
for Baltimore (ref previous UK comments).


Steve Newcomb said:

... the RM's graph construction rules,
which guarantee that, whenever two topic map graphs are
merged, each of the original topic map graphs is an
unchanged subgraph of the resulting merged graph.  That
way, anybody who knew either of the original graphs
will find the merged result at least as usable as the
originals were.=20

These are mathematical properties, IMO, and must be tested
mathematically, as well as in the rhetorical processes of this list. An
exact interpretation will be needed for  "at least as usable as the
originals", I guess in terms of similarity of results of similar
I share Bernard's concern about the kind of graph we end up with,
because an ISO standard is for everyone, not just for current
implementers. It would be good to be able to use established
mathematical techniques to gain assurance that the RM graph has nice
rather than nasty properties for future implementers.
I'm looking forward v much to Bernard's presentation at Baltimore -
please let it have enough space, as it could be one of the most
important things there.

Ann W.

HEDRA Limited=20
Registered Offices: Craven House, West Street, Farnham, Surrey, GU9 7ES=20
Tel.  01252 719000=20
Fax   01252 719111=20
Web   http://www.hedra.com=20
Registered in England number 2491619=20
VAT registration number 537 7047 30=20
This email and any files transmitted with it are confidential and=20
intended solely for the use of the individual or entity to whom=20
they are addressed.  If you have received this email in error please=20
notify the sender and delete the original message from your system.=20

This email and any attachments to it have been checked for viruses.=20
However, you should verify that both the email and any attachments to it =

are virus free and the sender accepts no responsibility for any damage=20
which may be caused by the inadvertent transmission of executable code.=20