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-126) MMI compliance clause is tricky for a PDS


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

David Snelling commented on COEL-126:
-------------------------------------

Note that we require that the ConsumerID not be used outside the ecosystem. How does this affect the PDS uase case.

> MMI compliance clause is tricky for a PDS
> -----------------------------------------
>
>                 Key: COEL-126
>                 URL: https://issues.oasis-open.org/browse/COEL-126
>             Project: OASIS Classification of Everyday Living (COEL) TC
>          Issue Type: Bug
>         Environment: Complaince
>            Reporter: Joss Langford
>            Priority: Minor
>
> The compliance for PQI and BAP interface currently requires the whole of the MMI. In fact, it only needs the status request. This inhibits applications around Personal Data Stores.



--
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]