Hi all,
Il 12/07/2021 13:26, Gould, James ha scritto:
Marc,
Thank you for the quick review and feedback. Below are responses to your early
comments:
- would be good to include specific text about jscontact, so when we
switch to it, this document does not need rev.
Agreed, that was thought about while drafting, but we initially left it out.
I'm confident that the extension will work with JSContact, but some text would
help for clarity.
I guess it will work even better than with jCard! JSContact is more
object-oriented than jCard and the json path expressions are simpler
since maps are mostly used to represent collections (e.g.
"$.entities[?(@.roles[0]=='registrant')].jscard.phones.voice.phone"
instead of
"$.entities[?(@.roles[0]=='registrant')].vcardArray[1][?(@[1].type=='voice')]")
Here in the following a first feedback from my side about the document:
- if, as it seems, the "name" property is unique in the "redacted"
array, I would prefer to define "redacted" as a map where the "name"
value is the map key. In theory, every RDAP information can be redacted
but, in practice, the number of RDAP properties usually redacted is
limited. If the possible "name" values were standardized, il would be
easier for RDAP clients implementers to check and pick a property inside
the collection of redacted properties.
- another possible pre-defined value for "pathLang" might be
"jsonpointer" as an alternative syntax to indentify a value within a
JSON doc.
- it seems to me that the document assumes that the role used to
identify the redacted entity within the array of entities should be in
the first position of "roles" array. Maybe such assumption should be
added somewhere in the document.
- there is a typo in the json path expression of "Registrant Street"
Best,
Mario
- I really would like to have an IANA registry for the « reason »
property. Because this would be potentially displayed to the user, and to avoid
having all variations of the same reason in different words. A registry of
reserved words would also facilitate translation in multiple languages.
We had a desire to stay away from needing to setup an IANA registry for
redaction. I view the reason property as not a good candidate for an IANA
registry, since it's meant to be a human readable informational value that
includes normative language not to be used as a client processing dependency.
This is a good discussion item.
Thanks,
--
Dr. Mario Loffredo
Technological Unit “Digital Innovation”
Institute of Informatics and Telematics (IIT)
National Research Council (CNR)
via G. Moruzzi 1, I-56124 PISA, Italy
Phone: +39.0503153497
Web: http://www.iit.cnr.it/mario.loffredo
_______________________________________________
regext mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/regext
