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 3850 - Two definitions of "constraining facet(s)"
Summary: Two definitions of "constraining facet(s)"
Status: RESOLVED FIXED
Alias: None
Product: XML Schema
Classification: Unclassified
Component: Datatypes: XSD Part 2 (show other bugs)
Version: 1.1 only
Hardware: Macintosh All
: P2 normal
Target Milestone: ---
Assignee: C. M. Sperberg-McQueen
QA Contact: XML Schema comments list
URL:
Whiteboard: thimble, easy
Keywords:
Depends on:
Blocks:
 
Reported: 2006-10-19 02:06 UTC by Dave Peterson
Modified: 2008-06-16 14:36 UTC (History)
0 users

See Also:


Attachments

Description Dave Peterson 2006-10-19 02:06:15 UTC
In section 4.3 there is a definition of "constraining facets" (plural) and a separate definition of "constraining facet" (singular).  We shouldn't do this unless the plural is indeed meant to mean something different from more than one of the singular.  In this case, the plural definition really tells what a constraining facet is, and the singular simply adds that all constraining facets are defined in the spec; no others may be added by users.

Suggest we delete the second definition and either add the fact that all are defined in 4.3 to the plural definition or add it as an additional non-definition sentence.
Comment 1 Dave Peterson 2006-11-18 02:27:03 UTC
Approved by the WG; awaiting incorporation into the status quo document.

Specifically, the WG directed the editors to delete the last para in 4.3 proper (before 4.3.1), "The term [Definition:] Constraining Facet refers to any of the components defined in this section." and add in the first para before the sentence beginning "For example...":

      All constraining facet components are defined in this section.
Comment 2 Dave Peterson 2007-02-25 17:57:06 UTC
(In reply to comment #1)
> Approved by the WG; awaiting incorporation into the status quo document.

While making the incorporation, I discovered that the identical problem exists for fundamental facets.  (I was fixing it in one place, looking in the other place in the XHTML, and wondering why the fix didn't show.)  On my own cognizance, I have made the corresponding change for fundamental facets as well.
Comment 3 C. M. Sperberg-McQueen 2007-09-18 00:40:03 UTC
The change proposed above was approved by the WG in its call of 
17 November 2006.  It is now reflected in the status quo version 
of the Datatypes spec.  Accordingly, I am setting the disposition of 
this issue to RESOLVED / FIXED.

If the originator of the issue would examine the change and let 
us know whether it satisfactorily resolves the problem or not, 
we'd be grateful.   To signal that the resolution is acceptable, 
change the status of the issue to CLOSED.  Otherwise, to signal 
that it's NOT acceptable, change the status to REOPENED (and 
tell us what's wrong).

If we don't hear from you in the next three weeks, we'll assume 
that silence betokens consent, and close the issue ourselves.   
Comment 4 C. M. Sperberg-McQueen 2008-06-16 14:36:05 UTC
Postscript:  link-checking the documents (for the first time in several
months) shows that the text deleted as described in comment #1 and
comment #2 was providing the hypertext anchor for generic references to
constraining and fundamental facet components.  So the change made broke
the links.  Moral 1:  the editors' analysis of the situation here was too
quick and overlooked salient points.  Moral 2:  the status-quo documents
need to be validated and link-checked more frequently, to catch problems
like this more quickly.