[weirds] vCard | Was: Re: Entity postal address information in draft-ietf-weirds-json-response-01

[Simon Perreault <[e-mail]>]

Please allow me to remind everyone that the IETF has a standard for such 
information: vCard. Let's use it and focus on WEIRDS, not on postal 
address formats.

And there is a draft about a JSON representation for vCard:
http://tools.ietf.org/html/draft-bhat-vcarddav-json-00

It's really straightforward IMHO...

Simon


Le 2012-12-19 14:55, Gavin Brown a écrit :
> Postal address information for entities is returned in a flat array format:
>
>           "postalAddress" :
>           [
>             "123 Maple Ave",
>             "Suite 90001",
>             "Vancouver",
>             "BC",
>             "12393"
>           ],
>
> For any registry whose database design was developed to support EPP,
> this is quite lossy, since the specific meaning of each field is lost.
>
> I suggest that in addition to the above format, the standard should also
> permit a full object, like so:
>
>           "postalAddress" :
>           {
>             street: [ "123 Maple Ave", "Suite 90001", ],
>             city: "Vancouver",
>             sp: "BC",
>             pc: "12393",
>             cc: "CA"
>           },
>
> It would be pretty easy for clients to work out which model was being
> used, and handle it accordingly. Servers should use one model or the
> other, but not both.
>
> G.
>


-- 
DTN made easy, lean, and smart --> http://postellation.viagenie.ca
NAT64/DNS64 open-source        --> http://ecdysis.viagenie.ca
STUN/TURN server               --> http://numb.viagenie.ca