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 5073 - Use of term simple ur-type
Summary: Use of term simple ur-type
Status: RESOLVED FIXED
Alias: None
Product: XML Schema
Classification: Unclassified
Component: Structures: XSD Part 1 (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: http://www.w3.org/TR/2007/WD-xmlschem...
Whiteboard: terminology cluster
Keywords: editorial, resolved
Depends on:
Blocks:
 
Reported: 2007-09-26 00:08 UTC by Xan Gregg
Modified: 2008-05-09 19:52 UTC (History)
0 users

See Also:

Attachments

Description Xan Gregg 2007-09-26 00:08:42 UTC 
I'm happy to see that the term "ur-type" has be superseded by "anyType" in XML Schema 1.1. Please make the corresponding replacement of "simple ur-type" with "anySimpleType".
Comment 1 C. M. Sperberg-McQueen 2008-05-08 00:34:21 UTC 
A wording proposal to change occurrences of 'the simple ur-type
definition' to 'xs:anySimpleType', and reformulate the definition
of the term accordingly, has been prepared and is at

  http://www.w3.org/XML/Group/2004/06/xmlschema-1/structures.urtype.200611.html
  (member-only link)

awaiting review by the WG.
Comment 2 C. M. Sperberg-McQueen 2008-05-09 19:52:26 UTC 
The proposal mentioned in comment #1 was adopted by the working group
on today's call.  With that, we believe this issue to have been resolved,
and I'm setting the status of the record to say that.

Xan, thank you very much for the comment.  When we next publish a
working draft of the document, we hope that you will review the text
of the document and confirm that the issue has been resolved to your
satisfaction.  (I'd attach a copy to the bug but it's kind of big and I
don't want to saddle Bugzilla with a lot of copies of the XSD spec
in varying states of revision.)  If at that time you are happy with the
resolution, please signal so by changing the status of this issue to 
CLOSED; otherwise, please let us know what's wrong and change it to
REOPENED.  If we don't hear from you within two weeks or so of publishing
the next working draft, we will assume that you are satisfied.   (In a
perfect world, I'll remember to update this bug report or send you offline
email to signal the availability of the text, but I don't want to promise
that.)