[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] nextml: some notes on instance requirements
Heyo. Slightly different perspective. What are the requirements for instance documents, for a 'nextml'? Best Practice: Elliotte Rusty Harold and some others have been focussed on creation of a "profile" or "conformance class" or perhaps "collection of best practices" for XML 1.0. That is, every document in this nextml is a well-formed (and namespace-well-formed) xml 1.0 + namespaces in xml document. It seems to me that this requires no indication in an instance document, although an optional indicator might allow some processors to optimize. Non-breaking change: (for example) Michael Kay has proposed an alternative namespace syntax, that doesn't violate xml 1.0 without namespaces, and that could possibly be transformed into xml 1.0 + namespaces algorithmically. The tag minimization proposals might fit here (except for their tendency to produce ill-formed (well, the equivalent) documents in SGML days, suggesting that transformations would fail more often in these cases). It seems to me that for such cases, where the nextml instance document is well-formed xml 1.0, but would provide less information than it contains to existing xml 1.0 processors, unless a common/standard transformation were first performed, a new PI would be sufficient. Breaking change: several have been proposed in the past few days, from permitting nested comments, to establishing an equivalence between attributes and simple child elements (and more that I haven't remembered). Such instance documents wouldn't be well-formed XML 1.0. The version number in the XML declaration must be changed. It would be easiest to get agreement on a set of best practices (note: I said "easiest;" I didn't say "easy"). It could be done outside of a sponsoring specification organization. It doesn't interest me, much, but it seems to appeal to a number of people here. Non-breaking changes could also be hammered out outside of a specifying organization, and consequently might have a chance of producing results in less than a year. This is the path that looks most interesting to me, at the moment (in part because I think that proving the concept, via non-breaking changes, might encourage more serious consideration of a nextml at W3C). Breaking changes are going to be hardest, take longest, and meet most resistance. Lots of people (and organizations) with a stake already on the table, and with influence in the organization that owns XML specifications. As I said, I don't think that the process is likely to start until there are some interesting "non-breaking" type proofs of concept to encourage W3C. Me, I'd like to see the namespaces problem addressed. I'd *so* much like to see nested comments, but I doubt that we can get those without a spec revision. Amy! -- Amelia A. Lewis amyzing {at} talsever.com Did you exchange a walk-on part in the war for the lead role in a cage? -- Pink Floyd
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] |
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|