See also: IRC log
<renato> Agenda: https://www.w3.org/2016/poe/wiki/Meetings:Telecon20160808
<michaelS> scribeNick CarolineB
<renato> approve: https://www.w3.org/2016/08/01-poe-minutes
<renato> accepted
renato: we'll go through the use cases,
... leave Mo's since hes not here
<renato> UC.18 https://www.w3.org/TR/poe-ucr/#policyAssertion
renato: ...UC18 comes fro Plus and allows people to assert rights
<renato> requirement: new PolicyType for an "Assertion" of terms
smyles: who is making the assertion. Is there a difference?
renato: its someone managing rights on behalf of another. No validation is implied (answering benws)
<renato> UC.19 https://www.w3.org/TR/poe-ucr/#relTimeConstraint
michaelS: It's temporal, allowed to do something before or after the event, but no exact time for the end.
<simonstey> https://www.w3.org/TR/2016/WD-owl-time-20160712/ ?
michaelS: so we need something more than fixed date and time
renato: there is an event constraint, could it work for this?
michaelS: it needs to be related to a time
<simonstey> "elapsedTime" - A period of time in which the policy action can be exercised. The start of the period is when the action is first exercised.
smyles: talks about how you "know" the event
has happened and how it is commonly handled by organisations
... if we buld it in will it be used?
michaelS: remembers this UC comes from
earlier discussion re sport
... often written in natural language
<simonstey> meteredTime The maximum period of metered usage time Value must conform to [ISO-8601] as represented in [W3CXMLSCHEMA]. For example “P30H” indicates a 30 hour period.
<simonstey> timeInterval Recurring period of time in which the usage may be exercised Interval value must conform to [ISO-8601] as represented in [W3CXMLSCHEMA]. For example, “P7D” indicates a 7 day period.
michaelS: don't need a description of event only an identifier of it
benws: wonders what ODRL needs for this. Agrees Michael just an identifier
<simonstey> +q
<smyles> https://www.w3.org/TR/2016/WD-owl-time-20160712/
renato: we'll look at the OWL temporal spec
and see what can be used for an encoding agnostic solution
... we've covered all we can in the UC doc for now
... we need the originators to cover the reamining ones
... so - now we look at actions
<renato> https://www.w3.org/2016/poe/track/actions/17
<renato> https://www.w3.org/2016/poe/track/actions/open
benws: how many people do we need on the
call for decisions re names
... clarifies list is a list of roles
sabrina: claims interesting action names
<renato> https://www.w3.org/2016/poe/track/issues/raised
renato: need to do a horizontal list of
deliverables. Need a privacy/security review
... editors, will you put the requirements into the WIki first?
<ivan> trackbot, end telcon