[topicmapmail] Announcement of XML Schema for ISO13250Topic Maps

[David RR Webber]

Patrick,

After all the tour around the block, I'm not sure that we
really disagree that much here!

The relevant points seem to be.

a) there are several classes/ communities of users, separated by
     their varying needs to interact with topicmap
     semantics.

b) ensuring interoperability between different vendors requires
     automated mechanisms that the average user just uses
     without being aware of the underpinning.

c) in b) above the developer community does need access to
     the underpinning in some way (angle bracket / and / or UI) 
     in order to configure and maintain.

d) exposing the topicmap semantics via UI can be needed 
     for business processes to succeed - particularly 
     knowing context.

e) Knowledge workers should not have to be experts in 
     topicmap semantics.

f) item b) above requires consistent use of XML syntax to
   deliver via as plain vanilla use of XML parser 
   built-in mechanisms as possible.

There's probably a few more points but this seems to 
be a good first wash.

The key thing is ensuring that what we architect delivers
on all this.

Thanks, DW.