[
Lists Home |
Date Index |
Thread Index
]
- To: "Costello, Roger L." <costello@mitre.org>
- Subject: Re: [xml-dev] [SUMMARY #1] Why is there little usage of XML on the'visible Web'?
- From: Mitch Amiano <mitch.amiano@agilemarkup.com>
- Date: Sat, 22 Jul 2006 10:56:46 -0400
- Cc: xml-dev@lists.xml.org
- In-reply-to: <B8415163A689094689542C617ECA0366E03FA2@IMCSRV5.MITRE.ORG>
- References: <B8415163A689094689542C617ECA0366E03FA2@IMCSRV5.MITRE.ORG>
- User-agent: Thunderbird 1.5.0.4 (Windows/20060516)
My bad for forgetting your post.
The example you gave was my first case - delivering my own bespoke
markup to a browser, but excluding XHTML.
So I'd conclude with others that the assertion (1)
>
> There is little usage of XML on the visible Web. That is, the
> information available to the end user (or his/her browser) is primarily
> in the form of (X)HTML, not XML.
is true in that case.
First, because the trouble of dealing with non-existent or defective browser implementations means delivering XML + XSLT to the client is not worth the effort.
Second, because the client-side experience isn't sufficiently enhanced to warrant the transform on the client side.
Third, because it isn't worth it to me to share my grocery list.
Costello, Roger L. wrote:
>
> Hi Mitch,
>
> You make an excellent point. I tried to characterize what I mean by
> "XML" in my initial message:
>
> *EXAMPLE: USING XML ON THE VISIBLE WEB*
>
> Suppose that you have a Web site where you make available your grocery
> list to anyone with a browser. “Using XML on the visible Web” means
> that you create an XML document that contains the raw grocery list,
> and a separate document (/e.g.,/ XSLT) which transforms the raw
> grocery list into a visually appealing form. Here is grocery.xml:
>
> <?xml version=“1.0”?> “
>
> <?xml-stylesheet type=“text/xsl” href=“grocery.xsl”?>
>
> <grocery-list>
>
> <fruit>Orange</fruit>
>
> <meat>Chicken</meat>
>
> <vegetable>Corn</vegetable>
>
> </grocery-list>
>
> Here is the URL to your grocery list resource:
>
> http://www.example.org/food/grocery-list
>
> A browser client that issues this URL will receive grocery.xml, and
> then it will dynamically transform the XML into HTML using grocery.xsl
>
> Let’s imagine that grocery.xsl displays the grocery items as an
> unordered bulleted list, and so the XML is rendered by the browser
> like this:
>
> * Orange
> * Chicken
> * Corn
>
> Your Web site is employing XML on the visible Web!
>
> *EXAMPLE: _NOT_ USING XML ON THE VISIBLE WEB*
>
> Now let’s contrast the above example with not using XML on the visible
> Web, instead, using HTML. A browser client that issues the above URL
> will receive from your Web site this HTML:
>
> <HTML>
>
> <body>
>
> <ul>
>
> <li>Orange</li>
>
> <li>Chicken</li>
>
> <li>Corn</li>
>
> </ul>
>
> </body>
>
> </HTML>
>
> The browser immediately renders the HTML. The same bulleted list shown
> above is displayed.
>
> Your Web site is _not_ employing XML on the visible Web!
>
|
