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

 


Help: OASIS Mailing Lists Help | MarkMail Help

ws-calendar message

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


Subject: [OASIS Issue Tracker] (WSCALENDAR-571) conformance targets not well-defined


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

William Cox commented on WSCALENDAR-571:
----------------------------------------

Cross reference to PIM issue: WSCALENDAR-572

> conformance targets not well-defined
> ------------------------------------
>
>                 Key: WSCALENDAR-571
>                 URL: https://issues.oasis-open.org/browse/WSCALENDAR-571
>             Project: OASIS Web Services Calendar (WS-Calendar) TC
>          Issue Type: Bug
>          Components: MIN
>    Affects Versions: MIN CSDPR01
>         Environment: TAB Review
>            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)


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