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?


Love'em or loathe 'em, the mil tech pubs world is still a DTD-spec'd  
environment.   Managing entity decls and refs and the entities  
requires a lot of code.   It isn't hard per se but a standard way  
would be better because it means not using XML Schemas.

OTOH, the case for XML Schemas in tech pubs is?

FWIW:  the skill levels required to create and deliver XML/XSL are  
already expensive enough that serious minds are questioning the  
value-add if Word and PDF can accomplish the missions.  I don't have a  
problem challenging those kinds of questions but in environments where  
many of the decision makers have the computer literacy of rhesus  
monkeys, it takes proof with $ columns to be convincing.  So it takes  
a presentation illustrating the pipeline from Word to IETM converted  
out of the DTD-controlled dataset to make the case.   A considerable  
amount of code is required to make that pipe flow.  The more different  
pieces with noisy incompatible standards the easier it is to say, to  
hell with it, let'em eat RTF.


Quoting Rick Jelliffe <rjelliffe@allette.com.au>:

> 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.

[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