Defining URI's

3 posts / 0 new
Log in to post comments
Last post
8 June, 2016 - 17:19
#1
fberetta
Defining URI's

In the Heloïse network we could use two kinds of URI's:

Projects are invited to provide self administered URI's based on the name of their institution or to use https://w3id.org/ URI's

Top
10 June, 2016 - 14:07
fberetta
Discussion of URI format

About the expressed proposition, two issues should be considered:

  • for using inside Drupal it would be better to have URIs in this form : http://heloisenetwork.eu/object/actor/asfe-33
    • this would allow to prepare different kinds of dereferencement pages according to the object class
    • and to provide unique identifiers for data coming from the different projects: 33 would be the identifier
    • this would allow to use the different identifiers (often database primary keys)
    • with project specific URIs it would be difficult to have heloise website dereferencing pages
  • a second issue is that even for Heloise specific ressources, URIs in this form :
Top
14 June, 2016 - 10:02
dferhod
Discussion of URI format

Hello Francesco,

What do you mean by "hash" ? For me a hash is something like this :

64359b7192746a14740ad4bb7afe4e097327d0790190fd16

If it was you're thinking about, I would not recommand to use a hash as identifier inside a URI unless it is the real identifier of the object inside the triplestore.

Can you provide an example for what could be a folder structure to express classes ?

 

As a reminder, all I need to properly display an object with Drupal is an unique ID property for all the classes of objects and knowledge units.

With that unique ID, I can extract an URI like http://heloisenetwork.eu/object/collective-actor/netw-33 the two components "collective-actor" and "netw-33" to call the right "Drupal Views" page and execute the proper SPARQL query with "netw-33" as a filter of the view.

Top
Log in to post comments