Hi James,
I have experienced the use case where multiple contacts have the same
role but not all of them are redacted.
Hence, a JSONPath where redacted contacts are identified by filtering
the enties only by role is not good.
Possible alternatives are:
- appending an index selector to indentify the redacted contacts among
those having the same role (e.g.
$.entities[?(@.roles[0]=='technical')][0]). This option seems to be
allowed by jsonpath-base doc but I haven't yet found an online JSONPath
evaluator supporting it. This make me think that libraries supporting
JSONPath might not handle it at least presently.
- using only the index selector regardless of the role (e.g.
$.entities[1]). This option is surely allowed and supported but doesn't
convey the concept that redaction is applied depending on contact role.
Should this case be treated in Section 5 to provide guidance for
implementers ?
Best,
Mario
--
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
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext
