URIs for INSPIRE - 303 URIs vs. hash URIs

[jechterhoff]

Description

INSPIRE application schemas model real-world phenomena as features. A feature provides a particular view upon a real-world phenomenon. Within the Linked Data domain, it is important to identify both the real-world phenomenon itself and representations that describe it.

The W3C note "Cool URIs for the Semantic Web" recommends the use of 303 URIs or Hash URIs to identify resources – the actual thing / real-world phenomenon as well as representations that describe it. Both solutions have their advantages and disadvantages. They can even be combined.

When transforming INSPIRE data into RDF, clear guidance is needed for the creation and assignment of URIs for spatial objects and the real-world phenomena they represent.

Discussion Item

If you have been involved in the development of a system that publishes RDF data: with which particular URI style (303 URIs and/or Hash URIs, or even an entirely different approach) does it publish data, and what were the reasons for choosing that URI style? In other words, can you give recommendations on when/why a specific URI style is preferable?

[cportele]

It will be interesting to learn why the upcoming pilots choose one approach over the other.

[jechterhoff]

Related to #3