- From: <bugzilla@wiggum.w3.org>
- Date: Wed, 25 Jun 2008 09:14:52 +0000
- To: public-sml@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=5721
John Arwe <johnarwe@us.ibm.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords|needsReview |editorial
--- Comment #5 from John Arwe <johnarwe@us.ibm.com> 2008-06-25 09:14:52 ---
f2f consensus review of comment 4
proposal 1: wg ignored the fact that no diff was given, grudgingly, however
believes the text should be changed to:
It is a consequence of the preceding that this specification assigns no meaning
to the sml:nilref attribute when it is used on an element that is not an SML
reference. Model validators MAY choose to warn their invokers should they
detect this condition in a document.
Note:
sml:nilref may be useful in the case where the schema author defines a complex
type specifying sml:ref with a fixed value of "true", but the instance author
wants to signal the absence of a target.
proposal 2: wg ignored the fact that no diff was given, grudgingly, however it
prefers the following
The constraints described above can be useful even on element declarations
whose instances are not necessarily SML references, because the decision about
whether to include a constraint and the decision about whether to make the
element an SML reference can be made independently - some choices made by the
schema author, other choices made by the instance document author.
--
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Wednesday, 25 June 2008 09:15:27 UTC