> Le 7 juin 2023 à 14:26, Andrew Newton <a...@hxr.us> a écrit :
>
> Hi All,
>
...
> By contrast, JSContact JSON objects are much more than simple JSON
> objects as found in RDAP. Here is an example of JSContact person
> titles:
>
> "titles": {
> "le9": {
> "kind": "title",
> "name": "Research Scientist"
> },
> "k2": {
> "kind": "role",
> "name": "Project Leader"
> }
> }
>
> What should be an array of strings (e.g. “List<String> titles”) is
> instead an object of objects, where each nested object has meta-data
> and is given a unique property name thus requiring the implementer to
> manually map the nested objects. There are even more complicated
> examples, such as the “name” object where given, middle, and sur names
> can be intermingled in sub-objects. IMHO, JSContact makes the same
> mistake of jCard but in the opposite way: where jCard has arrays that
> should be objects, JSContact has objects that should be arrays.
I agree with Andy on this.
Instead of:
"titles": {
"le9": {
"kind": "title",
"name": "Research Scientist"
},
"k2": {
"kind": "role",
"name": "Project Leader"
}
}
We should have:
"titles": [
{
"kind": "title »,
« Id »: « le9",
"name": "Research Scientist"
},
{
"kind": "role »,
« Id »: « k2",
"name": "Project Leader"
}
]
Regards, Marc.
_______________________________________________
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext
