OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

topicmaps-comment message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Subject: RE: [xtm-wg] Dynamic Generation and Serving of Topic Maps


I agree strongly with Lars here.

The model that gets built from processing (importing and holding a
representation) a topic map is not a DOM.

In order for XPath to perform useful topic map queries on the topic map
serialisation means that the XPath will have to do alot of hopping around in
order to first build the topic map model. I dont think that this will be
pretty.

cheers

Graham


> -----Original Message-----
> From: sentto-1553146-730-973252557-gdm=stepuk.com@returns.onelist.com
> [mailto:sentto-1553146-730-973252557-gdm=stepuk.com@returns.on
> elist.com]
> On Behalf Of Lars Marius Garshol
> Sent: 03 November 2000 11:56
> To: xtm-wg@egroups.com
> Subject: Re: [xtm-wg] Dynamic Generation and Serving of Topic Maps
>
>
>
> * Dave Pawson
> |
> | Whats missing from XSLT/XPATH for queries, which produce XML
> | results?
>
> * Murray Altheim
> |
> | Yes, this was my feeling as well. If XPath and XPointer don't fill
> | the bill, then we're in trouble. I'd think "XTMQL" would be simply a
> | document showing how to perform common XTM queries using XPath and
> | XPointer.
>
> Topic maps and XML have two completely different and unrelated data
> models. Using XPath for topic map queries is going to be terribly
> awkward and not likely to provide the right kinds of functionality at
> all.
>
> Furthermore, XPath does not support updates or deletions, which TMQL
> probably should.
>
> | There shouldn't be much need for anything else. If we're talking
> | about query languages for databases, we're no longer talking about
> | querying topic maps as XML documents, which to me seems waaay out of
> | scope for this activity.
>
> To me it is very difficult to understand how anyone can say this.
> Some topic maps may be XML documents, but that is an entirely
> coincidental and not very interesting fact. I very much doubt that
> any serious topic map applications will be based on topic maps as XML
> documents, but rather on databases.
>
> Furthermore, to TMQL, the actual form in which the topic map happens
> to be stored should not matter at all. To be honest I'm worried to see
> anyone at all thinking differently.
>
> --Lars M.
>
>
> -------------------------- eGroups Sponsor
> -------------------------~-~>
> eLerts
> It's Easy. It's Fun. Best of All, it's Free!
> http://click.egroups.com/1/9699/4/_/337252/_/973252557/
> --------------------------------------------------------------
> -------_->
>
> To Post a message, send it to:   xtm-wg@eGroups.com
>
> To Unsubscribe, send a blank message to:
> xtm-wg-unsubscribe@eGroups.com
>
>
> ______________________________________________________________
> __________
> This message has been checked for all known viruses, by Star
> Internet,
> delivered through the MessageLabs Virus Control Centre.
> For further information visit:
> http://www.star.net.uk/stats.asp
>
>


________________________________________________________________________
This message has been checked for all known viruses, by Star Internet, 
delivered through the MessageLabs Virus Control Centre. 
For further information visit:
http://www.star.net.uk/stats.asp


-------------------------- eGroups Sponsor -------------------------~-~>
eLerts
It's Easy. It's Fun. Best of All, it's Free!
http://click.egroups.com/1/9699/4/_/337252/_/973261985/
---------------------------------------------------------------------_->

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