[UA-discuss] Universal Acceptance now on Wikipedia...https://en.wikipedia.org/wiki/Universal_Acceptance

Wed Jan 3 17:20:06 UTC 2018

I agree.
It’s one thing to enter a bare domain name into a browser address bar, where the user intent can be inferred.
It’s another thing to assume that every internet-enabled app which displays strings which look like bare domain names should automatically linkify them into a URL.
Understanding of user intention has often been put forward as a prerequisite for linkification, at least since the meeting in Seattle last year.

From: UA-discuss [mailto:ua-discuss-bounces at icann.org] On Behalf Of Andrew Sullivan
Sent: Saturday, December 30, 2017 10:53 AM
To: Andre Schappo <A.Schappo at lboro.ac.uk>; Universal Acceptance <ua-discuss at icann.org>
Subject: Re: [UA-discuss] Universal Acceptance now on Wikipedia...https://en.wikipedia.org/wiki/Universal_Acceptance

I sincerely hope that linkification of bare domain names does _not_ take over, because it gets in the way.  The Internet is bigger than the web, and we aim for something too poor if we nail ourselves forever and only to https.

A

--
Please excuse my clumbsy thums

________________________________

On December 30, 2017 6:19:11 AM Andre Schappo <A.Schappo at lboro.ac.uk<mailto:A.Schappo at lboro.ac.uk>> wrote:
Really good to see UA on wikipedia. It feels like UA has made the mainstream.

2 suggestions:-

1️⃣ In the wikipedia article there are indirect references to https://uasg.tech<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fuasg.tech&data=02%7C01%7Cmarksv%40microsoft.com%7C0b4274415ebf461d96a608d54fb69fc5%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C1%7C636502568161358679&sdata=g29stbc3vUG%2BpPSaYE%2Fdq%2BBJedj0B8riHxy09S2rpyo%3D&reserved=0> eg https://uasg.tech/wp-content/uploads/2017/09/UASG-Report-UASG016.pdf<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fuasg.tech%2Fwp-content%2Fuploads%2F2017%2F09%2FUASG-Report-UASG016.pdf&data=02%7C01%7Cmarksv%40microsoft.com%7C0b4274415ebf461d96a608d54fb69fc5%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C1%7C636502568161358679&sdata=x8QOPFdx%2BJAQe4Ckeso2BmnpjB0rvmUrDxKLYqNbCMo%3D&reserved=0> I think there should be a direct reference to uasg home page in the wikipedia article ie https://uasg.tech<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fuasg.tech&data=02%7C01%7Cmarksv%40microsoft.com%7C0b4274415ebf461d96a608d54fb69fc5%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C1%7C636502568161358679&sdata=g29stbc3vUG%2BpPSaYE%2Fdq%2BBJedj0B8riHxy09S2rpyo%3D&reserved=0>

2️⃣ drop the www —  eg in the wikipedia article there is the link https://www.icann.org/resources/pages/universal-acceptance-2012-02-25-en<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.icann.org%2Fresources%2Fpages%2Funiversal-acceptance-2012-02-25-en&data=02%7C01%7Cmarksv%40microsoft.com%7C0b4274415ebf461d96a608d54fb69fc5%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C1%7C636502568161358679&sdata=Yvsz%2FGr3PFTQ%2FHHktdiVeJtr9HKdkj73VKqXZD6fvLw%3D&reserved=0> I suggest using https://icann.org/resources/pages/universal-acceptance-2012-02-25-en<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Ficann.org%2Fresources%2Fpages%2Funiversal-acceptance-2012-02-25-en&data=02%7C01%7Cmarksv%40microsoft.com%7C0b4274415ebf461d96a608d54fb69fc5%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C1%7C636502568161358679&sdata=3VRBHe4DJvpr%2BqezbrGqSdU6%2FneY2Nqe4pHgPJ5RqyQ%3D&reserved=0> instead. My experience is that the majority of people think the initial www is necessary but in the majority of web addresses the www is not necessary. My reasoning is that having the www prefix is contrary to IDNs because one then has mixed scripts in an IDN. Take Korea NIC. Their IDN is https://한국인터넷정보센터한국<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fxn--3e0bx5euxnjje69i70af08bea817g.xn--3e0b707e&data=02%7C01%7Cmarksv%40microsoft.com%7C0b4274415ebf461d96a608d54fb69fc5%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C1%7C636502568161358679&sdata=YNCctz7DFeW%2F%2FRBOBipB9rQDvd0jRNwirROTWWtlmb8%3D&reserved=0> They do support https://www.한국인터넷정보센터.한국<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.xn--3e0bx5euxnjje69i70af08bea817g.xn--3e0b707e&data=02%7C01%7Cmarksv%40microsoft.com%7C0b4274415ebf461d96a608d54fb69fc5%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C1%7C636502568161358679&sdata=mW%2FP9gD9%2BdtkVT5PfYtQgdiB8k0JEOgNBIzqk%2B%2BAb6I%3D&reserved=0> but they do not make the www necessary and they do not redirect to the www form.

Now, what I have written is also contradictory because I have used https:// so that my Apple Mail App will linkify. When I put links in my webpages I would only display to users 한국인터넷정보센터.한국 My hope for the future is that linkification will become more sophisticated and be able linkify 한국인터넷정보센터.한국 without the need for www or https:// thus resulting, in this case, a fully korean hangeul domain name.

So, I suggest the working practice — when possible (which I think is most of the time), drop both the www and https:// when presenting the domain name to end users.

André Schappo

On 30 Dec 2017, at 08:15, Don Hollander <don.hollander at icann.org<mailto:don.hollander at icann.org>> wrote:

A nice way to end a fairly productive year.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/ua-discuss/attachments/20180103/d893f68c/attachment.html>