ODRL evaluator implementation report

[AndreaCimminoArriaga]

This comment is related to the formal semantics document. It is to be expected to have multiple implementations of the ODRL evaluator, it would be a nice-to-have feature that the evaluators must provide and specify which operands, operators, and actions they support (pointing specifically to their ontology definitions). Related to issue #67 it would be nice that an ODRL service provides an RDF document where it specifies what operands, operators, and actions they support.

[joshcornejo]

There used to be a wiki for the evaluators - https://www.w3.org/2016/poe/wiki/Evaluator - we could set up a couple of hours per month to kickstart and create a few use cases - then add them on demand.

I think the latter part of your issue (ODRL service provides an RDF document where it specifies what operands, operators, and actions they support) is the purpose of a profile.

[AndreaCimminoArriaga]

I read the profile, but saw nothing about the result or the input for an ODRL evaluator. Maybe the vocabulary can be used, but I think the evaluation deserves a more specific set of terms aligned with the tables from the formal semantics that display the examples of the evaluation