[topicmapmail] Should resourceData have a MIME type?

[Paul Goldstein]

Maybe I'm missunderstanding the spec, but is this not allowed?:
<topic id="test">
    <baseName>
        <baseNameString>Hello this is a &lt;test&gt;</baseNameString>
    </baseName>
</topic>
</topicMap>

And you want to let your application know that the baseNameString needs 
to be processed so that the character entities are transformed to html 
markup characters.

If I'm totally off the point, let me know. Perhaps someone could send me 
some examples what they were talking about with the resourceData element.

By the way the following is pretty absurd, but validates with XML spy. 
It has baseNameString as richtext format:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE topicMap SYSTEM "C:\work\topicmap\xtm1.dtd">
<topicMap>
<topic id="test">
    <baseName>
        <baseNameString>{\rtf1\ansi\ansicpg1252\uc1 
\deff0\deflang1033\deflangfe1033{\fonttbl{\f0\froman\fcharset0\fprq2{\*\panose 
02020603050405020304}Times New Roman;}{\f29\froman\fcharset238\fprq2 
Times New Roman CE;}{\f30\froman\fcharset204\fprq2 Times New Roman Cyr;}
{\f32\froman\fcharset161\fprq2 Times New Roman 
Greek;}{\f33\froman\fcharset162\fprq2 Times New Roman 
Tur;}{\f34\froman\fcharset177\fprq2 Times New Roman 
(Hebrew);}{\f35\froman\fcharset178\fprq2 Times New Roman (Arabic);}
{\f36\froman\fcharset186\fprq2 Times New Roman 
Baltic;}}{\colortbl;\red0\green0\blue0;\red0\green0\blue255;\red0\green255\blue255;\red0\green255\blue0;\red255\green0\blue255;\red255\green0\blue0;\red255\green255\blue0;\red255\green255\blue255;
\red0\green0\blue128;\red0\green128\blue128;\red0\green128\blue0;\red128\green0\blue128;\red128\green0\blue0;\red128\green128\blue0;\red128\green128\blue128;\red192\green192\blue192;}{\stylesheet{
\ql 
\li0\ri0\widctlpar\aspalpha\aspnum\faauto\adjustright\rin0\lin0\itap0 
\fs24\lang1033\langfe1033\cgrid\langnp1033\langfenp1033 \snext0 
Normal;}{\*\cs10 \additive Default Paragraph Font;}}{\info{\title Hello 
this is a Test}{\author Time User}
{\operator Time 
User}{\creatim\yr2003\mo1\dy13\hr12\min26}{\revtim\yr2003\mo1\dy13\hr12\min26}{\version2}{\edmins3}{\nofpages1}{\nofwords0}{\nofchars0}{\*\company 
Time Inc.}{\nofcharsws0}{\vern8299}}
\widowctrl\ftnbj\aenddoc\noxlattoyen\expshrtn\noultrlspc\dntblnsbdb\nospaceforul\formshade\horzdoc\dgmargin\dghspace180\dgvspace180\dghorigin1800\dgvorigin1440\dghshow1\dgvshow1
\jexpand\viewkind1\viewscale95\pgbrdrhead\pgbrdrfoot\splytwnine\ftnlytwnine\htmautsp\nolnhtadjtbl\useltbaln\alntblind\lytcalctblwd\lyttblrtgr\lnbrkrule 
\fet0\sectd \linex0\endnhere\sectlinegrid360\sectdefaultcl {\*\pnseclvl1
\pnucrm\pnstart1\pnindent720\pnhang{\pntxta 
.}}{\*\pnseclvl2\pnucltr\pnstart1\pnindent720\pnhang{\pntxta 
.}}{\*\pnseclvl3\pndec\pnstart1\pnindent720\pnhang{\pntxta 
.}}{\*\pnseclvl4\pnlcltr\pnstart1\pnindent720\pnhang{\pntxta 
)}}{\*\pnseclvl5
\pndec\pnstart1\pnindent720\pnhang{\pntxtb (}{\pntxta 
)}}{\*\pnseclvl6\pnlcltr\pnstart1\pnindent720\pnhang{\pntxtb (}{\pntxta 
)}}{\*\pnseclvl7\pnlcrm\pnstart1\pnindent720\pnhang{\pntxtb (}{\pntxta 
)}}{\*\pnseclvl8\pnlcltr\pnstart1\pnindent720\pnhang
{\pntxtb (}{\pntxta 
)}}{\*\pnseclvl9\pnlcrm\pnstart1\pnindent720\pnhang{\pntxtb (}{\pntxta 
)}}\pard\plain \ql 
\li0\ri0\widctlpar\aspalpha\aspnum\faauto\adjustright\rin0\lin0\itap0 
\fs24\lang1033\langfe1033\cgrid\langnp1033\langfenp1033 {
Hello this is a Test
\par }}</baseNameString>
    </baseName>
</topic>
</topicMap>

-Paul G.



Murray Altheim wrote:

> Paul Goldstein wrote:
>
>> Not to be annoying, but doesn't this problem apply to baseNameString 
>> as well? I mean its perfectly allowable to include html as part of 
>> your baseNameString, not that I've ever seen it done.
>
>
>
> I'm not sure what you're referring to -- in XTM there are no allowed
> inclusions of other namespace'd markup (other than XLink as specified).
>
>
>> If we are not going to allow scope to solve the problem, then 
>> baseNameString seems like it has the same problem as resourceData. I 
>> don't think the fact that baseName includes variant elements really 
>> solves the problem, you still may want to put html or other formatted 
>> data in baseNameString (although I don't think I would).
>
>
>
> You point out the error in approaching this specific instance of
> MIME type: there are *many* potential metadata needs out there, so
> why limit things to MIME type? Why not just open up the floodgates
> and allow all manner of markup in XTM? A: Then nobody could reliably
> intercommunicate XTM documents.
>
> Sorry to be so grumpy about this, but I've seen many simple and
> functional technologies made similarly complex, unimplementable,
> and proprietary by acceding to the demands of every project's
> individual needs. I'm very wary of all the proposals to extend
> XTM simply because it currently (IMO) hits the 80/20 point in
> its design, and (again, IMO) we're now hearing from the other 20%.
>
> Murray
>
> ......................................................................
> Murray Altheim                  <http://kmi.open.ac.uk/people/murray/>
> Knowledge Media Institute
> The Open University, Milton Keynes, Bucks, MK7 6AA, UK
>
>      In the evening
>      The rice leaves in the garden
>      Rustle in the autumn wind
>      That blows through my reed hut.  -- Minamoto no Tsunenobu
>
> _______________________________________________
> topicmapmail mailing list
> topicmapmail@infoloom.com
> http://www.infoloom.com/mailman/listinfo/topicmapmail
>

-- 
Paul Goldstein
Senior Systems Developer
Time Inc.
212-522-0565
pgoldstein@timeinc.net