Use-case idea about rch-wg-charter HOT 5 CLOSED

In the particular case of an EARL report we could probably use a simpler mechanism where the commit that last modified the manifest(s) could be used both in the rollup implementation report.

Note that the EARL vocabulary doesn't have any notion of test manifest (only individual test URIs) and we'd need some vocabulary extensions to described manifests and their hashes, and there may be multiple manifests involved with a given report (e.g., SPARQL and JSON-LD). I typically add an earl:Report class and earl:assertion properties that serve as useful connective elements, and the Report might reference a hash of the manifests that were used, along with the URIs of those manifests, but if the hash isn't part of the manifest itself, it might be a high burden for implementors to calculate this hash.

As the implementation report incorporates elements of the manifests and the individual EARL reports submitted by implementors, it may be that an individual report should be ignored if the timestamp of the submission file is older than any of the manifests which include tests that it reports on.

It might be a reasonable time for a CG to give EARL an update.

from rch-wg-charter.

Sounds good to me. Now we have to be able to describe in some succinct form that even people who do not know what EARL is would understand...

from rch-wg-charter.

Yes @pchampin, that's a valid use case... related:

https://www.w3.org/TR/vc-imp-guide/#referencing-other-credentials

from rch-wg-charter.

@pchampin do you think you can put in a use case to the explainer? Having such use cases is important...

I would prefer to close this issue once a PR is there. Let us not give the impression that there are still open issues re charter...

from rch-wg-charter.

@gkellogg Thx for these precisions on EARL. Indeed, this would need to be thought through in more detailed. +1 to give EARL an update :)
@iherman I created PR #58 which adds a new UC, slightly more general than the one suggesed above. I will therefore close this issue, the discussion can now happen on in #58.

from rch-wg-charter.