[OASIS Issue Tracker] (WSCALENDAR-572) Conformance targets not well-defined in PIM

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

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

William Cox updated WSCALENDAR-572:
-----------------------------------

    Affects Version/s: PIM CS01
                           (was: MIN CSDPR01)
          Environment: TAB Review of MIN 201602. Cross reference to full issue WSCALENDAR-571  (was: TAB Review)
          Component/s: PIM
                           (was: MIN)

> Conformance targets not well-defined in PIM
> -------------------------------------------
>
>                 Key: WSCALENDAR-572
>                 URL: https://issues.oasis-open.org/browse/WSCALENDAR-572
>             Project: OASIS Web Services Calendar (WS-Calendar) TC
>          Issue Type: Bug
>          Components: PIM
>    Affects Versions: PIM CS01
>         Environment: TAB Review of MIN 201602. Cross reference to full issue WSCALENDAR-571
>            Reporter: Toby Considine
>            Assignee: William Cox
>
> The conformance targets or possible implementations that are subject to conformance are not well defined: we read "Implementations and specifications " in the conformance clause. These need be defined even if only intuitively. What is the difference between Implementations and specifications ? Can we use another term than "specifications" which is rather overloaded (also used for "this specifications" - are we talking of different classes of specifications?). At some other place we read "an application or specification..." - needs be defined too in this context. The base specification (PIM V1.0) also uses "specifications" as conformance target, but not defined. 



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