Dear Alberto and Jesse,

Dunno if you remember me (surely not :-) ). I asked the a.m. question in
March 2006 in this list. I think it is ok, if i give you a catch-up on this
now.

For you to remember, the long story short:
I have had problems with an authorative organization in medical health care
here in germany. They demand to encode some special characters as entities
in the documents they will accept and for which we have to pass a test
procedure. They demand this for the character '>' as well as for some
others. But Xerces won't encode > to > like it do it for the others like
charm. So i asked here for help.

You two answered me, that it is pretty W3C-legal to NOT encode this >
character (the choice is up to the xml-creater as W3C and you said). And so
Xerces won't and will not do it, and this is correct.

But my authority still demands the encoding. So Alberto wrote to me:
<Alberto>So they are accepting documents that they say are XML but refusing
standard XML documents... what do they claim they support?</Alberto> *LOL* I
love this sentence.

I promised, that i'll try to get them (the authority) to the right
direction, but it will take a while (government and authorities have much
time, you know?). And i did as promised. I confronted them with your
opinions and the W3C-Standards and waited what will happen.

AND TODAY! WOHOOO! I got a new version of the specification they demand for
their documents. And look, there i can read: 

<authority-spec-german>
Zu ersetzende Zeichen
> &gt; beide Schreibweisen sind laut W3C-Spezifikation erlaubt
</authority-spec-german>

Translation:
> &gt; both writings are allowed according W3C-Standards

Our Xerces-created XML-Documents have now passed all tests without errors
and we got our approval-number and can start transmitting such documents to
them from our application.

So we have won and surely have enlightened some people there. Like the boy
scouts motto "Every day a good deed" :-)

Thanks again for supporting me in this case.

CU
Jörg


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to