RE: ungetable http URIs

Hi Andy

> I would suggest putting something appropriate at the URLs for 
> each of these:

> 2/ A defintion of the controlled term (it's a web resource so 
> the return from GET is a representation of that resource - 
> could be RDF - just rdfs:label would help).
> 
>     <> rdf:label "Portrait" .
> 
> (<> is a "this" resource reference in N3)
> 
> 
> 3/ (Not quite sure what exactly you mean by "metadata 
> instance" 

something like this

<http://web.mit.edu/simile/metadata/artstor/id#UCSD_41822000037356>
      a       vra:Image ;
      art:geographic
<http://web.mit.edu/simile/metadata/artstor/geographic#Spain> ;
      art:hasMediaFile
<http://web.mit.edu/simile/metadata/artstor/mediafile#2-41822000037356.jpg>
.
      art:imageId
<http://web.mit.edu/simile/metadata/artstor/image_id#41822000037356> ;
      art:imageSource
<http://web.mit.edu/simile/metadata/artstor/source#ucsdsrc1> ;
      art:inCollection
<http://web.mit.edu/simile/metadata/artstor/collection#103> ;
      art:metadataCreationDate              "2003-09-26" ;
      art:metadataUpdateDate              "2003-09-26" ;
      art:objectId
<http://web.mit.edu/simile/metadata/artstor/object_id#23073> ;
      art:topic
<http://web.mit.edu/simile/metadata/artstor/topic#Architecture:Site> ;
      vra:creation "begun 1090" ;
      vra:id  "081908 999999" ;
      vra:idCurrentAccession              ".b38694116" ;
      vra:measurementsFormat
              <http://web.mit.edu/simile/metadata/artstor/format#color> ;
      vra:period "11th C. A.D" ;
      vra:subject
<http://web.mit.edu/simile/metadata/artstor/subject#Avila_(Spain)--San_Vicen
te> ;
      vra:title "Avila: San Vicente Int. North wall" ;
      vra:type <http://web.mit.edu/simile/metadata/artstor/recordType#work>
;
      vra:typeAAT "Avila (Spain)--San Vicente" .

I guess you knew that though, so what term would you prefer instead of
"metadata instance"?

> but ...) 
>    like 2/ a GET returns a representation.  If there is a 
> document/representation 

All this information is in the RDFied Artstor corpus, so it sounds like the
solution is to offer a HTTP interface to the Arstor corpus using the URLs
used in the corpus. So my next questions are:

1. To do this I think we need to produce appropriate subgraphs, perhaps
using a technique similiar to Alex Barnell's work on RDF objects, right?

2. Does Joseki support this - is it just a matter of publishing the data in
Joseki? Or is it something for future work?

3. If (2) is yes, does this have any implications for the URLs - do we need
to change them so we can use Joseki?

4. We've agreed to keep the Artstor data private, so we can't expose artstor
via HTTP. So does this mean we just use URNs? Making modelling decisions due
to non-technical issues feels wrong?

Dr Mark H. Butler
Research Scientist                HP Labs Bristol
mark-h_butler@hp.com
Internet: http://www-uk.hpl.hp.com/people/marbut/

Received on Wednesday, 19 November 2003 10:49:23 UTC