Feeler for SML (Simple Markup Language)

[Fabio Arciniegas A.]

- ...
-o No non-character entity references
-o No predefined character entities (I am iffy on this one)
- ...

- What do you guys think?

I think It is true that it saves a lot of work (at expenses of some features
that i confess i like, e.g attributes), therefore making it possible to use
smaller, faster parsers. But I would be a bit concerned about
interoperability  issues...

I think that in order to keep things interoperable, it could be an
"optimizing choice" for an application to use an "SML parser". The process
would be something like having the app ready for XML parsing and then when
faced with a PI(? -maybe something else-) stating that this is SML,
switching parsers...
But only as a convinient runtime choice. Implementing an application that
*only* manages SML wouldn't seem convenient to me in many important respects
like interoperability and extensibility...

- ...
-o No Attributes (ouch!)
-o No PI, Comments, Notations, or CDATA sections
-o No document type declaration
-o UTF-8 encoding only
- subject to change later depending on your capacity to scream
convincingly.  The key point to consider is whether there is
a broad enough need for such a subset of XML.


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)