Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


[xml-dev] Re: Namespace prefix declarations vs DTDs

From: ht@---.--.--.-- (----- -. --------)
To: Bjoern Hoehrmann <derhoermi@---.--->
Date: 5/18/2009 6:30:00 PM
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Bjoern Hoehrmann writes:

>   I would like the XML Conformance Test Suite to cover test cases such
> as these two documents.
>
>   <!DOCTYPE x [ <!ELEMENT x EMPTY> ]>
>   <x xmlns:xml='http://www.w3.org/XML/1998/namespace'/>
>   
>   <!DOCTYPE x [ <!ELEMENT x EMPTY> ]>
>   <x xmlns:foo='http://example.org'/>
>
> The reason for inclusion is that there is confusion as to whether the
> documents are valid. My own reading is that both documents are not
> valid. The libxml2 tool xmllint regards the first as valid but the
> second as invalid. The W3C Markup Validator accepts both as valid.

I agree with your judgement (as does rxp).  Getting them in the test
suite may take a while, see below.

> May I also enquire as to the status of previous submissions, e.g.
>
>   http://lists.w3.org/Archives/Public/public-xml-testsuite/2005Dec/thread.html#msg1

I believe the relevant spec. changes were made in subsequent
editions.  I haven't checked the status of the proposed tests.

>   http://lists.w3.org/Archives/Public/public-xml-testsuite/2006Sep/0000.html

Hmmm.  No discussion.  I'll see what I can do.

> Please let me know if there is anything I can do to ensure their
> timely inclusion.

The only member of the Core WG who regularly maintained the Test Suite
has taken a leave for personal reasons.  W3C staff time constraints
doesn't permit me to spend much time on the test suite, I'm sorry.

Net conclusion: what you can do to help, which would be _very_
welcome, is to join the XML Core WG and take over maintenance of the
Test Suite.

> As an aside, the errata of the first edition of Namespaces in XML
> got broken in September 2007 and has not been fixed since.

Hmm.  The reason for this is obscure == I can't immediately figure out
how to fix it.  I'll get back to you.

ht
- -- 
       Henry S. Thompson, School of Informatics, University of Edinburgh
                         Half-time member of W3C Team
      10 Crichton Street, Edinburgh EH8 9AB, SCOTLAND -- (44) 131 650-4440
                Fax: (44) 131 651-1426, e-mail: ht@i...
                       URL: http://www.ltg.ed.ac.uk/~ht/
[mail really from me _always_ has this .sig -- mail without it is forged spam]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)

iD8DBQFKEajWkjnJixAXWBoRAnv7AJ9WWVGowUhktBFR7qTUp2doHr8STgCfRFV/
NN5L4K+8qduOIInIVFbNQLk=
=wfM5
-----END PGP SIGNATURE-----

_______________________________________________________________________

XML-DEV is a publicly archived, unmoderated list hosted by OASIS
to support XML implementation and development. To minimize
spam in the archives, you must subscribe before posting.

[Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
Or unsubscribe: xml-dev-unsubscribe@l...
subscribe: xml-dev-subscribe@l...
List archive: http://lists.xml.org/archives/xml-dev/
List Guidelines: http://www.oasis-open.org/maillists/guidelines.php



transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent