Re: [Uri-review] Registration request for "at" URI scheme
Melvin Carvalho <melvincarvalho@gmail.com> Wed, 10 May 2023 18:21 UTC
Return-Path: <melvincarvalho@gmail.com>
X-Original-To: uri-review@ietfa.amsl.com
Delivered-To: uri-review@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1DC7EC1CAB43 for <uri-review@ietfa.amsl.com>; Wed, 10 May 2023 11:21:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.094
X-Spam-Level:
X-Spam-Status: No, score=-2.094 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0vf0Tgc0MNrP for <uri-review@ietfa.amsl.com>; Wed, 10 May 2023 11:21:37 -0700 (PDT)
Received: from mail-yb1-xb35.google.com (mail-yb1-xb35.google.com [IPv6:2607:f8b0:4864:20::b35]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C67BAC1CAB48 for <uri-review@ietf.org>; Wed, 10 May 2023 11:21:37 -0700 (PDT)
Received: by mail-yb1-xb35.google.com with SMTP id 3f1490d57ef6-ba693af163dso167253276.3 for <uri-review@ietf.org>; Wed, 10 May 2023 11:21:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1683742897; x=1686334897; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=RTqi+ydXNhcWDDjCSoEemhYDzVuF4YptToaT7bN7CCY=; b=CaEPtSYLnIlF6LVG1yky1oXLQzBeSzkFG9rIWJ/oG2vRikHoSRRCV8ThU0rvlraVm6 Pi1B4w/axmDfF5XJQy9IDKBfRVAdTGq0fWPp5kRfVJEAPVqkOyzTSHBFhawyeZENor93 8FqiPpD/RSYb/v2YRZ2oAmjanOIYqL/6jg1hAgtY08cLTv8038g6+muVN7dUj5iARDpO XiLIVaZmH4Xf6gyTmVGyUge0qZW+/kqCee/u7JrD0+99KxmiuQrOt8dmrxAQ0UdFS5Su IOEw6aety4c1LtDp4yhRyPpsheg+SlbAUumdk/AfvEobGfqPddMrWRWcuA81VYspLcUN UFDw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1683742897; x=1686334897; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=RTqi+ydXNhcWDDjCSoEemhYDzVuF4YptToaT7bN7CCY=; b=hyq6bQI2qSAFudWP+LCtFn7der9yu7OZf2ZUgfhJwyUu6drQ1EoZb3W+c5xXOS4hr7 I0qoJAwyAnRBPZQaJ14vYPiRH6tq+w2O570ONHX7g44ZrvXSGt6DSiCl+Y/4zwvAqdkI rZpIsRfTzF81pbEYm2UyGuSWaCWAJb/3NpbEv7K36q+PNDLINzFmpnLI4SaZlfEagU+B Rkn1IaJ8lWDGTctucVvwpbHdezaJ5la2ZoME8iM3RJxtUpj2gzw3VLeVgyJFip9CrgCE TP4qB78J1BGRZuJS2WJUNuudNA99EMp9TGKIicO7ZVPr+hYBde+lIFVGCfuMOEJDBIpJ rUxQ==
X-Gm-Message-State: AC+VfDwTlwPhbD3Pht76BAqVkML+KpqzeGWTwHV10n4LLMvk7VvXdLJh Zvvj/vdLVbqTeCK/y/4I05cZS7nXrNa6vmXhpg7vksPOHFg=
X-Google-Smtp-Source: ACHHUZ4uImroAWuvEf9hJf7fT8jW7dcP0xfy50IL+ZqHPLjQ9/EU/0F7c34DpNM+bxE9aOwF9/n+BXOd7ZNG1RJQnSo=
X-Received: by 2002:a25:fc0a:0:b0:b8f:5639:cb8a with SMTP id v10-20020a25fc0a000000b00b8f5639cb8amr20305335ybd.9.1683742896905; Wed, 10 May 2023 11:21:36 -0700 (PDT)
MIME-Version: 1.0
References: <f456a86-b079-2bec-f698-f2fc4fb7e76b@robocracy.org> <CAKaEYhKaB9=NVGY_eQk3vq4zGEy_N7FNy9yj02wdz0DuHS2wqw@mail.gmail.com> <CABFYohi+CD33Hn9SnPk3Fk+_W3=8pwtnHeGF1KWVQZG4bV_hnA@mail.gmail.com> <CAKaEYhK=snie3_nAz3CdJoMDh=fx6zmGwbcc9m_jESdjV2ym3w@mail.gmail.com> <81587de4-d623-01d2-9a68-0f797a1eec6b@lear.ch> <54504db-83d3-c2e3-7820-3275323d5bd@robocracy.org> <ee6f60d9-5f19-3344-bd26-e87f881aa5a6@lear.ch> <e53bf99a-012b-40b7-742b-f9f5c56e876c@ninebynine.org> <CAD4FMei=03TAnaC=d6qtnP1Kt6eAJhxZUWXvSnpyKLscKj3F6g@mail.gmail.com>
In-Reply-To: <CAD4FMei=03TAnaC=d6qtnP1Kt6eAJhxZUWXvSnpyKLscKj3F6g@mail.gmail.com>
From: Melvin Carvalho <melvincarvalho@gmail.com>
Date: Wed, 10 May 2023 20:21:24 +0200
Message-ID: <CAKaEYhKGxuGNGWvb_0Am=USLq9Db-2ShUEttM-yM8cgsZjk6kw@mail.gmail.com>
To: Paul Frazee <pfrazee@gmail.com>
Cc: Graham Klyne <gk@ninebynine.org>, Devin Ivy <devin@blueskyweb.xyz>, uri-review@ietf.org, Jay Graber <jay@blueskyweb.xyz>, Bryan Newbold <bryan@blueskyweb.xyz>
Content-Type: multipart/alternative; boundary="00000000000043620405fb5af16d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/uri-review/hJ4bFYeL-o2vzt0oJofyabfn6CE>
Subject: Re: [Uri-review] Registration request for "at" URI scheme
X-BeenThere: uri-review@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Proposed URI Schemes <uri-review.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/uri-review>, <mailto:uri-review-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/uri-review/>
List-Post: <mailto:uri-review@ietf.org>
List-Help: <mailto:uri-review-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/uri-review>, <mailto:uri-review-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 May 2023 18:21:42 -0000
st 10. 5. 2023 v 19:29 odesílatel Paul Frazee <pfrazee@gmail.com> napsal: > The idea is indeed that at:// could user-facing in the same way http:// > is. The intent is to express a social address so that I could be at:// > pfrazee.com to provide a social identity and http://pfrazee.com to > provide a website. We're hoping to make the scheme intuitive to people, as > it has a clear connection to the "@pfrazee.com" convention. > The additional information is appreciated. Perhaps it's worth adding the connection between "at://" and "@" in the docs. Introducing the at:// URI scheme as interchangeable with the "@" symbol might be a clash due to possible confusion with existing schemes like mailto:, parsing issues, compatibility problems, security concerns, and adoption challenges. The term @ is parsed in many different scenarios. I'll assume you would be putting it in JSON. It's worth noting that you already have terms in the JSON using the @ symbol, namely @context and @id. > > I can understand the hesitance around what we're proposing. It's a common > word and assigning it to an early project is a big ask. I'd like to keep > the scheme because I believe it's user-friendly, but I also don't want to > push something that people aren't comfortable with. > > My question from here is, is there a way forward to address the concerns > around this proposal, or do folks feel like this proposal is a non-starter? > If there is a path forward, how can we help get there? > > Paul > > On Wed, May 10, 2023 at 10:54 AM Graham Klyne <gk@ninebynine.org> wrote: > >> A small clarification to Eliot's comment: the *provisional* registry is >> FCFS, but there is still a possibility for a hold-up come the time this is >> advanced to a permanent registration. The good news is that by raising >> this here and now (rather than waiting for a permanent registration >> review), there's a better chance that a consensus on this issue can emerge >> before the protocol is very widely deployed. So, thank you for doing that! >> >> #g >> >> >> On 08/05/2023 09:18, Eliot Lear wrote: >> >> Hi Bryan, >> >> As Alex mentioned, I wasn't referring to URI schemes, but rather that the >> word "at" is not descript, reused in many different contexts, from Austria >> to a preposition, to a scheduling command in UNIX to various other acronym >> expansions. My understanding is that the registry is FCFS, and so this is >> *advice*. Whatever you choose you'll be stuck with. If you even added >> an extra character or two that could make more clear what this is, you may >> find it helpful later on. >> >> Eliot >> On 08.05.23 00:14, bnewbold@robocracy.org wrote: >> >> >> Hi Eliot, >> >> We did do both some general search, and checked against the URI schema >> registry when starting work on the protocol, and are not aware of any >> problematic existing use or conflicts the the use of the URI scheme name. >> >> The closest confusion we are aware of with 'at' is the Hayes AT command >> originally used with modems. We are unaware of any URI scheme specifically >> for the Hayes AT command set, and while that command set is still in broad >> use, it does not seem likely to start using one now. >> >> "at" matches our protocol name ("AT" stands for "Authenticated >> Transfer"). There is a bit of wordplay going on with "@" (the "at symbol"), >> which is used as a prefix convention in social media to indicate a user >> handle. AT Protocol is primarily used for social media applications (at >> least, that is the focus at present). >> >> As precedent, there are several other two-character URI schemes in the >> current registry. >> >> URIs starting with "at://" are already being used by several >> implementations of the AT Protocol. At this point it seems like a change >> would only add to confusion. >> >> --bryan >> >> On Sun, 7 May 2023, Eliot Lear wrote: >> >> As another casual observer, can I suggest that you use a slightly more >> descriptive scheme name? "at" is heavily overloaded, and a name that >> provides at least a guess what this is will serve the user better. >> >> >> _______________________________________________ >> Uri-review mailing listUri-review@ietf.orghttps://www.ietf.org/mailman/listinfo/uri-review >> >> -- >> Graham Klynemailto:gk@ninebynine.org <gk@ninebynine.org>http://www.ninebynine.org >> Mastodon: @gklyne@indieweb.social >> GitHub/Skype: @gklyne >> >> _______________________________________________ > Uri-review mailing list > Uri-review@ietf.org > https://www.ietf.org/mailman/listinfo/uri-review >
- [Uri-review] Registration request for "at" URI sc… bnewbold
- Re: [Uri-review] Registration request for "at" UR… Melvin Carvalho
- Re: [Uri-review] Registration request for "at" UR… bnewbold
- Re: [Uri-review] Registration request for "at" UR… Tim Bray
- Re: [Uri-review] Registration request for "at" UR… Melvin Carvalho
- Re: [Uri-review] Registration request for "at" UR… bnewbold
- Re: [Uri-review] Registration request for "at" UR… Melvin Carvalho
- Re: [Uri-review] Registration request for "at" UR… Eliot Lear
- Re: [Uri-review] Registration request for "at" UR… bnewbold
- Re: [Uri-review] Registration request for "at" UR… Alexander Mayrhofer
- Re: [Uri-review] Registration request for "at" UR… bnewbold
- Re: [Uri-review] Registration request for "at" UR… Eliot Lear
- Re: [Uri-review] Registration request for "at" UR… Ted Hardie
- Re: [Uri-review] Registration request for "at" UR… bnewbold
- Re: [Uri-review] Registration request for "at" UR… Tim Bray
- Re: [Uri-review] Registration request for "at" UR… Melvin Carvalho
- Re: [Uri-review] Registration request for "at" UR… Graham Klyne
- Re: [Uri-review] Registration request for "at" UR… Paul Frazee
- Re: [Uri-review] Registration request for "at" UR… Melvin Carvalho
- Re: [Uri-review] Registration request for "at" UR… Melvin Carvalho
- Re: [Uri-review] Registration request for "at" UR… Paul Frazee
- Re: [Uri-review] Registration request for "at" UR… Martin J. Dürst
- Re: [Uri-review] Registration request for "at" UR… Melvin Carvalho
- Re: [Uri-review] Registration request for "at" UR… Melvin Carvalho
- Re: [Uri-review] Registration request for "at" UR… Graham Klyne
- Re: [Uri-review] Registration request for "at" UR… bnewbold
- Re: [Uri-review] Registration request for "at" UR… bnewbold
- Re: [Uri-review] Registration request for "at" UR… bnewbold