[sc34wg3] Almost arbitrary markup in resourceData

[Dmitry]

I personally see a lot of benefits in including XML fragments into Topic
Maps.

I would like to concentrate more on specific suggestions:

TMDM:
Define additional property for occurrence item: encoding type.
Encoding type is enumeration:
. Base64,
. XML,
. PCDATA

Also define property "namespaces" which will keep track of namespaces inside
inline occurrences with XML encoding

TMQL:
TMQL should be able to return inline occurrences of these encoding types.
TMQL should allow 'to ask' about encoding types of specific occurrences

TMCL:
TMCL should be able to constraint possible encoding types for specific
occurrence types.

XTM:
. Allow to define foreign namespaces in topicMap tag.
. Introduce new tag  <baseNameXML> and allow to define foreign namespaces in
it.
. Introduce new tag  <resourceXML> and allow to define foreign namespaces in
it.
. Introduce new tag  <resourceBase64>

XTM deserialization
During  XTM deserialization'global' foreign namespaces should be copied to
each occurrence object with XML encoding.

Merging of inline occurrences with XML encoding
Based on Infoset.


I think also that it is important to have ability to reference topics from
regular XML documents. XTM namespace is just overkill for that. I would
probably suggest defining small specification which is analog of XLink,
something like TMLink or TMRef.

This specification will allow authors explicitly reference topics during XML
authoring. Something like this:
<city tmref:ref=http://www....#paris tmref:type="
http://www....#general-city-information" >Paris</city>


Dmitry