XML.orgXML.org
FOCUS AREAS |XML-DEV |XML.org DAILY NEWSLINK |REGISTRY |RESOURCES |ABOUT
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] Towards XML 2.0

Most Excellent ! I was only aware of the XProc Profile spec.

 

Question:  I cant tell by reading this isf the Minimum  profile actually requires parsing of namespaces.

It must be "namespace wellformed' which just limits the number ":" in attributes but does it have to be a 'namespace aware' processor ?

 

 

 

----------------------------------------

David A. Lee

dlee@calldei.com

http://www.xmlsh.org

 

From: vojtech.toman@emc.com [mailto:vojtech.toman@emc.com]
Sent: Tuesday, December 07, 2010 7:55 AM
To: xml-dev@lists.xml.org
Subject: RE: [xml-dev] Towards XML 2.0

 

Just to make sure, you are all aware of the XML Processor Profiles draft, right?

 

http://www.w3.org/TR/xml-proc-profiles/

 

Incidentally, it is in last call now, so if you want to comment, you should let us know now. :)

 

Regards,

Vojtech

 

 

--
Vojtech Toman
Consultant Software Engineer
EMC | Information Intelligence Group
vojtech.toman@emc.com
http://developer.emc.com/xmltech

 

From: David Lee [mailto:dlee@calldei.com]
Sent: Tuesday, December 07, 2010 1:44 PM
To: 'Cecil New'; stephengreenubl@gmail.com
Cc: Toman, Vojtech; xml-dev@lists.xml.org
Subject: RE: [xml-dev] Towards XML 2.0

 

+10 !!! for conformance classes.

This is what I meant when suggesting "Processor Profiles".

A set of well-defined subsets of XML for particular purposes.   It would all still be "XML" but just limit the use to particular features,

and enable processers to be written optimized for that class/profile.

By defining these publicly it gives a 'nod' to the users to 'feel OK' about what they are doing, and a justification to other engineers/mgt etc.

It also gives a common set of specs for all parts of the content pipe.   This would be a great boon for the Mobile space, IMHO,

as we might actually get a decent mobile XML parser (possibly in JS) conforming to a 'standard' profile … instead of giving up because

doing 100% was just too big.

 

"Were using Min Profile 3.2 - No Namespaces, No Mixed Content …"



[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