RE: My specification writing project has failed :-(
Thanks for the explanation. A problem I see is fundimental. What transformation to do is really a property of the application not the namespace. Example. Suppose you have MathML inside XHTML. There are many ways this could be transformed, and it is not up to either the MathML or XHTML namespaces (or more accurately the publisher of the URIs) to decide for the app what the transformation should be like. I think you could use RDF to describe a mapping of namespaces to say XSLT code (or a simplier one to one mapping) but it should reside in the application layer, not be associated globally as a property of the namespaces. That's my take atleast. But as Len said, don't see this as failure ! You learned things, solicited input from others and got others to think about ideas. That's success. ---------------------------------------- David A. Lee firstname.lastname@example.org http://www.xmlsh.org > -----Original Message----- > From: Victor Porton [mailto:email@example.com] > Sent: Friday, June 29, 2012 10:58 AM > To: David Lee; firstname.lastname@example.org > Subject: Re: My specification writing project has failed :-( > > 29.06.2012, 17:46, "David Lee" <email@example.com>: > > The topic seems interesting so I started reading this spec but unfortunately I > cannot understand what the goal is. > > It is not clear at all to me what "Transformation between XML namespaces" > is meant to do. Perhaps if you could describe that more clearly I might have > suggestions ... > > Suppose we have an XHTML document with added other namespaces, such as > semantic markup not included in the XHTML vocabulary. > > We want to convert it into plain XHTML (or maybe into XML Formatting > Objects, or whatever). > > My idea was to do this download RDF files from all document namespaces > used in this documents, and then run transformations described in these RDF > files, to do it with whatever namespaces may be invented. > > > The other goal ... validating documents with multiple namespaces, isn't that > already handled by current XML Schema specifications ? What am I missing > here ? > > The existing software does not validate subdocuments of other namespaces. > > My idea about this is to retrieve validation info directly from namespace URLs > of all namespaces in the document. > > There are no trouble with validation (like it is a trouble with transformation), > but it is not worth to doing an RDF at namespace URL for validation only. > > -- > Victor Porton - http://portonvictor.org
[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