Hi,

On 8/3/06, Frederick Giasson wrote:
>
> Hi guys,
>
> Recently I talked with Alex to ask him if he could be interested in making his
> SIOC Browser interacting with Talk Digger. In fact, the next version of Talk
> Digger, currently in alpha testing, will generate a SIOC document for each
> conversation page.
>
> Currently Alex’s SIOC explorer is crawling and indexing some blogs that
> has the
> Wordpress (b2Evolution too?) SIOC exporter plugin.

Actually, the browser is just a front-end to any SPARQL store.
What I've done with it is:
- Use Uldis crawler to get SIOC content from different sources;
- Put all the data in a RDF stote;
- Put the browser as a frontend of the store

> What I suggested him was to let his browser crawl Talk Digger’s SIOC data
> as
> well.
>
> A couple of days ago, Uldis received the acceptance of his speech at the
> BlogTalk Reloaded conference. Their job (because he is not alone in the boat)
> is to merge all the current SIOC browsers into a unique one for the
> presentation (at least it is what I understood).
>
> As people know, the idea behind the SIOC ontology is to link online communities
> together. So the idea is the present information, in the same environment (a
> SIOC browser in the present case), from many different sources/types of
> communities.
>
> So what I would suggest is to start thinking about a way to let Talk Digger
> ping the SIOC browser when new SIOC data is available from Talk Digger for the
> browser.

Indeed, we should get a way to link between the plaform(s) that will
crawl / store SIOC data and the ones that create some, so that stores
will be up-to-date.

> At first, I could create a list of links where data could be crawled, and later
> we could think about a more automatic/permanent way to let them interact
> together. At first I thought about a simple pinging system using XML-RPC (like
> all the new search engines pinging systems). But any other methods could work
> as well.

An RDF file containing recently created links could be good to start:
a cron could fetch it and get only new URLs using incremental crawler,
then we'll put data it in the store.
A ping service will be nicer, but longer to implement I think, so we
can start with this list.

> So let me know if you could be interested, if it is a good idea, and how/when
> it could be done.

Let's start with it :)
What you could do first is to create this URLs page, so we can try the
crawler and its incremental functions on it to see if we fetch the
data as aspected.

In the meanwhile, we'll work on the browser with Uldis, so we can
think on specific queries for TalkDigger.

Best,

Alex.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "SIOC-Dev" group.
To post to this group, send email to sioc-dev@googlegroups.com
To unsubscribe from this group, send email to sioc-dev-unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sioc-dev
-~----------~----~----~----~------~----~------~--~---