Lists Home |
Date Index |
- From: Chris Maden <firstname.lastname@example.org>
- To: email@example.com
- Date: Wed, 8 Jul 1998 14:13:22 -0400 (EDT)
> > <xsl:rule pattern="html:p">
> > <paragraph>
> > <xsl:children/>
> > </paragraph>
> > </xsl:rule>
> This is neither explicitly forbidden nor explicitly supported in the
> current namespaces draft -- the meaning of colons in attribute
> values is undefined.
That's true. But in XSL, that attribute contains element type names,
and so I would expect an XSL processor to handle them as such.
> More generally, however, it might make sense to partition rules by
> namespace, either in separate XSL specs or at least in separate
> sections; the reason is that well-known namespaces will often come
> with their own XSL specifications, and the author of a top-level XSL
> spec should not have to duplicate that work.
He wouldn't have to; he can include the well-known stylesheets and
override parts of them. That doesn't imply a need for segregation.
(It is possible that XSL will have stylesheet sections, but I don't
think that namespaces alone necessitate them.)
<!NOTATION SGML.Geek PUBLIC "-//Anonymous//NOTATION SGML Geek//EN">
<!ENTITY crism PUBLIC "-//O'Reilly//NONSGML Christopher R. Maden//EN"
<USMAIL>90 Sherman Street, Cambridge, MA 02140 USA" NDATA SGML.Geek>
xml-dev: A list for W3C XML Developers. To post, mailto:firstname.lastname@example.org
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:email@example.com the following message;
To subscribe to the digests, mailto:firstname.lastname@example.org the following message;
List coordinator, Henry Rzepa (mailto:email@example.com)