[Home] [By Thread] [By Date] [Recent Entries]

  • From: David Carlisle <d.p.carlisle@g...>
  • To: Roger L Costello <costello@m...>
  • Date: Wed, 8 Feb 2023 11:55:20 +0000



On Wed, 8 Feb 2023 at 11:43, Roger L Costello <costello@m...> wrote:
excellent.

My <airport> use case is an example of (a). The <airport> element provides information. An aircraft flight management system (FMS) uses that information to fly the airplane.

My <xsl:value-of ...> use case is an example of (b). The <value-of> element is an instruction. An XSLT processor reacts to the presence of that element with a certain specific defined behavior.


No. Your two examples are the same. They are just data encoded in XML. As being discussed at present in another thread, the xsl:value-of might just be input data to a process that produces canonical  xslt, or Xquery or whatever.  Conversely the airport xml could be processed by some auto-pilot system to control a flight . In what way are the two fragments different?


My <airport> use case is an example of (b). The <airport> element  is an  instruction. An aircraft flight management system (FMS) reacts to the presence of that element with a certain specific defined behavior. to fly the airplane.

My <xsl:value-of ...> use case is an example of (a). The <value-of> provides information..It demonstrates, for example in this email, aspects of XSLT syntax.

 


David



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


Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member