[sc34wg3] Almost arbitrary markup in resourceData

Robert Barta sc34wg3@isotopicmaps.org
Wed, 12 Nov 2003 06:01:17 +1000

On Mon, Nov 10, 2003 at 08:07:55PM +0100, Lars Marius Garshol wrote:
> OK? If so, what does it mean? Is it OK for <scope> to appear here? For
> <topicMap/>? For <resourceData>?

My first reaction to this would be to use the super-annihilator on
this person, deport his family to Alpha-centaurii and erase every
record of their existence. Everything additional could be regarded as


> This is clearly OK, however:
>   <resourceData>XTM is <xhtml:em>really</xhtml:em>
>   cool.</resourceData>

This would mean that _every_ resource data is now XML and not any more
an opaque sequence of characters? Even images or LaTeX data? Can I
flag that what is NOT xmlish?

And obviously must it be well-formed then to make the whole instance
wf-ed.  But what if I want

       <scope topicRef="#theBegin">
       <resourceData>This is my <x:opening> tag for may fancy application</resourceData>

       <scope topicRef="#theEnd">
       <resourceData>This is my </x:opening> tag for may fancy application</resourceData>

And a TM processor would store it as o DOM o XML fragment o String?

And a TMCL would be able to touch/constrain data in it? What about
TMQL, does it offer now access to this? If not, why not, when that
would be 'standard'?

I find <resourceData/> myself rather inconvenient (fortunately, AsTMa
shields me mostly from the 'niceties' of XML), but this does not look
as if it would get better.

Between the 0% ( = 'dont embed data at all') and 100% (= 'fully embed
data'), <resourceData/> is somewhere around the 1%. This move would
now make it 10%. I would rather prefer a more non-adhoc-ish solution
to be somewhere around 90%, while being clueless how this can/should
be achieved.