On 20-08-2025 11:00 AM, Mario Loffredo wrote:
[ML3] My interpretation of that section is that it warns clients that a postal address could appear in either format in an RDAP response and, therefore, they should be prepared to handle both of them. But I'm pretty sure that clients typically consider the unstructured version only when the structured one isn't available. For an implementer, it's much easier to start with structured data and aggregate/manage it as desired rather than the other way around.
I don't know what "typical" is, but my client will display both if both are given... but I have never seen any registry do that. While I think supporting unstructured addresses is an absolute requirement, it does occur to me that even registries that cannot fully support structured addresses do have the country and sometime region in a semi-structured form. Therefore I don't think it is unreasonable to allow unstructured addresses and at least these two fields in a structured form... it isn't great, but it is better than nothing. It is also my understanding that one of the reasons unstructured addresses area allowed in vCard is that they represent what can be written out on a postal envelope for an economy. (I don't know what JSContact does here). It is one thing to have a postal address in structured form, but if you cannot use it on a postal envelopes that seems to be a bit odd. I think we westerners tend to think that structured addresses are obvious in postal envelope form, but that is not true for many places in Asia where writing direction on both axes is not the same (as ours). -andy, as an individual _______________________________________________ regext mailing list -- regext@ietf.org To unsubscribe send an email to regext-le...@ietf.org
