[sc34wg3] Removing added scope from <mergeMap>

[Kal Ahmed]

Which goes back to my point that while mergeMap does not fix everything, =
it
does address a subset of the issue - not only that, but it does so in a =
way
that is both implemented and in use in production systems right now.=20

This is getting circular - I think we have shown the points on both side =
of
the debate, so to summarise:

Added themes on a mergeMap declaration has the advantages of allowing =
you to
identify the provenance of individual topic characteristic assignments. =
Its
major weakness is in subject identity assignment (and resulting merge
behaviour). Source locators provide some of the functionality of an
addedThemes directive but are restricted in that (a) they only identify =
the
topic map source and cannot be used to identify (for example) the source
organization and (b) they would only be generated on topic =
characteristic
assignments that have an ID in the merged topic map - so you are reliant =
on
the source providing those IDs. Furthermore, two users (Murray and Jim) =
have
both said that they use added themes on a mergeMap.

K

> -----Original Message-----
> From: sc34wg3-admin@isotopicmaps.org [mailto:sc34wg3-
> admin@isotopicmaps.org] On Behalf Of Geir Ove Gr=F8nmo
> Sent: 16 January 2006 13:40
> To: sc34wg3@isotopicmaps.org
> Subject: Re: [sc34wg3] Removing added scope from <mergeMap>
>=20
> On 1/16/06, Kal Ahmed <kal@techquila.com> wrote:
> > You can if you have added themes on the merged topic map.
>=20
> Umm. My point was that if  having processed the XTM document with a
> <mergeMap> caused any of the topics in the "mother" topic map to
> merge, then there would be *no* way to unmerge them. You could of
> course get rid of the topic characteristics (except the subject
> identifiers and subject locators) that came from the topic map that
> was merged-in, but you cannot repair any of the damage that happened
> to the topics in the "mother" topicmap.
>=20
> --
> Geir O.
> _______________________________________________
> sc34wg3 mailing list
> sc34wg3@isotopicmaps.org
> http://www.isotopicmaps.org/mailman/listinfo/sc34wg3
>=20