W3C home > Mailing lists > Public > www-xml-schema-comments@w3.org > July to September 2009

[Bug 7366] New: Support JCnQName type

From: <bugzilla@wiggum.w3.org>
Date: Wed, 19 Aug 2009 07:59:25 +0000
To: www-xml-schema-comments@w3.org
Message-ID: <bug-7366-703@http.www.w3.org/Bugs/Public/>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=7366

           Summary: Support JCnQName type
           Product: XML Schema
           Version: 1.1 only
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Datatypes: XSD Part 2
        AssignedTo: David_E3@VERIFONE.com
        ReportedBy: petexmldev@codalogic.com
         QAContact: www-xml-schema-comments@w3.org
                CC: cmsmcq@blackmesatech.com


Discussions on the xml-dev mailing list have suggested that the use of QNames
can be problematic, especially when they become disassociated with the
documents thay were initially contained in (due to namespace prefix mappings
being lost).

One way to address this is to use James Clark notation qualified names (e.g.
{http://www.w3.org/2001/XMLSchema}element ) rather than QNames that rely on
prefixes.

A James Clark notation qualified name suggests a type name of JCnQName.  Other
suggested names are Explicitly Qualified Name (EQName), and Canonically
Qualified Name (CQName).

The expectation is that this change won't make it into datatypes 1.1., but this
entry will formally record it as an input to datatypes 1.2.


-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Wednesday, 19 August 2009 07:59:35 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:50:10 UTC