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 1340 - determing the value of character encoding scheme during serialization
Summary: determing the value of character encoding scheme during serialization
Status: CLOSED WONTFIX
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: Data Model 1.0 (show other bugs)
Version: Last Call drafts
Hardware: PC Windows XP
: P2 normal
Target Milestone: ---
Assignee: Norman Walsh
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-05-11 03:16 UTC by Felix Sasaki
Modified: 2005-06-22 07:44 UTC (History)
0 users

See Also:

Attachments

Comment 1 Norman Walsh 2005-05-17 13:54:52 UTC 
S3c. 6.1.5 (infoset mapping)

You write at the end of the section that the [character encoding scheme]
property has no value. You should add s.t. like "Its value is determined during
the serialization of the data model." and a link to the section which defines
the encoding parameter of the serialization, e.g. in sec. 3.

Based on Martin's review, comment [21]
Comment 2 Felix Sasaki 2005-05-30 08:38:46 UTC 
consensus of the i18n-core-wg, telecon 27 may 2005: approved by i18n-core-wg.
Comment 3 Norman Walsh 2005-06-07 15:39:10 UTC 
I think we should reject this comment. The [character encoding scheme] in the
generated infoset has no value (it can't have a value because we didn't start
with an encoded sequence of octets.

The serialized data model *is* a sequence of octets and therefore has no
[character encoding scheme] property at all.
Comment 4 Norman Walsh 2005-06-07 16:25:53 UTC 
Rejected at 7 June 2005 telcon.
Comment 5 Norman Walsh 2005-06-20 18:54:23 UTC 
Dear i18n-core-wg:

Per the 7 June 2005 telcon, the QT groups have elected to reject this comment.
The [character encoding scheme] in the generated infoset has no value (it can't
have a value because we didn't start with an encoded sequence of octets.

The serialized data model *is* a sequence of octets and therefore has no
[character encoding scheme] property at all.

Please let us know if you find this resolution unsatisfactory.
Comment 6 Felix Sasaki 2005-06-22 07:44:23 UTC 
consensus of the i18n-core-wg (telecon 21 May 2005):
We regard the issue as closed.
Best regards, Felix Sasaki