[OASIS Issue Tracker] (COEL-54) Machine-readable consent terms

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://issues.oasis-open.org/browse/COEL-54?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=62544#comment-62544 ] 

Paul Bruton commented on COEL-54:
---------------------------------

Reviewed David's latest revision (18) and tidied up some of the track markup just for readability. I added a comment, repeated here, relating to the 'required' field of the consent elements. All are currently optional but I imagine there must be some dependencies between these elements:

"Are there some ‘conditions’ here. For example if we have WebTokenID, must we also have a ReceiptService? Should we always require an Expiry Date – does the absence of a date mean consent forever? Can we have PolicyURL without Jurisdiction?"

I'm just not sure what a well-formed element section would look like.

> Machine-readable consent terms
> ------------------------------
>
>                 Key: COEL-54
>                 URL: https://issues.oasis-open.org/browse/COEL-54
>             Project: OASIS Classification of Everyday Living (COEL) TC
>          Issue Type: New Feature
>            Reporter: Joss Langford
>            Assignee: Joss Langford
>
> COEL does not currently support machine readable consent terms and this could be added to every atom



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)