OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

tag message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: RE: [tag] Re: Checking Enumerative QNames for the TAML-defined simple values


Hmm, I don't think it is a default namespace problem.  I think it is because
we are not requiring a colon in the QName.

Suggestions:

Under <xs:simpleType name="prescriontLevelBaseCode_type> I suggest that you
use 
  <xs:restriction base="xs:NCName">

Under <xs:simpleType name="codeExtension_type"> do what is needed to require
a colon in the QName using a pattern.  


 - Dennis 

-----Original Message-----
From: stephengreenubl@gmail.com [mailto:stephengreenubl@gmail.com] On Behalf
Of Stephen Green
http://lists.oasis-open.org/archives/tag/200911/msg00067.html
Sent: Sunday, November 15, 2009 09:33
To: dennis.hamilton@acm.org
Cc: TAG TC List
Subject: [tag] Re: Checking Enumerative QNames for the TAML-defined simple
values

Yep, it does work - see latest schema (TAML v1.0.0.3)

http://www.oasis-open.org/committees/download.php/35196/testAssertionMarkupL
anguage-1-0-0-3.xsd

[ ... ]

I note though that the following is also valid (without a prefix):

<testAssertion xmlns="http://docs.oasis-open.org/tag/taml/200911";
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://docs.oasis-open.org/tag/taml/200911
http://www.oasis-open.org/committees/download.php/35196/testAssertionMarkupL
anguage-1-0-0-3.xsd"
id="illustation-1-0" schemaVersionId="1.0.0.3" time="08:39:23.312"
date="2009-11-30">
     <prescription level="deprecated"/>
</testAssertion>

because of XML Schema rules, so the namespace prefix is optional.

I'm not expert enough to know for sure why this is but
I guess it might be because the attribute itself does not need
a namespace declaration; something to do with it automatically
taking the default namespace?? Anyway, that it a bit too geeky
for me to worry me. Just suffice that the namespace and prefix
happen to be optional. The side effect of that is that folk have
to be aware that the schema will not catch typos for the built-in
values; i.e.

[ ... ]



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]