While I agree the primary aim isn't shortening, the result is usually much shorter by virtue of cutting out everything non essential to identification. I say this as a non stakeholder in w3id, just a fan.
Nevertheless I take your point that it isn't automated. I would like to understand the use case better; could you describe a specific scenario? Thanks Julie On Wednesday, June 1, 2016, Stas Malyshev <[email protected]> wrote: > Hi! > > > Hi there, may I ask what link shorteners provide you that w3id does not? > > Eg baked in metrics or 10char urls? Just curious why you would want to > > reimplement. > > From what I can see, the target audience of w3id is a relatively small > set of very stable URL prefixes that are used a lot and never change. It > also does not aim at making these URLs shorter, it aims at making them > stable. Adding URL namespace to it is a manual process, and individual > URLs are not stored. > > The target of URL shorteners is much bigger set of URLs, many of which > are relatively low-use or transient, but which can be created via > automatic means in great volumes, which make URL shorter and which are > aimed at storing, at least for a while, each URL as individual data piece. > > So, for our purposes w3id would not be very useful. > -- > Stas Malyshev > [email protected] <javascript:;> > > _______________________________________________ > Wikidata mailing list > [email protected] <javascript:;> > https://lists.wikimedia.org/mailman/listinfo/wikidata > -- ---------------------------------- [email protected] +1 805 455 5877 skype: mcmurry.julie git: jmcmurry ----------------------------------
_______________________________________________ Wikidata mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikidata
