Well, yes, but this is assuming that no other item identifier has the same
format. For instance, suppose the IRI of the topic map is http://foo.com/tm
and we have a topic:
<topic id="x">
<itemIdentity href="http://foo.com/tm#y";>
....
</topic>
we end with two very similar identifiers:
http://foo.com/tm#x and
http://foo.com/tm#y
regards
> -----Original Message-----
> From: Conal Tuohy [mailto:conal.tuohy-O5iVTVtUEt6lVyrhU4qvOw@xxxxxxxxxxxxxxxx]
> Sent: Wednesday, September 19, 2007 11:44 PM
> To: Borislav Iordanov
> Cc: 'TopicMapMail'
> Subject: Re: [topicmapmail] TMDM serialization
>
> On Wed, 2007-09-19 at 22:10 -0400, Borislav Iordanov wrote:
> > Hi,
> >
> > I have a couple of question regarding XML serialization of topics
> maps
> > represented in TMDM 2.0. I'm working on a topic maps implementation
> and I'd
> > like the implementation to be able to read an XMT 2.0 file, store it
> and
> > then export the exact same file. Two questions came while I was
> writing the
> > export part:
> >
> > 1) The id attribute of the topic tag found in the original file gets
> bundled
> > into an item identifier in the TMDM. Given that a topic may have
> multiple
> > item identifiers, how to recover the original id during export?
>
> You say you are exporting "the exact same file". If you can specify the
> URL of that file in your export procedure then you should be able to
> identify which (if any) of the topic's item identifiers refers to a
> topic in that same topicmap document, the document which you are
> exporting into. You can use the fragment identifier from the end of the
> URL as the value for the topic/@id.
>
> Con
>
> --
> Conal Tuohy
> New Zealand Electronic Text Centre
> www.nzetc.org
|
