CAWG & TRQP

[darrellodonnell]

Copied from Slack @Scott Perry in our other chat you asked about what a trust registry needs - data wise - to "do it's thing".

TRQP needs 4 parameters (plus some optional). I will use an example of a photojournalist publishing a photo so there are some working examples (npte: IPTC will need to come up with it's view of what it is authoritative for. I may have it very wrong in this example).

• entity_id - the identifier of the entity you are querying about - likely, in the CAWG assertion, the creator that is making the assertion (e.g. a photojournalist). This value will be used by the trust registry so must match in that trust registry.
• action - what action are you querying about (e.g. "publish")
• resource - what resource are you querying about (e.g. "photo.journalist.approved" for a photo that a credentialed journalist is making an assertion about)
• authority_id - the authority that the assertion is made under (e.g. "did:webvh:ABC123:iptc.org:registry" )

[byh-trufo]

The ultimate consumer of these fields seems to be the Validator, so perhaps it would be good to discuss from the angle of, given these fields, how should the Validator change how the content is displayed?

For example, for IPTC VNP, the Validator may want to label any content published by the BBC (that they label as news?) as "news". In order to do so, the Validator would check the TRQP response that the BBC is authorized by the IPTC to publish the content as news. This also requires the Validator to know that the IPTC is the "correct" authority to reference when deciding whether to display the "news" label.

For implementation, perhaps each GA would need to coordinate with Validators for the Validators to implement the consumption of the field. In order for this to scale, perhaps the GAs would publish (when they register with CAWG?) some schema that Validators can easily look up and implement.

[darrellodonnell]

As an example, from looking at the RIAA site about licensing, I can start with the following:

From "Display the work publicly.":

• Action: display
• Resource: work.recordedmusic

From "Create a derivative work.":

• action: derive
• resource: work.recordedmusic

The Entity, in both cases, would need relationship with the work's copyright owners, but that is out of scope for the assertion. The Entity (entity_id) is saying "I have the authority to Display the work publicly, and I am saying this under the authority (authority_id) of my membership in RIAA".