Re: Topic Maps for Drupal

Patrick Durusau <patrick-Q/[email protected]>
Newsgroups gmane.text.xml.xtm.general
Message-ID <[email protected]>
Jan,

On Mon, 2010-10-04 at 15:01 +0200, Jan Schreiber wrote:
> Patrick,
> 
> 
> I agree with you. A blog harvester makes it easier to integrate blogs
> (no user administration required). It also allows us to integrate
> certain categories of a blog into the planet feed (otherwise we would
> have a lot of beer tasting posts, I guess).
> Planet Topic Maps seems a good place for harvesting blogs.
> Maybe something like topicmaps.org/planet or planet.topicmaps.org
> would be an alternative to http://topicmaps.bouvet.no/planet/, but,
> hey, good URIs never change.


I would be happy with http://topicmaps.bouvet.no/planet/ as the top link
in my blog roll with something like: "TM Blog Harvester" as my local
title for it. 

But then I am not selling ads on my site. ;-)

More seriously, the stability of URIs is a fiction. TBL talks about URIs
being stable for 10 to 15 years. What a joke. That isn't even an entire
generation. (in the US, about 25 years). 

Sure, URIs are useful, but let's remember that some use cases are more
than tomorrow's dentist appt. or a tennis match. 

Ex. The work at Y-12 (where they build things that go boom) requires
records that will persist and be useful for 50 years. Including how to
build any tools that may be needed. (Not that is documentation.)

Ex. Social Security (US) where they have records of all contributions
into the system since the 1930's. 

Ex. The Vatican, which has reliable records at least back to the 8th
century, probably earlier (that is from memory).

And the list goes on and on. 

Yes, URIs are useful, but they aren't every going to be applied to all
data, electronic or otherwise. 

Moreover, if you are planning in terms of decades, present URIs aren't a
good bet. Or at least by themselves. Leave room for newer forms of
identification. (as with using a topic map)

Hope you are having a great day!

Patrick


> 
> - Jan
> 
> 
> 
> On 4. okt. 2010, at 14.51, Patrick Durusau wrote:
> 
> > Robert,
> > 
> > On Mon, 2010-10-04 at 14:39 +0200, Robert Cerny wrote:
> > > Can't we have one blog for all topic mappers? I would contribute.
> > 
> > 
> > Feeding into a blog harvester I suspect would be easier.
> > 
> > Yes?
> > 
> > Not objecting to the idea of a single blog but managing logins, etc.
> > puts a management burden on someone. And deciding who gets one, and
> > so
> > on. 
> > 
> > Hope you are having a great day!
> > 
> > Patrick
> > 
> > 
> > > Best,
> > > 
> > > Robert
> > > 
> > > Am 04.10.2010 um 14:32 schrieb Lars Heuer:
> > > 
> > > > [...]
> > > > > > Hmmm... maybe I should create a blog and stop bothering the
> > > > > > mailing
> > > > > > list ;)
> > > > 
> > > > > While I can't think of any good reason why you shouldn't have
> > > > > a
> > > > > blog, I wouldn't call this "bothering the list". :)
> > > > 
> > > > Ah, fishing for compliments works, actually. ;) Thanks :)
> > > > 
> > > > Best regards,
> > > > Lars
> > > > -- 
> > > > Semagia
> > > > <http://www.semagia.com>
> > > > 
> > > > <https://twitter.com/larsheuer> @Twitter
> > > > <http://www.topicmaps.de/mailinglist/> German Topic Maps mailing
> > > > list
> > > > <http://tinytim.sourceforge.net/> Open Source Topic Maps engine
> > > > <http://mappa.semagia.com/> Mappa - Python Topic Maps engine
> > > > _______________________________________________
> > > > topicmapmail mailing list
> > > > topicmapmail-Zo64W7twoUFWk0Htik3J/[email protected]
> > > > http://www.infoloom.com/mailman/listinfo/topicmapmail
> > > _______________________________________________
> > > topicmapmail mailing list
> > > topicmapmail-Zo64W7twoUFWk0Htik3J/[email protected]
> > > http://www.infoloom.com/mailman/listinfo/topicmapmail
> > _______________________________________________
> > topicmapmail mailing list
> > topicmapmail-Zo64W7twoUFWk0Htik3J/[email protected]
> > http://www.infoloom.com/mailman/listinfo/topicmapmail
> > 
> 
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.