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

 


Help: OASIS Mailing Lists Help | MarkMail Help

soa-eerp message

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


Subject: [OASIS Issue Tracker] Commented: (SOAEERP-33) PR07-T12Non-normative text in BSLA should be identified.



    [ http://tools.oasis-open.org/issues/browse/SOAEERP-33?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=19446#action_19446 ] 

Szu Chang  commented on SOAEERP-33:
-----------------------------------

Same as SAO-EERp-28, 

>> BSLA spec: Line 672, 860-861 

672 The examples in this section are non-normative. 

860 Note: The separate machine readable schema document, listed on Section 2.2, is normative. The text 
861 included here is non-normative. 

http://www.oasis-open.org/committees/download.php/38432/SOA-EERP-bSLA-spec-wd09-diff-cd03.pdf 


> PR07-T12 Non-normative text in BSLA should be identified.
> ---------------------------------------------------------
>
>                 Key: SOAEERP-33
>                 URL: http://tools.oasis-open.org/issues/browse/SOAEERP-33
>             Project: OASIS Service-Oriented Architecture End-to-End Resource Planning (SOA-EERP) TC
>          Issue Type: Sub-task
>          Components: PR Comments
>            Reporter: Paul Yang 
>            Assignee: Szu Chang 
>
> 13. In BSLA Non-Normative text is Appendix C, preceded by the SML Schema. This should be identified per OASIS rules as non-normative and that the separate XSD file is normative. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


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