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 5111 - 4.4 Identity Constraints and later
Summary: 4.4 Identity Constraints and later
Status: RESOLVED FIXED
Alias: None
Product: SML
Classification: Unclassified
Component: Core (show other bugs)
Version: unspecified
Hardware: PC Windows XP
: P2 normal
Target Milestone: ---
Assignee: Kumar Pandit
QA Contact: SML Working Group discussion list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-09-30 19:46 UTC by John Arwe
Modified: 2007-10-20 01:23 UTC (History)
0 users

See Also:


Attachments

Description John Arwe 2007-09-30 19:46:43 UTC
several cases of 
from "...attribute MUST be     name of ..."
to   "...attribute MUST be the name of ..."

some of the bulleted list entries end with full stop (period), others do not.
all should (or should not, but should is usually easier)
Comment 1 John Arwe 2007-09-30 20:09:24 UTC
4.4.3 sml:keyref
from "...be used to scope references to point to elements within a valid range."
to   "...be used to scope references to point to elements with a valid range of values."
I am assuming "values" is the intent, although it could have been "location in the document"

5.2.1 Limited Support
If the queryBinding attribute is specified, then its value MUST be set to "xslt".
(add full stop aka period at end)

Comment 2 Kumar Pandit 2007-10-20 01:22:07 UTC
all changes were made as suggested except one.

The clause ", and can be used to scope references to point to elements within a valid range." was deleted. This makes the text clearer without chaning the meaning.