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 5109 - sml 4.3.2.0 Constraints on Targets
Summary: sml 4.3.2.0 Constraints on Targets
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:33 UTC by John Arwe
Modified: 2007-10-25 19:41 UTC (History)
0 users

See Also:


Attachments

Description John Arwe 2007-09-30 19:33:42 UTC
from "SML supports three attributes: "
to   "SML defines  three attributes: "

from "...the same name as P must specify the same set ..."
to   "...the same name as P MUST specify the same set ..."

from "...as P and these attributes must have the same values..."
to   "...as P and these attributes MUST have the same values..."

from "...all of the following must be enforced:"
to   "...all of the following MUST be enforced:"

from "The above conditions on the use of sml:target* attributes..."
to   "Note (non-normative):
      The above conditions on the use of sml:target* attributes..."

from "...implementation burden  on  model validators for verifying..."
to   "...implementation burden on model validators for verifying..."
(remove 2 extra spaces around "on")

from "... and they MUST be supported on global and local element declarations. "
to   ".  Model authors MAY specify them on any <xs:element> in a schema document. "
(steals more precise language from acyclic and separates concerns)

move "Model validators that conform to this specification MUST enforce the following:" AFTER paragraph break that follows this text today.

Recommend taking all the text starting with "Model validators that conform to this specification MUST enforce the following:" and ending before "4.3.2.1 sml:targetElement" and making it a new h4 "Derivation by Restriction".  I would also recommend placing that new section AFTER the 3 target* attributes it applies to instead of before.
Comment 1 Kumar Pandit 2007-10-25 06:33:29 UTC
Made all of the suggested changes except the following one:

from "... and they MUST be supported on global and local element declarations.
"
to   ".  Model authors MAY specify them on any <xs:element> in a schema
document. "

IMO, what model authors may choose to do is not the same as what an implementation must support. If I am wrong in this assumption then feel free to reopen the bug.
Comment 2 John Arwe 2007-10-25 13:33:14 UTC
The part of the change that mattered more was missed in comment #1.  The existing version says local and global, the new version implicitly says global (omitted local consciously, since I believe we currently say elsewhere they are only allowed on globals).  No quibble with the model author vs implementor part.
Comment 3 John Arwe 2007-10-25 19:41:31 UTC
Mistook xs:element for saying not local, which is incorrect.  So fine as fixed, closing.