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 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?
The XML Management Company
+31 (0)20 750 7582 / +31 (0)6 55 347 448 /
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
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