Re: Investigating the Artstor and VRA schemas

Hi Mark, Andy,

If we are going to try to collapse all versions of Person to a single 
Person reference then presumably there also must be a way to collapse 
the individual records that come from converting our XML sources to 
RDF.  Arguably then my XSLT script should first look up a person in the 
common database before creating a new person so that the Person records 
aren't massively duplicated.  Anyone have recommendations on how to set 
up a global table of Person records to reference in XSLT?  Or perhaps it 
would be easier to put in a temporary reference using XSLT and replace 
that with a global reference using a bit of Perl?

Cheers,
-kls


Butler, Mark wrote:

>Hi team,
>
>Using the tools I've outlined in the previous email I've been analysing
>Andy's VRA schema, my VRA schema, and my Artstor VRA schema. It is useful to
>compare the classes and properties in each schema:
>
>Andy's VRA schema - classes:
>
><http://web.mit.edu/simile/2003/10/person#Person>
><http://web.mit.edu/simile/2003/10/vraCore3#Image>
><http://web.mit.edu/simile/2003/10/vraCore3#LargerEntity>
><http://web.mit.edu/simile/2003/10/vraCore3#Location>
><http://web.mit.edu/simile/2003/10/vraCore3#Material>
><http://web.mit.edu/simile/2003/10/vraCore3#Measurement>
><http://web.mit.edu/simile/2003/10/vraCore3#Record>
><http://web.mit.edu/simile/2003/10/vraCore3#Series>
><http://web.mit.edu/simile/2003/10/vraCore3#Work>
>
>  
>


-- 
========================================================
   Kevin Smathers                kevin.smathers@hp.com    
   Hewlett-Packard               kevin@ank.com            
   Palo Alto Research Lab                                 
   1501 Page Mill Rd.            650-857-4477 work        
   M/S 1135                      650-852-8186 fax         
   Palo Alto, CA 94304           510-247-1031 home        
========================================================
use "Standard::Disclaimer";
carp("This message was printed on 100% recycled bits.");