[Bug 3889] 3.3.1 incorrect use of "respectively" (editorial)

http://www.w3.org/Bugs/Public/show_bug.cgi?id=3889





------- Comment #4 from dsb@smart.net  2008-02-21 02:52 -------
> Please let us know if you agree with this resolution of your issue, by
> adding a comment to the issue record and changing the Status of the
> issue to Closed. 

The change addresses the problem I reported.


However, something doesn't seem quite right about the improved sentence:

  The explicit values of {substitution group exclusions}, extension or 
  restriction, rule out element declarations having types whose derivation 
  from {type definition} involves any extension steps, or restriction steps, 
  respectively.

Something seems unclear about the word "explicit" there.

Does it really differentiate from anything implicit?  Although the block
_attribute_ could be considered to implicitly contain set member values 
implied by a blockDefault attribute, for the {substitution group exclusions} 
_property_, the set member values are always explicit defined (by the 
Element Declaration Schema Component representation table in section 
3.3.2).

Is it possible that that occurrence of "explicit" was meant to be some other
word that referred to the individual values that can appear in the set values
of the property (as opposed to the possible set values themselves ({}, 
{restriction}, {extension}, {restriction, extension}))?


Would something like this be better?:

  The value extension or restriction in {substitution group exclusions} 
  rules out element declarations having types whose derivation from {type
  definition} involves any extension steps or any restriction steps 
  respectively.


Daniel

Received on Thursday, 21 February 2008 02:52:37 UTC