URIs do not have semantic meaning, they are opaque identifiers. https://www.w3.org/DesignIssues/Axioms.html#opaque
On Tue, 2 Jul 2019 at 17.06, Siddhesh Rane <kingsid...@gmail.com> wrote: > If the URL is some REST endpoint then you can map UUID in the URL to > binary keys in the database. > If your URLs are RDF resource identifiers, then better to stick with > hyphenated UUID form that is standard. > > Just out of curiosity, RDF is mostly for semantic data that has some > meaning. > If you are quring using keys that are essentially random strings, > would it not be more suitable to use a relational database? > > Siddhesh > > On Tue, Jul 2, 2019 at 8:17 PM Mikael Pesonen > <mikael.peso...@lingsoft.fi> wrote: > > > > > > This is handy to know, but in this case we are serving data over the id > > URLs, so that's why https://example.com type. > > > > > > > > On 02/07/2019 11:47, Claude Warren wrote: > > > I agree with Andy, but note that there is a URN specification for UUID > ( > > > https://tools.ietf.org/html/rfc4122) > > > > > > So the URI would be urn:uuid:<uuid string here> > > > > > > I used this in a recent project. > > > > > > Claude > > > > > > On Tue, Jul 2, 2019 at 8:53 AM Andy Seaborne <a...@apache.org> wrote: > > > > > >> I doubt one URI design vs another where it will make any observable > > >> difference. > > >> > > >> Andy > > >> > > >> On 01/07/2019 18:50, Siddhesh Rane wrote: > > >>> You could save the UUID as a 128 bit number in the database. > > >>> Conversion between alphanumeric and byte encoded UUIDs can be done on > > >>> the fly. > > >>> This would be the most compact solution compared to text format. > > >>> > > >>> Regards > > >>> Siddhesh Rane > > >>> > > >>> On Mon, Jul 1, 2019 at 9:02 PM Mikael Pesonen > > >>> <mikael.peso...@lingsoft.fi> wrote: > > >>>> > > >>>> We are now using UUIDs for resource ids, e.g. > > >>>> https://example.com/f0c6b590-0bd6-4c66-8872-f6a0f3aa33ac where id > > >> length > > >>>> is 38 characters. > > >>>> > > >>>> Would it be any better performance wise to use more compact id > > >>>> https://example.com/jgie3590roGvnfsjvGUEu using 21 alphanum > characters > > >>>> > > >>>> UUID is a standard atleast and better supported in various systems. > > >>>> > > >>>> -- > > >>>> Lingsoft - 30 years of Leading Language Management > > >>>> > > >>>> www.lingsoft.fi > > >>>> > > >>>> Speech Applications - Language Management - Translation - Reader's > and > > >> Writer's Tools - Text Tools - E-books and M-books > > >>>> Mikael Pesonen > > >>>> System Engineer > > >>>> > > >>>> e-mail: mikael.peso...@lingsoft.fi > > >>>> Tel. +358 2 279 3300 > > >>>> > > >>>> Time zone: GMT+2 > > >>>> > > >>>> Helsinki Office > > >>>> Eteläranta 10 > > >>>> FI-00130 Helsinki > > >>>> FINLAND > > >>>> > > >>>> Turku Office > > >>>> Kauppiaskatu 5 A > > >>>> FI-20100 Turku > > >>>> FINLAND > > >>>> > > >>> > > > > > > > -- > > Lingsoft - 30 years of Lea > <https://www.google.com/maps/search/0+years+of+Lea?entry=gmail&source=g>ding > Language Management > > > > www.lingsoft.fi > > > > Speech Applications - Language Management - Translation - Reader's and > Writer's Tools - Text Tools - E-books and M-books > > > > Mikael Pesonen > > System Engineer > > > > e-mail: mikael.peso...@lingsoft.fi > > Tel. +358 2 279 3300 > > > > Time zone: GMT+2 > > > > Helsinki Office > > Eteläranta 10 > > FI-00130 Helsinki > > FINLAND > > > > Turku Office > > Kauppiaskatu 5 A > > FI-20100 Turku > > FINLAND > > > > > -- > Your greatest regret is the email ID you choose in 8th grade >
