OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
Re: [xml-dev] what's missing in XML? What's coming?

True but it also means some new very large, complex and expensive  
documents can not use XSD.  I'm not defending Entity Declarations per  
se, but the combinations of these, character entities and all the  
problems of ensuring these can be handled by the enterprise software  
do become onerous.

A tech pubs world where the XML never sees the web or a browser and  
the documents are long lived and very slow (real publishing) seems to  
be increasingly willing to lag behind.

It may be inevitable that XML becomes not just markup on the web, but  
only markup on the web, meaning it may be time for military technical  
publishing to reconsider it's early adopter commitments to markup.  It  
takes years to create and publish the guidance documents, the XSD is  
barely documented despite being hundreds of pages long, making  
substantial post-validation contributions and creating layouts,  
resolving references, etc. vital to follow-on products (say, Class III  
and IV IETMs).   Enterprises with very large networks of users who are  
also adopting new media distribution devices (say handyPhones) have to  
consider cost benefits.


Quoting Henri Sivonen <hsivonen@iki.fi>:

> On Mon, Jan 2, 2012 at 3:18 PM, Rick Jelliffe  
> <rjelliffe@allette.com.au> wrote:
>> 2) Clearer story on how to use the ISO/MathML entity sets along with XML
>> Schemas, or with no schemas. I often hear "XML Schemas does not support
>> entities, so I cannot use entities with XML Schemas" or vice versa.
>> Preferably, build the default mappings of the entities into XML.
> Adding entities to XML without DTDs would break the compatibility of
> new documents with old parsers. I think entities alone are not worth
> such a discontinuity.
> If there's a discontinuity that makes new documents potentially
> incompatible with old parser (but old documents stay compatible with
> new parsers), I think it makes sense to move to well-defined
> non-Draconian processing (XML5-style) while at it.
> --
> Henri Sivonen
> hsivonen@iki.fi
> http://hsivonen.iki.fi/
> _______________________________________________________________________
> XML-DEV is a publicly archived, unmoderated list hosted by OASIS
> to support XML implementation and development. To minimize
> spam in the archives, you must subscribe before posting.
> [Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
> Or unsubscribe: xml-dev-unsubscribe@lists.xml.org
> subscribe: xml-dev-subscribe@lists.xml.org
> List archive: http://lists.xml.org/archives/xml-dev/
> List Guidelines: http://www.oasis-open.org/maillists/guidelines.php

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]

News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 1993-2007 XML.org. This site is hosted by OASIS