This calls for great precision and agreement which I suspect we do not yet
have. (It also arises in the PubID vs SysID question).
I suspect there are two strategies:
- accept it as a very difficult problem and not attempt to solve it. The
community (market) will then come up with approaches which may or may not
find ecological niches
- accept it as a very difficult problem and propose a solution. Some of
the community will accept this and some won't.
I would suggest that we only address the mechanism whereby prefix is linked
to ns. And that in a minimalist manner (i.e. providing Names for these
beasties). *What* ns should refer to is beyond XML-DEV at present (though
it may be a very appropriate forum in the future).
FWIW I will adopt a very simple strategy for JUMBO. I will not use ns to do
other than to give me a unique string, thus:
<?xml:namespace ns="xml-cml.org" prefix="CML" ?>
The ns value is unique within the galaxy. I then resolve it with a
JUMBO-specific PI:
<?JUMBO ns="xml-cml.org" java="jumbo.cml"?>
This will *implicitly* link any CML element to a class:
<CML:MOL> links to jumbo.cml.MOLNode
(JUMBO will have the convention that <FOO> links to FOONode). These classes
will be stored under the classpath (using the tools that you have all
helpfully told me about recently).
I will also store the CML XSchema in the same area. Whether XSchema need to
give me a handle for this I don't know (I shan't use 'src'). *** This
brings up the question of what the XSchema file is called ***. Do we name
it after the 'root' element? Thus:
- what is the XSchema for CML called (a) if there is a <!ELEMENT CML ...>
(b) if there isn't?
- what mechanism might there be for locating the XSchema file?
P.
Peter Murray-Rust, Director Virtual School of Molecular Sciences, domestic
net connection
VSMS http://www.nottingham.ac.uk/vsms, Virtual Hyperglossary
http://www.venus.co.uk/vhg