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 5524 - Rename section 4.4.1.1
Summary: Rename section 4.4.1.1
Status: RESOLVED FIXED
Alias: None
Product: SML
Classification: Unclassified
Component: Core (show other bugs)
Version: LC
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Virginia Smith
QA Contact: SML Working Group discussion list
URL:
Whiteboard:
Keywords: externalComments, reviewerSatisfied
Depends on:
Blocks:
 
Reported: 2008-03-04 16:50 UTC by Pratul Dublish
Modified: 2008-08-07 18:37 UTC (History)
3 users (show)

See Also:


Attachments

Description Pratul Dublish 2008-03-04 16:50:36 UTC
Minor comment from http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2008Mar/0001.html 
4.4.1.1: Please call this "Mapping from schema document"
Comment 1 Kumar Pandit 2008-03-06 20:31:38 UTC
resolution (3/6 conf call): mark as not a valid bug

Reason:
The attributes and elements on which these mappings rely are present not only in schema documents but also in schemas (in the relevant annotation properties), so we believe the current title is correct.
Comment 2 Henry S. Thompson 2008-04-18 13:59:03 UTC
[Section is now "5.2.1.1 Mapping from Schema"]  I still think this is ill-judged -- the prose of this section talks _only_ about mapping from attributes and elements, which always originate in schema documents.  Could we compromise on "Mapping from XML Representations" ?
Comment 3 C. M. Sperberg-McQueen 2008-04-24 18:18:02 UTC
Strictly speaking, I think the premise that elements and attributes
always originate in schema documents is at fault here.  The section on
mapping from schema is talking about the mapping from an annotation
component (NOT an annotation source declaration), the contents of
which are element and attribute information items.  

In the usual case, of course, the elements and attributes will have
originated in a schema document, but we wish also to cover the case
that the annotation component was born binary.  Even in the latter
case, however, it will contain element and attribute information
items.
Comment 4 Pratul Dublish 2008-04-24 18:19:39 UTC
The SML WG endorsed Comment #3 in the 4/24 call
Comment 5 Kumar Pandit 2008-05-15 19:06:09 UTC
The SML WG believes that comment# 3 combined with the response to bug# 5520 comment# 5 addresses this issue fully.

I'm changing its status accordingly. The change in status should cause email to be sent to the originator of this issue, to whom the following request is addressed.

Please review the comment text and let us know if you agree with this resolution of your issue, by adding a comment to the issue record. Or, if you do not agree with this resolution, please add a comment explaining why. If we do not hear from you in the next two weeks, we will assume you agree with the WG decision.

Comment 6 James Lynn 2008-07-10 19:25:17 UTC
Sandy has discussed this with Henry and he is ok with "mapping from schema" -> "sml constraint contruction"

This will need to be considered in all 5 places where this exists. Editors shall consider each individually.
Comment 8 Henry S. Thompson 2008-07-28 12:44:18 UTC
I'm satisfied by the most recent change.
Comment 9 Pratul Dublish 2008-08-07 18:37:33 UTC
Per resolution in 8/7 call