[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

RE: Extended file extentions (XfeX) for xml/xsl files

Subject: RE: Extended file extentions (XfeX) for xml/xsl files
From: Mark Birbeck <Mark.Birbeck@xxxxxxxxxxxxx>
Date: Sun, 28 Nov 1999 18:39:58 -0000
file extentions
Stefano Mazzocchi wrote:
> Choices are
> 
>  single chars:
> 
>    "."    standard.xmlspec.html.xsl
>    "-"    standard-xmlspec-html.xsl
>    "_"    standard_xmlspec_html.xsl 
>    "@"    standard@xmlspec@h...
>    ...
> 
>  more complex char names
> 
>   "[]"   standard.[xmlspec][html].xsl
>   "{-}"  standard.{xmlspec-html}.xsl

> What are your comments? (please, let's not get too religious 
> about this, let's come up with real arguments, not personal
> esthetic reasons only)

Tell *that* to Nietzsche! ;-)

I like the proposition. I wonder if you might want to consider some
aspects from another direction, to see if we can harmonise. In
particular when the name is used in a full URL:

1. I'd avoid '[' and ']' because of XPath. I already read XML
   from a database with a sort of sub-XPath, and I'm sure others
   have done the full thing:

	http://server/articles/article[@ID=5]

2. If you can, keep away from the '.' because it already breaks the
   document name from the document format. In my case I use it to
   separate the stylesheet that should be applied to an XML document
   from the content type to use for return:

	http://server/articles/article[@ID=5]/article.htm

   gives me the XML for article 5 as an HTML document, created using
   http://server/stylesheets/article.xsl, whilst:

	http://server/articles/article[@ID=5]/article.xml

   would give the same transformation (stylesheets/article.xsl) but
   set the content type to XML (say for XHTML). The reason I do this,
   is so I can have things like:

	http://server/articles/article[@ID=5]/word.doc

   and:

	http://server/people/person[@ID=5]/person.vcf

   which allows piping my XML straight into some application. It
   also allows easy specification of different stylesheets for
   alternative output:

	http://server/articles/article[@ID=5]/handheld.htm

3. I have begun to extend this logic as follows:

	http://server/articles/article[@ID=5]/summary.handheld.htm

   and:

	http://server/articles/article[@ID=5]/summary.WebTV.htm

   Therefore, if I was to make my stylesheet names more meaningfull
   using your syntax, I might have a stylesheet called:

	article_fo.xsl

   and another called:

	fo_handheld.xsl

   and yet another called:

	fo_WebTV.xsl

   Then my URLs might become:

	http://server/articles/article[@ID=5]/article_fo.fo_WebTV.htm

What do you think?

Regards,

Mark


Mark Birbeck
Managing Director
x-port.net Ltd.
220 Bon Marché Centre
241-251 Ferndale Road
London
SW9 8BJ
w: http://www.iedigital.net/
t: +44 (171) 501 9502
e: Mark.Birbeck@xxxxxxxxxxxxx


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list


Current Thread

PURCHASE STYLUS STUDIO ONLINE TODAY!

Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
Email
First Name
Last Name
Company
Subscribe in XML format
RSS 2.0
Atom 0.3
Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.