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 15915 - [SER 3.0] Unspecified ==> absent
Summary: [SER 3.0] Unspecified ==> absent
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: Serialization 3.0 (show other bugs)
Version: Last Call drafts
Hardware: PC All
: P2 minor
Target Milestone: ---
Assignee: Henry Zongaro
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
Depends on:
Reported: 2012-02-06 16:31 UTC by Michael Kay
Modified: 2012-07-10 02:20 UTC (History)
1 user (show)

See Also:


Description Michael Kay 2012-02-06 16:31:58 UTC
In 3.1 list item 2 we read "otherwise, the setting of the parameter is unspecified". I think "unspecified" here means "absent" - that is, the effect is that no value has been supplied for the parameter. This is different from "unspecified" which is used in at least one other place to mean "implementation-dependent".
Comment 1 Henry Zongaro 2012-02-06 19:43:45 UTC
Thank you for catching that inconsistency.  If the working groups do not object, I will treat this editorially by making the following changes:

1. Replace item 2 in the numbered list in section 3.1 to read, "otherwise, the setting of the parameter is absent."

2. In the paragraph following the note in section 3.1, change the phrase, "any serialization parameters whose values remain unspecified after applying the mechanism" to "any serialization parameters whose values are absent after applying the mechanism"
Comment 2 Henry Zongaro 2012-07-10 02:20:05 UTC
This will be corrected in the next working draft of Serialization 3.0.