[sc34wg3] XTM 1.1 issues: MergeMap

Tue, 13 Dec 2005 08:32:13 -0500

This is a multi-part message in MIME format.

------_=_NextPart_001_01C5FFE9.A1E447DD
Content-Type: text/plain;
 charset=us-ascii
Content-Transfer-Encoding: quoted-printable

Murray,=20
=20
This is my position, too. I use it for modularization. I don't care what =
it's
called; it might as well be <FileInclude> so far as I'm concerned.
=20
Jim
=20
=20
Jim,

I don't think of <mergeMap> as authoring, but a component in =
modularization.
I'm certain that it can be valuable in authoring too, but to me its =
essential
functionality is the ability to create ontological components that can =
be
mixed and matched as needed. The ability to scope the merged Topics is =
also
important in being able to extract the merged set from the soup one has
created.

In my experience, the mergeMap feature in both XTM and LTM has proven
invaluable, as I don't generally deliver a single Topic Map document, I
deliver a set of modules. As such, having an interchange syntax absent
<mergeMap> or #MERGEMAP would seriously hinder the ability to maintain =
the
set of Topic Maps as modules, as I'd then have to perform a pre-merge =
for
delivery and lose the modularity, a feature I'm sure is appreciated by =
those
who don't want the entirety of the package, or want to reuse various
components.

In summary, it helps keep the module soup organized in LTM and XTM. If =
you
like your soup organized... I do. I would guess anyone using Topic Maps =
for
ontology modelling work would too, as monolithic ontologies are pretty
useless.

Murray

......................................................................

Murray Altheim http://www.altheim.com/murray/
<http://www.altheim.com/murray/>=20

Strategic Services Development Manager

The Open University Library and Learning Resources Centre

The Open University, Milton Keynes, Bucks, MK7 6AA, UK .

------_=_NextPart_001_01C5FFE9.A1E447DD
Content-Type: text/html;
 charset=us-ascii
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE></TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.2769" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT face=3DArial =
color=3D#0000ff=20
size=3D2>Murray, </FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2>This is my position, =
too. I use it=20
for modularization. I don't care what it's called; it might as well be=20
&lt;FileInclude&gt; so far as I'm concerned.</FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2>Jim</FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>
<P>Jim,</P>
<P>I don't think of &lt;mergeMap&gt; as authoring, but a component in=20
modularization. I'm certain that it can be valuable in authoring too, =
but to me=20
its essential functionality is the ability to create ontological =
components that=20
can be mixed and matched as needed. The ability to scope the merged =
Topics is=20
also important in being able to extract the merged set from the soup one =
has=20
created.</P>
<P>In my experience, the mergeMap feature in both XTM and LTM has proven =

invaluable, as I don't generally deliver a single Topic Map document, I =
deliver=20
a set of modules. As such, having an interchange syntax absent =
&lt;mergeMap&gt;=20
or #MERGEMAP would seriously hinder the ability to maintain the set of =
Topic=20
Maps as modules, as I'd then have to perform a pre-merge for delivery =
and lose=20
the modularity, a feature I'm sure is appreciated by those who don't =
want the=20
entirety of the package, or want to reuse various components.</P>
<P>In summary, it helps keep the module soup organized in LTM and XTM. =
If you=20
like your soup organized... I do. I would guess anyone using Topic Maps =
for=20
ontology modelling work would too, as monolithic ontologies are pretty=20
useless.</P>
<P>Murray</P>
<P>......................................................................=
</P>
<P>Murray Altheim </FONT><A =
href=3D"http://www.altheim.com/murray/"><U><FONT=20
color=3D#0000ff =
size=3D2>http://www.altheim.com/murray/</U></FONT></A></P><FONT=20
size=3D2>
<P>Strategic Services Development Manager</P>
<P>The Open University Library and Learning Resources Centre</P>
<P>The Open University, Milton Keynes, Bucks, MK7 6AA, UK=20
.</P></FONT></DIV></BODY></HTML>

------_=_NextPart_001_01C5FFE9.A1E447DD--