Re: [Uri-review] Registration request for "at" URI scheme

so 6. 5. 2023 v 17:06 odesílatel <bnewbold@robocracy.org> napsal:

>
> [re-trying from my personal email; original email was blocked as spam]
>
> Hi Folks!
>
> We are requesting a provisional registration of the "at" URI scheme, for
> use with the AT Protocol (atproto.com). Details are listed below.
>
> We do expect to add some additional constraints and small tweaks before
> formalizing the entire protocol, but we will maintain compatibility with
> existing URIs, and it seems prudent to register provisionally at this
> time.
>

I know that the AT protocol is not finished yet, and the identifier system
is not finalized e.g. with did:plc

https://github.com/bluesky-social/did-method-plc

Bluesky writes: "We cheekily titled the method "Placeholder", because we
don't want it to stick around. We're actively hoping to replace it with
something less centralized."

Could I perhaps encourage you to think about how else you could achieve
this without minting a new URI scheme, as I think it's not really needed.
Perhaps take the same approach as with "did placeholder"

The JSON objects already have 7 different types of identifiers, and there's
more (e.g. CID) and when you replace did:plc it will be at least 9.  See:

[image: image.png]

https://imgproxy.snort.social/_BJ6z8w2BYFa4rD3jToRuYzwW1UM5yvDM5S1qmJKHNo//aHR0cHM6Ly92b2lkLmNhdC9kLzJUQ0pxZkpLYldOZFpzUGNrZ1pCeXoud2VicA

I think it ought not be an issue to register "at", but I really think you
might be saving yourself some trouble if you hold off for a bit and
complete the protocol.  at:// likely is not needed at all.

The HTTP identifiers can be done with http:// and the did identifers can be
done with did:, which is part of the design of URIs.  There's not a huge
need to put at:// in front of either, IMHO

>
> -------------
>
> URI scheme name: at
>
> Status: provisional
>
> URI scheme syntax:
>      at://<authority>
>      at://<authority>/<path>
>      at://<authority>/<path>#<fragment>
>
> URI scheme semantics:
>      Reference a repository or record in the Authenticated Transfer
> Protocol (AT Protocol)
>
> Encoding considerations:
>      Unknown, use with care.
>
> Applications/protocols that use this URI scheme name:
>      The Bluesky social network (https://bsky.app), running on top of AT
> Protocol
>
> Interoperability considerations:
>      Unknown, use with care.
>
> Security considerations:
>      Unknown, use with care
>
> Contact:
>      - Bryan Newbold <bryan@blueskyweb.xyz>
>
> Change controller:
>      - Bluesky PBLLC
>      - Paul Frazee <pfrazee@gmail.com>
>
> References:
>      "AT Protocol Overview" <https://atproto.com/guides/overview>
>      "ATP URI Scheme" <https://atproto.com/specs/at-uri-scheme>
>
> _______________________________________________
> Uri-review mailing list
> Uri-review@ietf.org
> https://www.ietf.org/mailman/listinfo/uri-review
>

Re: [Uri-review] Registration request for "at" URI scheme

Attachment: image.png