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 5529 - Clarify Appendix C
Summary: Clarify Appendix C
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: Kumar Pandit
QA Contact: SML Working Group discussion list
URL:
Whiteboard:
Keywords: externalComments, reviewerSatisfied
Depends on:
Blocks:
 
Reported: 2008-03-04 16:55 UTC by Pratul Dublish
Modified: 2008-06-24 12:53 UTC (History)
3 users (show)

See Also:


Attachments

Description Pratul Dublish 2008-03-04 16:55:45 UTC
Minor comment in http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2008Mar/0001.html

Appendix C: If I've understood things correctly, the presence of the
reference in the instance document cannot have any impact on model
validation, since, as is emphasised in the text, the schema
doc. involved contains none of the SML attributes which would provoke
reference checking, right?  If so, please call this out.  If not,
please clarify!
Comment 1 Pratul Dublish 2008-03-06 17:07:21 UTC
Even if no SML constraints are defined in the schema, the references in instance documents will be checked for the following
4.2.1 At Most One Target
Every non-null SML reference MUST target at most one element in a model. A recognized reference scheme in an SML reference MUST NOT resolve to more than one target. 

4.2.2 Consistent References
If a non-null SML reference contains multiple reference schemes, all recognized reference schemes MUST resolve to the same target or they all MUST be unresolved. 


This should be clarified in the text of the appendix
Comment 2 Kumar Pandit 2008-03-13 19:04:50 UTC
resolution (3/13 conf call): mark editorial. Editors to fix per comment# 1 and then mark as needsReview
Comment 3 Kumar Pandit 2008-05-15 18:56:05 UTC
The SML WG agrees with the suggestion. We will change the text as suggested. 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 resolution and let us know if you agree with it by adding a comment to the issue record. If we do not hear from you in the next two weeks, we will assume you agree with the WG decision.
Comment 4 Kumar Pandit 2008-06-05 18:39:19 UTC
resolution (6/5/08 conf call):  remove the decided keyword
Comment 5 Kumar Pandit 2008-06-05 21:43:52 UTC
Added the following paragraph in Appendix C:

Note that, there are no SML constraints defined on the EnrolledCourse element or on the type of that element in the schema. Therefore, even if the first EnrolledCourse element instance is marked as an SML reference, no SML constraints are evaluated for that element during model validation. However, checks such as the ones defined in section 4.2.1 At Most One Target and section 4.2.2 Consistent References are still performed on that SML reference during model validation. 
Comment 6 Pratul Dublish 2008-06-12 19:12:57 UTC
SML WG approves Comment #5
Comment 7 Henry S. Thompson 2008-06-24 12:52:23 UTC
I'm happy that the additional text in Appendix C removes the apparent contradiction.