OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
Re: [xml-dev] Why do W3C specifications have "implementation defined"parts?

On 08/04/2010 13:06, Costello, Roger L. wrote:
> In many of the W3C specifications there are parts that are "implementation defined."
> To give one example, in the XSLT specification it says this about the<xsl:message>  element [1]:

well sometimes one suspects that it is because the committee couldn't 
agree on something.

However in the example you gave being the destination of xsl:message 
output, that interacts with the host environment so is intrinsically 
implementation specific. How could it be defined?
The XSLT spec assumes nothing about the host environment, no assumption 
that there is for example a file system accessible so it is hard to see 
how you could define in a way that makes sense on all systems a standard 
location for any output.

Similarly XSLT has a notion of parameters that may be set externally but 
there is no mechanism specified or specifiable within the XSLT spec as 
to how they may be set,


The Numerical Algorithms Group Ltd is a company registered in England
and Wales with company number 1249803. The registered office is:
Wilkinson House, Jordan Hill Road, Oxford OX2 8DR, United Kingdom.

This e-mail has been scanned for all viruses by Star. The service is
powered by MessageLabs. 

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

News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 1993-2007 XML.org. This site is hosted by OASIS