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 4652 - Should SML-IF be described at the octet level or the infoset level?
Summary: Should SML-IF be described at the octet level or the infoset level?
Alias: None
Product: SML
Classification: Unclassified
Component: Interchange Format (show other bugs)
Version: unspecified
Hardware: Macintosh All
: P2 normal
Target Milestone: Second draft
Assignee: Valentina Popescu
QA Contact: SML Working Group discussion list
Keywords: editorial
: 4666 (view as bug list)
Depends on:
Reported: 2007-06-13 22:37 UTC by C. M. Sperberg-McQueen
Modified: 2007-08-28 03:52 UTC (History)
1 user (show)

See Also:


Description C. M. Sperberg-McQueen 2007-06-13 22:37:22 UTC
At various points (e.g. 3.2), the SML-IF document describes SML-IF 
documents (and other XML documents) at the level of the octet stream.

Some WG members believe that it would be better to define SML-IF
exclusively (or at least primarily) at the level of the XML information
set of the documents in question, and to leave all details of the
character encoding scheme and similar issues to the XML parsing layer
of the stack.  This affects the description of SML-IF documents in
the third paragraph of 3.2, the description of physical embedding
of model documents in the fifth paragraph (and following) of 3.2,
and possibly other parts of the spec.  (A separate issue is to be raised
concerning the encoding question in 3.2 paragraph 3.)
Comment 1 Virginia Smith 2007-08-02 20:04:33 UTC
Resolution is to remove second bullet point in 3.3 and move to non-normative text.
Comment 2 Virginia Smith 2007-08-09 18:38:00 UTC
*** Bug 4666 has been marked as a duplicate of this bug. ***
Comment 3 Valentina Popescu 2007-08-28 03:52:38 UTC
Removed this bullet from section 3.3 
* be encoded either in UTF-8 or in UTF-16.

Created this item under the Open Issues ( Non Normative section )

*Remove requirement that SML IF documents must be encoded using UTF-8 or UTF-16.