W3C home > Mailing lists > Public > xmlschema-dev@w3.org > February 2003

QNames in content

From: Robin Berjon <robin.berjon@expway.fr>
Date: Wed, 19 Feb 2003 12:12:54 +0100
Message-ID: <3E5366B6.4030001@expway.fr>
To: xmlschema-dev@w3.org

Hi,

as noticed recently on www-tag[0], QNames in content aren't consistently used 
accross specs. Some (like XML Schema, 3.15.3.2.2.1) have them use the default 
namespace, others (like XSLT, 2.4) don't.

Question one:

Does the following snippet adequately capture a default-namespace-insensitive 
QName (the regex might be slightly off as I'm not fully familiar with XML Schema 
regexen, but it's "NCName:NCName" to ensure it can only be a QName if it has a 
prefix):

<simpleType>
   <union>
     <simpleType>
       <restriction base='QName'>
         <pattern value='[_\i]([\c]-[:])*:[_\i]([\c]-[:])*'/>
       </restriction>
     </simpleType>
     <simpleType>
       <restriction base='NMTOKEN'/>
     </simpleType>
   </union>
</simpleType>


Question two:

It's too late to decide on only one option and make all specs consistent on this 
point, but wouldn't it be a good idea for a WG (XML Core?) to publish short and 
simple guidelines for when QNames in content are appropriate and when which 
option (defaulting ns or not) is best?


[0]http://lists.w3.org/Archives/Public/www-tag/2003Jan/0096.html

-- 
Robin Berjon <robin.berjon@expway.fr>
Research Engineer, Expway        http://expway.fr/
7FC0 6F5F D864 EFB8 08CE  8E74 58E6 D5DB 4889 2488
Received on Wednesday, 19 February 2003 06:13:26 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 11 January 2011 00:14:36 GMT