Worse, actually. Just about all of them use that namespace. =
Unfortunately,
none of them have it as targetNamespace.

-----Original Message-----
From: Michael Kay [mailto:michael.h.kay@[...].com]
Sent: 04 March 2002 15:15
To: 'Nicolas LEHUEN'; Anderson, John; xml-dev@[...].org
Subject: RE: [xml-dev] A good case for namespace URIs



-----Original Message-----
From: Nicolas LEHUEN [mailto:nicolas.lehuen@[...].com]
Sent: 04 March 2002 13:44
To: 'Anderson, John'; 'xml-dev@lists.xml.org'
Subject: RE: [xml-dev] A good case for namespace URIs


http://www.google.com/search?sourceid=3Dnavclient
<http://www.google.com/search?sourceid=3Dnavclient&q=3Dgovtalk+schema> 
&q=3Dgovtalk+schema
=20
This is a good namespace URI, too ;).
=20
From there you promptly get to
<http://www.govtalk.gov.uk/interoperability/draftschema.asp> 
http://www.govtalk.gov.uk/interoperability/draftschema.asp , and from =
there
to hundreds of pages of schema documentation.=20
=20
=20
... none of which appears to use the namespace
<http://www.govtalk.gov.uk/CR/core>  http://www.govtalk.gov.uk/CR/core
(unless you strike lucky). Which rather proves John Anderson's original
point.
=20
Mike Kay
=20

-----Message d'origine-----
De : Anderson, John [mailto:John@[...].com]
Envoy=E9 : lundi 4 mars 2002 13:38
=C0 : xml-dev@[...].org
Objet : [xml-dev] A good case for namespace URIs




I've just hit a problem which would seem to present a very strong case =
for
*using* namespace URIs (maybe even with RDDL), at least until some =
formal
spec comes along. And I'd be pretty confident I'm not the only one.

I am trying to develop some stuff against the UK govtalk schemas, and =
they
reference elements and attributes in the =
http://www.govtalk.gov.uk/CR/core
<http://www.govtalk.gov.uk/CR/core>   namespace.

Has anybody ever tried to find a schema describing this namespace on =
the
govtalk website? I spent hours yesterday. Wouldn't it have been really,
really nice if that URI didn't result in a 404. It would also be quite =
easy,
wouldn't even have to be a RDDL document - since everything is done in =
XSD,
just the schema would have been quite satisfactory. In fact, even a
not-valid-XML text document with all possible permutations of that =
namespace
(if they do the XHTML thing) would have been a good start.

I know there are all kinds of sound academic arguments for not doing =
this,
but in the meantime they prohibit a simple and very practical aid to my
work.

BTW, if anyone does have a copy of this schema, could they please send =
it to
me?=20

_______________________________________________________
John Anderson=20
CTO BarbadosoftTM=20
The XML Management Company=20
+31 (0)20 750 7582 / +31 (0)6 55 347 448 / www.barbadosoft.com=20




The information transmitted by this e-mail message is intended solely =
for
the use of the person to whom or entity to which it is addressed. The
message may contain information that is privileged and confidential.
Disclosure, dissemination, distribution, review, retransmission to, =
other
use of or taking any action in reliance upon this information by anyone
other than the intended recipient is prohibited. If you are not the =
intended
recipient, please do not disseminate, distribute or copy this =
communication,
by e-mail or otherwise. Instead, please notify us immediately by return
e-mail (including the original message with your reply) and then delete =
and
discard all copies of the message.

Although we have taken precautions to minimize the risk of transmitting
viruses we nevertheless advise you to carry out your own virus checks =
on any
attachment to this message. We accept no liability for any loss or =
damage
caused by viruses.

--------------InterScan_NT_MIME_Boundary--


The information transmitted by this e-mail message is intended solely =
for
the use of the person to whom or entity to which it is addressed. The
message may contain information that is privileged and confidential.
Disclosure, dissemination, distribution, review, retransmission to, =
other
use of or taking any action in reliance upon this information by anyone
other than the intended recipient is prohibited. If you are not the =
intended
recipient, please do not disseminate, distribute or copy this =
communication,
by e-mail or otherwise. Instead, please notify us immediately by return
e-mail (including the original message with your reply) and then delete =
and
discard all copies of the message.

Although we have taken precautions to minimize the risk of transmitting
viruses we nevertheless advise you to carry out your own virus checks =
on any
attachment to this message. We accept no liability for any loss or =
damage
caused by viruses.