This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 1276 - "implementation-provided" needs to be defined if used
Summary: "implementation-provided" needs to be defined if used
Status: CLOSED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XPath 2.0 (show other bugs)
Version: Last Call drafts
Hardware: PC Windows XP
: P2 normal
Target Milestone: ---
Assignee: Don Chamberlin
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-04-28 13:03 UTC by Jonathan Robie
Modified: 2005-05-09 18:38 UTC (History)
0 users

See Also:

Attachments

Description Jonathan Robie 2005-04-28 13:03:52 UTC 
The phrase "implementation-provided default" now occurs throughout the XPath /
XQuery specs, but is nowhere defined. Is this the same as
"implementation-defined" default? If not, what is the difference?
Comment 1 Michael Rys 2005-04-28 19:10:34 UTC 
"implementation-provided" means that the value is provided by the 
implementation. This can be either through an implementation-defined or 
implementation-dependent mechanism and just means that it comes from the 
outside of the scope of the specification. I am not sure that we really need 
to add a definition for this English term. Would "externally-initialized" be 
better?
Comment 2 Don Chamberlin 2005-05-09 18:03:20 UTC 
The phrase "implementation-provided" never occurs in the XPath spec. It occurs 
in the XQuery spec four times, always referring to an implementation-defined 
default value. I have changed each of these phrases to "implementation-
defined." I consider this to be an editorial change.
Comment 3 Jonathan Robie 2005-05-09 18:38:13 UTC 
Yes, I think it's editorial, and your solution makes me happy.