[sc34wg3] Almost arbitrary markup in resourceData

Murray Altheim sc34wg3@isotopicmaps.org
Tue, 11 Nov 2003 23:35:53 +0000

Kal Ahmed wrote:
> On Tue, 2003-11-11 at 20:01, Robert Barta wrote:
>>And a TM processor would store it as o DOM o XML fragment o String?
> A TM processor would be required to give you back the content of the
> resourceData element as a String, modulo XML whitespace processing.

Would you have to modify the XML processor to ignore the markup
somehow within specific contexts or use CDATA sections?

I don't know of an XML processor that could do this, and I'd surely
not want to require custom XML processors for XTM. If an XML processor
comes across markup, it parses it as XML unless it's escaped as a
CDATA section. And even if you did escape the XML markup as CDATA,
(i.e., as a String) handing that String off as an XML fragment to an
application, a String that doesn't have any namespace declarations
(since they're part of the markup, not part of escaped markup), doesn't
have a document wrapper or necessarily even a parent wrapper within
its own namespace, well, again, I don't know of an XML processor that
supports processing that. It's clearly not within any of the XML specs.
Paul Grosso has a proposal for fragment interchange, but it doesn't
do this, is a lot more complicated than I'm sure you want, is not yet
supported in any XML processors, and I doubt it'll be widely supported
even when and if it becomes a W3C Recommendation.


Murray Altheim                         http://kmi.open.ac.uk/people/murray/
Knowledge Media Institute
The Open University, Milton Keynes, Bucks, MK7 6AA, UK                    .

   Entitled Continuing Collateral Damage: the health and environmental
   costs of war on Iraq, the report estimates that between 22,000 and
   55,000 people - mainly Iraqi soldiers and civilians - died as a direct
   result of the war.

   Entitled Continuing Collateral Damage? ...a euphemism for BushCo.