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

Namespaces and XSLT simplified syntax

  • From: Dan Vint <dvint@s...>
  • To: xml-dev@i..., xsl-list@m...
  • Date: Sun, 09 Jan 2000 16:13:21 -0500

xsl simplified
Here is yet another question on namespaces that I came up with after looking at
the XSLT specification and its simplified syntax. And let me go a little
further back to HyTime.

I understand (sort of) how an attribute on any'ol element can be pointed to or
mapped to an attribute in a different namespace by using a prefix to the
attribute name as shown here:

<html xsl:version="1.0"
                xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
                xmlns="http://www.w3.org/TR/xhtml1/strict">

I also thought that architectural forms from HyTime allowed me to say this
element of whatever name I specify should be treated like this other element
over here - I don't remember what the syntax is for it by I have sort of
thought of namespaces as being related to this functionality.

What I'm looking for is the syntax in XML/namespaces that would allow me to say
(in the above example)
that my element <html> should be treated as <xsl:stylesheet> and thus allow me
to use content from the HTML content model for the element <html> and the
content for the <xsl:stylesheet>. Of course I would use the namespace prefix
for those elements as well.

Is there a method for aliasing two elements like this?

There seems to be an indication that an xsl:stylesheet modeled style sheet
should work the same as a stylesheet somehow being managed in a literal result
element (see the requirements for the version and other attributes in this
case), but then the only example shown in the spec (and the only model that I
can think of) seems to fall squarely into the simplified syntax model which
then has the restrictions about only using instruction elements - am I just
mixing these two ideas up? 

Is the simplified syntax just a stricter set of requirements, but the more
general form of using a literal result element as the document root and
spreading xsl:xxxx top-level elements is allowed in the more general case?

..dan

---------------------------------------------------------------------------
Danny Vint                                       http://www.dvint.com
Author: SGML at Work   	http://www.slip.net/~dvint/pubs/sgmlatwork.shtml 
                                                       mailto:dvint@s...
    
Calian                                              Voice:804-975-3482
mailto:d.vint@c...
Charlottesville, VA Office                http://www.calian.com              


xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@i...
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To unsubscribe, mailto:majordomo@i... the following message;
unsubscribe xml-dev
To subscribe to the digests, mailto:majordomo@i... the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@i...)



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
 

Stylus Studio has published XML-DEV in RSS and ATOM formats, enabling users to easily subcribe to the list from their preferred news reader application.


Stylus Studio Sponsored Links are added links designed to provide related and additional information to the visitors of this website. they were not included by the author in the initial post. To view the content without the Sponsor Links please click here.

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.