-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hackable URIs #5
Comments
Yes, you are right. The number of residential estates for which the planning permission has expired, in respect of which formal written requests for taking in charge (from residents or developers), were on hands at the beginning of the year If you are ok to have these large URIs (I think there are no more than 8) I can change them. |
Boris, URIs don't have to be verbose to that extent. As long as it is clear enough it should suffice. That is, something like a label - a few words at most. For instance, reusing the broader concept's label as base, and then appending the rest might be okay. p-6 Concept could be: p-6-1 Concept could be: Note: That's just to illustrate the idea, I'm not suggesting that those choice of terms are best ways to describe them. |
Ok, so we have
|
The resources in the dataset should use "hackable" URIs where they can be easily understood by developers and end-users.
Example:
For http://stats.data-gov.ie/data/m-1-4/2009/county/galway , it is difficult to intuitively know what m-1-4 supposed to represent unless it is dereferenced.
An example of a particular concept http://stats.data-gov.ie/concept/m-4 which is:
concept:m-4
a skos:Concept ;
concept:level "2"^^xsd:string ;
skos:altLabel "Public opening hours"^^xsd:string ;
skos:broader concept:m ;
skos:inScheme http://stats.data-gov.ie/codelist/geo/service-indicators-2009 ;
skos:notation "m.4"^^xsd:string ;
skos:prefLabel "M.4"^^xsd:string .
could use an URI like:
http://stats.data-gov.ie/concept/opening-hours
Bonus: If these URIs reflect notation from another document, it should use skos:definition and link to it.
The text was updated successfully, but these errors were encountered: