Closed SportsOpenData closed 7 years ago
I decided not to use a URL Slug based on the label because the labels might change, be substituted for synonyms, or translated. A stable non-readable id provides a better basis.
From the point of view of building this into a service there's no reason why you couldn't choose to use the prefLabel
in a sub domain or path component within your application, mapping it to the id internally.
That's great I'm agree with you :-)
Thanks a lot. Rgds. Paolo.
Il giorno lun 19 giu 2017 alle 18:21 Leigh Dodds notifications@github.com ha scritto:
I decided not to use a URL Slug http://patterns.dataincubator.org/book/url-slug.html based on the label because the labels might change, be substituted for synonyms, or translated. A stable non-readable id provides a better basis.
From the point of view of building this into a service there's no reason why you couldn't choose to use the prefLabel in a sub domain or path component within your application, mapping it to the id internally.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/openactive/activity-list/issues/10#issuecomment-309491632, or mute the thread https://github.com/notifications/unsubscribe-auth/ASsJHnY-qfJIoxy0-CzFKJCKSkElY7X6ks5sFp__gaJpZM4N-dKM .
--
Paolo Riva Presidente & Co-Founder Open Data in Sports
It could be interesting adding a prefSlug and altSlug for prefLabel and altLabel to make URI readble.
In our case, for example, activity is our entry point (e.g.: soccer.sportsopendata.net): it could be difficult to deliver a service by using UUID.
Using slug (pref or alt) it could be a good solution instead of RESTful way.