Josh Cornejo

I find the wording of access control and monitoring confusing. I would need a sequence diagram to understand the difference. My understanding from the text is: _that any monitoring scenario...

Examples 1 - 4: - `odrl:target pd:BankAccount ;` // [pd:BankAccount](https://w3c.github.io/dpv/2.1/pd/#BankAccount) isn't an [odrl:Asset](https://www.w3.org/TR/odrl-model/#rule) "_A Rule MAY have none or one relation sub-property values of type Asset_".

So `dpv:ResearchAndDevelopment` is part of the `dpv:vocab-purpose` taxonomy. As per my answer on the email exchange, the 3 scenarios I can foresee: Option 1: ``` odrl:leftOperand odrl:purpose ; odrl:operator odrl:eq...

My thoughts, - `odrl:eq` is part of the set (`:lt, :gt, :lteq, :gteq, :neq`) across some linear values that can be instance evaluated and can be in order; you should...

Hopefully a simpler example. How do I represent this in ODRL? This is a prohibition: Contract says I **MUST NOT do any Advertising**. Data graph says I am doing Advertising....

No opposition - I would just suggest that the input and output models keep some compatibility with other ACL languages. Specifically [AuthZen](https://openid.github.io/authzen/) that is geared towards interoperability.

Yes, I have this view in the long term. I have API endpoint that produce JSON-LD or TTL, those should (at some point) resolve to any "over the public" internet...

From what Joaquin mentioned during a call with him a couple of weeks ago - and aligned with what I think - first comes "how will people with 'content' expertise...

BTW - MQTT is for Telemetry, I would think AMQP suits better?

More than one refinement is done by [logical constraints](https://www.w3.org/TR/odrl-model/#constraint-logical) and their operators (and, or, xone, andSequence). ``` md:uri:225b96258645:23249 a odrl:Action; rdf:value odrl:concurrentUse, odrl:play; odrl:refinement md:uri:225b96258645:23250. md:uri:225b96258645:23250 a odrl:LogicalConstraint; odrl:and md:uri:225b96258645:23251,...