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 2433 - {primitive type definition} mapping rule misleading
Summary: {primitive type definition} mapping rule misleading
Status: RESOLVED FIXED
Alias: None
Product: XML Schema
Classification: Unclassified
Component: Datatypes: XSD Part 2 (show other bugs)
Version: 1.1 only
Hardware: PC Windows XP
: P2 normal
Target Milestone: ---
Assignee: C. M. Sperberg-McQueen
QA Contact: XML Schema comments list
URL: http://www.w3.org/XML/Group/2005/09/x...
Whiteboard:
Keywords: resolved
Depends on:
Blocks:
 
Reported: 2005-11-03 12:00 UTC by Henry S. Thompson
Modified: 2005-12-28 01:23 UTC (History)
0 users

See Also:

Attachments

Description Henry S. Thompson 2005-11-03 12:00:38 UTC 
Mapping rules as changed by rec12-map got primitive type defintion wrong
Fix agreed at f2f 2005-09-26
Comment 1 C. M. Sperberg-McQueen 2005-12-28 01:21:38 UTC 
As near as I can tell from the opaque description of this issue,
it was intended to be used to track the decision to recast the
description of the {primitive type definition} mapping in Datatypes
4.1.2.  The wording agreed on in Edinburgh was "If the 
corresponding datatype is ·special· or ·primitive·, then as 
specified in Built-in Simple Type Definitions (§4.1.6), 
otherwise, among the ancestors of this STD, that STD which 
corresponds to a primitive datatype."  

This wording was integrated into the status quo document
on 8 December 2005, so I'm marking this resolved.