RE: [xml-dev] Why do W3C specifications have "implementationdefined" par

["stephengreenubl@gmail.com" <stephengreenubl@gmail.com>]

As an example, I worked on OASIS UBL where we  defined codelists which had built in (specified) values but also codelists, like tax code, for which we did not provide values (implementation-defined). There's no prpblem with this.

Stephen D Green


-----Original Message-----
From: Costello, Roger L.
Sent:  08/04/2010 1:06:13 pm
Subject:  [xml-dev] Why do W3C specifications have "implementation defined" parts?

Hi Folks,

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]:

    The xsl:message instruction sends a message in an implementation-defined way. 
    The xsl:message instruction causes the creation of a new document, which is 
    typically serialized and output to an implementation-defined destination.


QUESTIONS:

1. The purpose of a specification is to define a standard. Doesn't "implementation defined" defeat that purpose since it means that each vendor will define their implementation in their own way, thereby obviating standardization?

2.Is this unique to the W3C? Do other standards organizations also have "implementation defined" sections in their specifications?


/Roger

[1] http://www.w3.org/TR/2007/REC-xslt20-20070123/#message 

_______________________________________________________________________

XML-DEV is a publicly archived, unmoderated list hosted by OASIS
to support XML implementation and development. To minimize
spam in the archives, you must subscribe before posting.

[Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
Or unsubscribe: xml-dev-unsubscribe@lists.xml.org
subscribe: xml-dev-subscribe@lists.xml.org
List archive: http://lists.xml.org/archives/xml-dev/
List Guidelines: http://www.oasis-open.org/maillists/guidelines.php