This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
ACTION 20050809-06: Editors to (a) Define "ancestor" (non-reflexively) (b) use it to {define primitive type definition} property (c) get rid of the definition of "type derived from" or align with definition for simple types.
I've drafted a resolution to (a) and (b) above, distribution to the WG is pending agreement about mechanics with the other editors. I believe Michael and DaveP have to decide what to do about (c).
I note that in HT's draft wording, the definition of "derived from" for simple type( definition)s has been eliminated. I think we can live with that, although if we later discover that we need the term, we can resurrect it. (If we do, though, we should align it with the definition of the term "derived from" for datatypes, which appears in section 2.
A definition of ancestor was included in the omnibus proposal sent to the Working Group 31 August 2005; the relevant parts of the proposal were approved in September 2005. They have now been integrated into the status quo document, so I am marking this issue resolved. I do not know whether this marks the last remaining thing to do on bug 1852 or not, so I am leaving bug 1852 untouched for now.
(In reply to comment #3) > A definition of ancestor was included in the omnibus proposal > sent to the Working Group 31 August 2005; the relevant parts of > the proposal were approved in September 2005. They have now > been integrated into the status quo document, so I am marking > this issue resolved. I had the feeling that the intent of this requirement was not only to introduce the term but also to go through the document to see if there are other places where it can be used to simplify wording that was correct but convoluted. I wonder if Henry actually has made such a pass.
Since really the WG introduced this bug, and no one has complained about the resolution in over a year, I'm marking it closed.