W3C home > Mailing lists > Public > public-ietf-w3c@w3.org > June 2017

Re: [IAB] Call for Participation, Workshop on Internet naming systems

From: Mark Nottingham <mnot@mnot.net>
Date: Sat, 24 Jun 2017 11:20:27 +1000
Cc: public-ietf-w3c@w3.org
Message-Id: <FDE2AA36-7E85-4232-AAC3-780E635FCAF1@mnot.net>
To: Graham Klyne <GK@ninebynine.org>
I sent it to uri@w3.org. uri-review is for reviewing URI schemes, so probably not.


> On 23 Jun 2017, at 6:31 pm, Graham Klyne <GK@ninebynine.org> wrote:
> I agree.  Is it worth circulating to URI-review as well?
> #g
> --
> On 23/06/2017 01:37, Mark Nottingham wrote:
>> FYI; this touches on naming and URIs. It'd be good to have some Web folks there, I think.
>>> Begin forwarded message:
>>> From: IAB Chair <iab-chair@iab.org>
>>> Subject: [IAB] Call for Participation, Workshop on Internet naming systems
>>> Date: 23 June 2017 at 6:53:20 am AEST
>>> To: iab@iab.org, ietf-announce@ietf.org, ietf@ietf.org
>>> Call for Participation
>>> IAB workshop on Explicit Internet Naming Systems
>>> Internet namespaces rely on Internet connected systems sharing a common set of assumptions on the scope, method of resolution, and uniqueness of the names.    That set of assumption allowed the creation of URIs and other systems which presumed that you could authoritatively identify a service using an Internet name, a service port, and a set of locally-significant path elements.
>>> There are now multiple challenges to maintaining that commonality of understanding.
>>> Some naming systems wish to use URIs to identify both a service and the method of resolution used to map the name to a serving node.  Because there is no common facility for varying the resolution method in the URI structure, those naming systems must either mint new URI schemes for each resolution service or infer the resolution method from a reserved name or pattern. Both methods are currently difficult and costly, and the effort thus scales poorly.
>>> Users’ intentions to refer to specific names are now often expressed in voice input, gestures, and other methods which must be interpreted before being put into practice.  The systems which carry on that interpretation often infer which intent a user is expressing, and thus what name is meant, by contextual elements.  Those systems are linked to existing systems who have no access to that context and which may thus return results or create security expectations for an unintended name.
>>> Unicode allows for both combining characters and composed characters when local language communities have different practices.  When these do not have a single normalization, context is required to determine which to produce or assume in resolution.  How can this context be maintained in Internet systems?
>>> While any of these challenges could easily be the topic of a stand-alone effort, this workshop seeks to explore whether there is a common set of root problems in the explicitness of the resolution context, heuristic derivation of intent, or language matching.   If so, it seeks to identify promising areas for the development of new, more explicit naming systems for the Internet.
>>> We invite position papers on this topic to be submitted by July 28, 2017 to ename@iab.org <mailto:ename@iab.org>.    Decisions on accepted submissions will be made by August 11, 2017.
>>> Proposed dates for the workshop are September 28th and 29th, 2017 and the proposed location is in the Pacific North West of North America.  Finalized logistics will be announced prior to the deadline for submissions.
>>> Ted Hardie
>>> for the IAB
>> --
>> Mark Nottingham   https://www.mnot.net/

Mark Nottingham   https://www.mnot.net/
Received on Saturday, 24 June 2017 01:21:00 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:10:28 UTC