Re: Consolidating RDF XML data with different ids

Hi there. There are many good suggestions here. I appreciate the time 
taken to repy to this post. It gives me some ideas about how I might 
proceed with this.

At this point, it has left me attempting to answer a bigger question 
now. Whether to consolidate the rdf into a single store or simply index 
the rdf with a full text search and not try quering against a 
consolidated store at all.

It may be faster and less expensive for query time than the alternative 
and perhaps less complicated that trying to determine all the possible 
permutations of equivalent data. If I went this way it seems somewhat 
regressive however, since I felt rdf could really help pull this 
information together a bit more easily. I essentially have all the 
information as triples conforming to the same schema. It is ironic in a 
way that rdf is perhaps the best index in the world yet I am considering 
something outside of rdf for pulling the data together.

Regards
David


Jeremy Carroll wrote:
> 
> Hans Teijgeler wrote:
> 
>> It turns out that some vendors are more descriptive (using more
>> properties in the schema) than others. When I consolidate, I would
>> really like to combine the efforts of the vendors so that my part
>> information in my national data store is as comprehensive as possible.
>>
>> [HT] You can only safely consolidate that IFF the more and the less 
>> described classes are *really* the same. In that case use 
>> owl:equivalentClass [2]
>>
> 
> This seems to get to the heart of at least one issue:
> 
> A purist approach worries a lot about identity and equivalence.
> 
> A more practical approach is concerned with utility. If it is useful to 
> assert that two classes are equivalent, then maybe do it, but be aware 
> that problems may arise later, because the two concepts were 
> independently developed (and owned) by different people who have 
> different views of the world.
> 
> Jeremy
> 
> 
>

Received on Monday, 23 January 2006 15:28:19 UTC