FW: [topicmapmail] Should resourceData have a MIME type?

Mon, 13 Jan 2003 17:01:33 -0500

Paul,

What you are doing with basenamestring corresponds to
the original intent of the variant name element with
the parameter value of display.
In the first syntax of Topic Maps (HyTm) there was an
element called <displayName> distinct from <baseName>.
In XTM, <displayName> has been generalized into variant,
therefore you have to put it in the parameter.

The original intent of <baseNameString> was to enable
merging based on names (with scopes). There has been
recently a lot of discussions as to we should get rid
of the name-based merging rule. If basename is not used
any more for merging, it becomes artificial to try to
distinguish baseName from variant. This might explain why
your question, in the current state of affairs, is pointing
to a real issue which has not been completely solved yet.
I believe we need to elaborate further on the mechanism
for expressing merging rules. When this will be done, then
the difference between basename and display-variant name
will be clear again and I think the answer to your question
will be: don't do that, because there are other uses for
basename if you want to interchange your topic map with others
that you won't be able to do if you mix it with all this
formatting.

I hope this helps.

Michel

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Michel Biezunski
Coolheads Consulting
402 85th Street #5C
Brooklyn, New York 11209
Email:mb@coolheads.com
Web  :http://www.coolheads.com
Voice: (718) 921-0901
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D
=20

> -----Original Message-----
> From: topicmapmail-admin@infoloom.com
> [mailto:topicmapmail-admin@infoloom.com]On Behalf Of Paul Goldstein
> Sent: Monday, January 13, 2003 12:29 PM
> To: Murray Altheim; topicmapmail@infoloom.com
> Subject: Re: [topicmapmail] Should resourceData have a MIME type?
>=20
>=20
> Maybe I'm missunderstanding the spec, but is this not allowed?:
> <topic id=3D"test">
>     <baseName>
>         <baseNameString>Hello this is a &lt;test&gt;</baseNameString>
>     </baseName>
> </topic>
> </topicMap>
>=20
> And you want to let your application know that the baseNameString =
needs=20
> to be processed so that the character entities are transformed to html =

> markup characters.
>=20
> If I'm totally off the point, let me know. Perhaps someone could send =
me=20
> some examples what they were talking about with the resourceData =
element.
>=20
> By the way the following is pretty absurd, but validates with XML spy. =

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

> )}}{\*\pnseclvl8\pnlcltr\pnstart1\pnindent720\pnhang
> {\pntxtb (}{\pntxta=20
> )}}{\*\pnseclvl9\pnlcrm\pnstart1\pnindent720\pnhang{\pntxtb (}{\pntxta =

> )}}\pard\plain \ql=20
> \li0\ri0\widctlpar\aspalpha\aspnum\faauto\adjustright\rin0\lin0\itap0=20
> \fs24\lang1033\langfe1033\cgrid\langnp1033\langfenp1033 {
> Hello this is a Test
> \par }}</baseNameString>
>     </baseName>
> </topic>
> </topicMap>
>=20
> -Paul G.
>=20
>=20
>=20
> Murray Altheim wrote:
>=20
> > Paul Goldstein wrote:
> >
> >> Not to be annoying, but doesn't this problem apply to =
baseNameString=20
> >> as well? I mean its perfectly allowable to include html as part of=20
> >> 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=20
> >> baseNameString seems like it has the same problem as resourceData. =
I=20
> >> don't think the fact that baseName includes variant elements really =

> >> solves the problem, you still may want to put html or other =
formatted=20
> >> 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
> >
>=20
> --=20
> Paul Goldstein
> Senior Systems Developer
> Time Inc.
> 212-522-0565
> pgoldstein@timeinc.net
>=20
>=20
>=20
> _______________________________________________
> topicmapmail mailing list
> topicmapmail@infoloom.com
> http://www.infoloom.com/mailman/listinfo/topicmapmail
>=20