Feeling good about SML

[Bill dehOra]

Don,

Suggestions:

First define the environment, or domain, that SML is targeted for. Inversely
one could define what XML isn't for. Then rephrase all specifications in
terms of the domain, mentioning XML if necessary. This may allow specs to
become more operational and verifiable. Possibly:

1. SML shall be targeted for the following domains: [TBD]
2. SML shall be a simplified subset of XML.
3. SML shall have no optional features.
4. SML shall be designed with ease of implementation in mind.
5. XML implementations shall understand SML. (implicit by 2?)


Regards,

Bill de hOra



        

xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev at ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To unsubscribe, mailto:majordomo at ic.ac.uk the following message;
unsubscribe xml-dev
To subscribe to the digests, mailto:majordomo at ic.ac.uk the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa at ic.ac.uk)