OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

coel message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [OASIS Issue Tracker] (COEL-85) Definition of consent record ID


     [ https://issues.oasis-open.org/browse/COEL-85?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul Bruton updated COEL-85:
----------------------------

    Description: 
The consent section of BAP specifies a WebTokenID. This might be too specific as it is possible to use a smaller ID as long as is is a unique reference for the ReceiptService.

The larger web token also has the possibility of containing a subject ID - this is not a problem if it is encrypted and we don't have a key but we may need to specify this.

Also, we may want to consider the more generic reference to a ConsentRecord where a consent receipt is an example.

  was:
The consent section of BAP specifies a WebTokenID. This might be too specific as it is possible to use a smaller ID as long as is is a unique reference for the ReceptService.

The larger web token also has the possibility of containing a subject ID - this is not a problem if it is encrypted and we don't have a key but we may need to specify this.

Also, we may want to consider the more generic reference to a ConsentRecord where a consent receipt is an example.


> Definition of consent record ID
> -------------------------------
>
>                 Key: COEL-85
>                 URL: https://issues.oasis-open.org/browse/COEL-85
>             Project: OASIS Classification of Everyday Living (COEL) TC
>          Issue Type: Improvement
>         Environment: BAP - consent field
>            Reporter: Joss Langford
>            Priority: Minor
>
> The consent section of BAP specifies a WebTokenID. This might be too specific as it is possible to use a smaller ID as long as is is a unique reference for the ReceiptService.
> The larger web token also has the possibility of containing a subject ID - this is not a problem if it is encrypted and we don't have a key but we may need to specify this.
> Also, we may want to consider the more generic reference to a ConsentRecord where a consent receipt is an example.



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


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]