-
Notifications
You must be signed in to change notification settings - Fork 2
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
URL patterns for resources created by linked fiesta. #2
Comments
Good suggestions, Nandana! I have added some PROV triples and updated the URIs for festivals from fiestas.net and they are now in the format of http://fiestas.linkeddata.es/festival/es/{PROVINCE}/{TOWN}/{FESTIVALNAME}. You can see the result in https://github.com/fpriyatna/linked-fiestas/blob/master/datasets/fiestas/linkedfiestas1b.nt |
About the domain: Another option is to use w3id.org. e.g., https://w3id.org/linked-fiestas/es/{PROVINCE}/{TOWN}/{FESTIVALNAME} The good thing is that we can host everything on Github and just write redirection rules. This will be much easier than hosting the data on our servers. About the URL patterns: (a) {PROVINCE}/{TOWN}/{FESTIVALNAME} vs (b) {id} I believe (a) is great for human-readability and debugging but might not be suitable for all situations. For example, for some festivals, we might not know the town, etc. In addition, we are encoding a lot of information to the URL. |
I removed PROVINCE from the URIs, some of the festivals don't have province, but all of them have town |
we can also remove "festival" from the URI, I dont really agree to put the type in the URI. How about: http://{LANGUAGE}.fiestas.linkeddata.es/{TOWN}/{FESTIVALNAME}? |
IRI pattern https://w3id.org/linkedfiestas/resource/{id} |
IRI pattern https://w3id.org/linked-fiestas/resource/{id} |
I propose to create an IRI within a namespace managed by us for each festival and then link it to the other external datasets.
For example,
<http://fiestas.linkeddata.es/festival/es/nnnnn> a schema:Festival .
Then we can provide sameAs links
In addition, depending on where we derive the information, we can also give provenance information
<http://fiestas.linkeddata.es/festival/es/nnnnn> prov:wasDerivedFrom <https://fiestas.net/bunol/>
And also additional links to webpages etc, if we have any.
<http://fiestas.linkeddata.es/festival/es/nnnnn> rdfs:seeAlso <http://latomatina.info>
What do you think?
The text was updated successfully, but these errors were encountered: