[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: RE: [xtm-wg] Merging proposals uploaded
>to be useful you still need to be able to make >globally (in the scope of xtmdoc) unique identifiers Yes. my question was, how does your mechanism cope with the case where two distinct maps from different contexts both refer to id="/foo/bar.xtm#ab4756" by pure accident ? you have to look at the contexts of the two TMs whatever, don't you? Peter -----Original Message----- From: Kal Ahmed [mailto:kal@ontopia.net] Sent: 19 October 2000 15:49 To: xtm-wg@egroups.com Subject: RE: [xtm-wg] Merging proposals uploaded Yes...well, sort of yes - to be useful you still need to be able to make globally (in the scope of xtmdoc) unique identifiers, and to resolve references between packaged topic maps (without requiring the package reader to go to the original source of the packaged tm). Hence the modifications to the content model of xtmdoc. I think that with these modifications (or something like them), what you want to do will be possible and I can think of usecases where such a facility would be useful. I think my real point is that **without** those modifications, you would not be really solving the packaging problem. Kal PS I can see techquila.com becoming a 'topic map merging service' ... send me your packages and I'll send you a single merged tm. Now I just have to work out a pricing structure ;-) > -----Original Message----- > From: Sam Hunting [mailto:sam_hunting@yahoo.com] > Sent: 19 October 2000 15:23 > To: xtm-wg@egroups.com > Subject: RE: [xtm-wg] Merging proposals uploaded > > > [kal writes] > > 3) A proposal for handling xtmdoc. ... [T]here is also a need for > > ensuring that the packaging and unpackaging can actually be done > > simply. ... BTW, I feel that packaging tms is a really weak argument > > considering that the merging and scoping mechanisms can be trivially > > combined to do tm packaging > > Packaging into xtmdoc is wicked simple, because it could be done with > an XML editor, or even a text editor. One could, of course, use the > usual entity mechanisms. > > Contrariwise, packaging TM with a scoping and merging mechanism is not > wicked simple, because it cannot be done with an XML editor or text > editor. > > Alternatively, I'm missing some subtle point obvious to all but me. > > S. > > > > > ===== > <? "To imagine a language is to imagine a form of life." > -- Ludwig Wittgenstein, Philosophical Investigations ?> > > __________________________________________________ > Do You Yahoo!? > Yahoo! Messenger - Talk while you surf! It's FREE. > http://im.yahoo.com/ > > > To Post a message, send it to: xtm-wg@eGroups.com > > To Unsubscribe, send a blank message to: xtm-wg-unsubscribe@eGroups.com > > > To Post a message, send it to: xtm-wg@eGroups.com To Unsubscribe, send a blank message to: xtm-wg-unsubscribe@eGroups.com -------------------------- eGroups Sponsor -------------------------~-~> Your family still won't know what you do. At least they'll know where. The resources, brainpower & breadth of opportunities at Microsoft are unmatched. The only question is are you ready for that kind of impact? http://click.egroups.com/1/9223/4/_/337252/_/971967325/ ---------------------------------------------------------------------_-> To Post a message, send it to: xtm-wg@eGroups.com To Unsubscribe, send a blank message to: xtm-wg-unsubscribe@eGroups.com
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC