Re: TPAC/Reqs summary

Hi!

> Dear UCR editors, as per the request at the last teleconf, to check
> the requirements against the TPAC discussion, I have gone thru the
> TPAC minutes and mapped the outcome to all the listed wiki
> requirements - see text below.

wow.. thanks a lot Renato!!

I've updated the Req. wiki [1] accordingly.

br,
simon

[1] https://www.w3.org/2016/poe/wiki/Requirements

---
DDipl.-Ing. Simon Steyskal
Institute for Information Business, WU Vienna

www: http://www.steyskal.info/  twitter: @simonsteys

Am 2016-10-20 05:19, schrieb Renato Iannella:
> Dear UCR editors, as per the request at the last teleconf, to check
> the requirements against the TPAC discussion, I have gone thru the
> TPAC minutes and mapped the outcome to all the listed wiki
> requirements - see text below.
> 
> Renato Iannella, Monegraph
> Co-Chair, W3C Permissions & Obligations Expression (POE) Working Group
> 
> 
> ===================
> 
> POE.R.DM.01 Define how constraints on a party can be expressed
>  - Accepted
>  - add Constraint Model to Party and Asset
> 
> POE.R.DM.02 Define target of a constraint
>  - Accepted
>  - add new property to Constrait model to indicate (the assumed)
> subject
> 
> POE.R.DM.03 Introduce policy template
>  - Part Accepted
>  - support inverse target link only: targetURI <hasThis> policyURI
>  - defined by vocabulary (narrative in model)
>  - more/improved use cases needed to support full templates (Action
> on??)
> 
> POE.R.DM.04 Support versioning policies
>  - Part Accepted
>  - improved use cases needed to support validity (Action on??)
> 
> POE.R.DM.05 Set a global price for all permissions of a policy
>  - Satisfied (no action req)
> 
> POE.R.DM.06 Support relative time constraints
>  - Accepted
>  - same solution as POE.R.DM.09
> 
> POE.R.DM.07 Define a category property for class Party
>  - Accepted
>  - by supporting Constraint model for this entity
>  - same solution as POE.R.DM.01
> 
> POE.R.DM.08 Add a category property to Asset
>  - Accepted
>  - by supporting Constraint model for this entity
>  - same solution as POE.R.DM.01
> 
> POE.R.DM.09 Complex Constraints
>  - Accepted
>  - define an updated constraints on constraints model
> 
> POE.R.DM.10 Extended Relations
>  - Part Accepted
>  - improved use cases needed to support ER (Action on??)
> 
> POE.R.DM.11 Remedies
>  - Not Accepted
> 
> POE.R.DM.12 Grouping party entities
>  - Satisfied (no action required)
> 
> POE.R.V.01 Add rights holder terms to Roles of a Party Vocabulary
>  - Not accepted
> 
> POE.R.V.02 Add term for redepositing to Duty Vocabulary
>  - Not accepted
> 
> POE.R.V.03 Add concept of 'unit-of-count' to Duty Constraint
> Vocabulary
>  - Accepted
>  - add unit-of-count to Constraint (ODRL Info Model)
> 
> POE.R.V.08 Add terms to the Action Vocabulary
>  - Not Accepted
> 
> POE.R.V.09 Add Linked Data related actions to Action Vocabulary
>  - Not Accepted
> 
> POE.R.V.10 Add terms to the Roles of a Party Vocabulary
>  - Accepted
>  - add "compensatingParty"
> 
> POE.R.V.11 New Party Category Vocabulary
>  - Satisfied (no action required)
> 
> POE.R.V.12 New Asset Category Vocabulary
>  - Satisfied (no action required)
> 
> POE.R.V.15 Reference to Source License
>  - Accepted
>  - include example in the ODRL Best Practices NOTE (action on??)
> 
> POE.R.E.01 Referring to external resources for defining payment fees
>  - Accepted
>  - include ability to indicate the rightOperand is a reference to the
> value
> 
> POE.R.E.02 Prove that a list of existing licenses can be
> expressed/encoded
>  - Accepted
>  - include examples in the ODRL Best Practices NOTE (action on??)
> 
>  *** The following are un-numbered Requirements***
> 
> Define rules for matching permissions/prohibitions against specific
> use cases
>  - Not Accepted
> 
> Define a language for controlling processing policies
>  - Not Accepted
> 
> Define processing rules for versioned policies
>  - Accepted
>  - include examples in the ODRL Formal Semantics NOTE (action on??)
> 
> Support to auto-generate a policy from a template plus provided
> parameter values
>  - Not Accepted
> 
> Guidance on Rights Assignments through Aggregation and Derivation
>  - Satisfied (no action required)
> 
> Guidance on Specifying Subsets of Assets
>  - Satisfied (no action required)
> 
> Guidance on Conflicting Permissions
>  - Not Accepted
> 
> Guidance on the Provenance of Policies
>  - Accepted
>  - include examples in the ODRL Best Practices NOTE (action on??)
> 
> Make policies accessible by URL
>  - Accepted
>  - include examples in the ODRL Best Practices NOTE (action on??)
> 
> ==============================

Received on Thursday, 20 October 2016 06:38:04 UTC