Re: [Uri-review] URI scheme for postal addresses?

Hi Nicholas,

No, there isn't a URI scheme for postal addresses, AFAIK.

But relevant prior art is the "ADR" structured property in vCard 3.0 (RFC
6350, 2011):

  https://datatracker.ietf.org/doc/html/rfc6350#section-6.3.1

Cheers,
- Ira

On Wed, Jul 26, 2023 at 9:22 AM Nicholas Humfrey <nicholas.humfrey@bbc.co.uk>
wrote:

> Hello,
>
>
>
> In ETSI TS 102 818, in Appendix A there is a URI scheme for postal
> addresses:
>
>
> https://www.etsi.org/deliver/etsi_ts/102800_102899/102818/03.04.01_60/ts_102818v030401p.pdf
>
>
>
> I was surprised to discover that this isn’t defined anywhere else.
>
> Is there any interest in defining this in an RFC?
>
>
>
> I also registered the following URI schemes provisionally and had intended
> to submit an RFC for them; but have not got around to it yet: dab, fm,
> amms, drm
>
>
>
>
>
> Thanks,
>
>
>
> Nicholas Humfrey
>
>
>
>
>
>
>
> This clause defines a URI scheme for defining postal addresses.
>
> The format is a URI-compliant and case insensitive string in the form:
>
>
>
>     addressuri = "postal:" addressdata
>
>     addressdata = segment *("/" segment)
>
>     segment = *urlchar urlchar = unreserved | escaped
>
>
>
> Either the most generalized part OR the most localized part of the address
> should come first (depending on the postal scheme practices of the target
> country), separating each main fragment with a slash ("/"), through the
> hierarchy until the most localized/generalized resource is reached.
> unreserved and escaped are defined in IETF RFC 3986.
>
>
>
> NOTE:
>
> Where "/" is needed as a character in the address (e.g. "20/22 High St")
> it should be encoded as the hex equivalent (i.e. "%2F").
>
>
>
> EXAMPLE:
>
> postal:Creative%20Technologies/1%20Passage%20Street/Bristol/
> BS2%200JF/United%20Kingdom/
>
>
> _______________________________________________
> Uri-review mailing list
> Uri-review@ietf.org
> https://www.ietf.org/mailman/listinfo/uri-review
>