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 27880 - Adaptive serialization method, default value of item-separator
Summary: Adaptive serialization method, default value of item-separator
Status: CLOSED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: Serialization 3.1 (show other bugs)
Version: Candidate Recommendation
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: C. M. Sperberg-McQueen
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-01-22 08:37 UTC by Christian Gruen
Modified: 2015-01-27 17:58 UTC (History)
0 users

See Also:

Attachments

Description Christian Gruen 2015-01-22 08:37:17 UTC 
In Bug 27498, the new serialization method "adaptive" was introduced. The current working draft says that

  Each item in the supplied sequence is serialized individually as follows,
  with an occurrence of the chosen item-separator between successive items.

However, the item-separator can be absent, so need to clarify what is going to happen in that case. I would propose to use 
 (newline) as fallback separator, as this is the character that's usually bound to the item-separator parameter, in particular when using "command line or other "ad-hoc" interfaces", as motivated by mkay in Bug 27498.
Comment 1 C. M. Sperberg-McQueen 2015-01-27 16:42:19 UTC 
The responsible WGs discussed this issue at today's call, and agreed to make the suggested change.  In section 10.1.15 [1], add the sentence:

    If the item-separator parameter is absent, the string '
' (a single newline character) is used by the Adaptive Serialization method as the item-separator value.

[1] https://www.w3.org/XML/Group/qtspecs/specifications/xslt-xquery-serialization-31/html/#ADAPTIVE_ITEM-SEPARATOR

(Wording may need editorial word-smithing.)

Christian, if you would, please review the disposition of your comment and indicate that you are satisfied with the resolution by closing the bug, or if necessary indicate that you are dissatisfied by reopening it and explaining what is wrong.  If the WGs don't hear from you one way or the other in two weeks, we'll assume you are content.
Comment 2 Christian Gruen 2015-01-27 17:58:27 UTC 
Michael, thanks for the confirmation; I have closed the bug.