[OASIS Issue Tracker] (COEL-126) MMI compliance clause is tricky for a PDS

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

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

Joss Langford updated COEL-126:
-------------------------------

       Assignee: Joss Langford
    Description: 
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.

Reduce PQI & BAP interface compliance requirements to only refer to MMI status section.

  was: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.

       Proposal: 
Change point (d) of 13.5 and 13.6 to read:

It correctly implements the Information Request defined in section 7.2.2 “COEL Minimal Management Interface (MMI)”.

  was:Reduce PQI & BAP interface compliance requirements to only refer to MMI status section.


> 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
>            Assignee: 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.
> Reduce PQI & BAP interface compliance requirements to only refer to MMI status section.



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