• From: David <dlee@c...>
• To: xml-dev@l...
• Date: Fri, 20 Aug 2010 13:05:51 -0400

I agree your example with XSLT is one use case.  I don't agree it should 
be generalized to all uses of XML.
I also suggest "Prime App" is misleading in the general case.  For XSLT 
and XHTML it may be a good description.
For many other types of XML it is not a good description.


On 8/20/2010 12:53 PM, Costello, Roger L. wrote:
>> If everyone used the same application there would be no need for data
>> interchangeability. "interchangeability" implies the possibility of>  1.
>> If everyone uses the same app XML would be irrelevant.
> I appreciate your feedback David and David. It is helping me to clarify and refine my argument.
>
> Consider XSLT. I can create an XSLT document and run it on my XSLT processor. I can send the XSLT document to you and you run it on your XSLT processor. We get the same behavior. We agree perfectly on what the<xsl:for-each>  element means and how it should behave. Ditto for all the other elements and attributes in the XSLT vocabulary.
>
> We have successfully interoperated.
>
> What enabled this?
>
> What enabled the interoperability is the fact that we are using the same Prime App. (You may be using Xalan and I may be using Saxon; they both belong to the same class of Prime Apps.)
>
> I can create a second XSLT document and send it to you. Again, perfect interoperability. And a third. And so forth. The Prime App allows endless different XSLT transforms to be created, exchanged and executed with perfect understanding/interoperability.
>
>
> /Roger
>
>
> _______________________________________________________________________
>
> 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@l...
> subscribe: xml-dev-subscribe@l...
> List archive: http://lists.xml.org/archives/xml-dev/
> List Guidelines: http://www.oasis-open.org/maillists/guidelines.php
>


-- 
David A. Lee
dlee@c...
http://www.xmlsh.org

• References:
  • Data Interoperability ... Why do some XML vocabularies specifymeaning + behavior whereas others specify only meaning?
    • From: "Costello, Roger L." <costello@m...>
  • RE: Data Interoperability ... Why do some XML vocabularies specifymeaning + behavior whereas others specify only meaning?
    • From: "Costello, Roger L." <costello@m...>
  • Re: RE: Data Interoperability ... Why do some XML vocabulariesspecify meaning + behavior whereas others specify only meaning?
    • From: David <dlee@c...>
  • RE: RE: Data Interoperability ... Why do some XMLvocabularies specify meaning + behavior whereas others specify only meaning?
    • From: "Costello, Roger L." <costello@m...>