RE: [ws-rx-editors] A review of the references to resolve issue i057

Title: A review of the references to resolve issue i057

Guys, 

 

If there are no issues, I will submit to this to the tc. I 
also propose to align the names of the schema references such as XML-Schema1 
--> XML-Schema Part1 in both documents for consistency. 

 

Just let me know by EOB tomorrow. 

 

Thanks. 

 

--umit

 

  

  
  From: Yalcinalp, Umit 
Sent: 
  Wednesday, Dec 07, 2005 3:15 PM
To: Yalcinalp, Umit; 
  
Subject: RE: [ws-rx-editors] A 
  review of the references to resolve issue i057

  

  
I have been told that there is a slight varience in the 
  line numbers for WSRMP for schema references being slightly off. 
  

  
 

  
For wsrmp, replace line numbers for schema references 
  should read 253-256 instead, instead of 251-254. 

  
 

  
Thanks.  

  
 

  
--umit

  
 

  
    

    
    From: Yalcinalp, Umit 
    [mailto:] 
Sent: Wednesday, Dec 07, 2005 
    12:57 PM
To: 
Subject: 
    [ws-rx-editors] A review of the references to resolve issue 
    i057

    

    
Folks I checked the wsrm (07) and wsrmp (02) 
    documents. 

    
Here is what we should propose as the editors 
    team. Let me know whether you have any issues with this. If we do not come 
    to an agreement, I will ask the tc to make the decision. 

    
--------------------------------------------------- 

    
Wsrm spec (07) from pdf: 

    
This spec is pretty right on target, except the 
    following couple of cases: 

    
6 References 
    
6.1 Normative 
    

    
[KEYWORDS] 
    
S. Bradner, "Key words for use in RFCs to Indicate 
    Requirement Levels," RFC 
    2119, Harvard University, 
March 1997 
[SOAP] 
W3C 
    Note, "SOAP: Simple Object 
    Access Protocol 1.1," 08 May 
    2000. 
[URI] 
T. 
    Berners-Lee, R. Fielding, L. Masinter, "Uniform Resource Identifiers (URI): Generic 
    Syntax," RFC 3986, 
    
MIT/LCS, U.C. Irvine, Xerox 
    Corporation, August 1998. 
[XML-ns] 
W3C Recommendation, "Namespaces in XML," 14 January 1999. 

    
The following two references in 
    lines 835-838 are not used anywhere. I propose putting the following 
    normative references in Appendix A changing line 858 to 

    
{The normative schema that is defined using 
    [XML-Schema1] and [XML-Schema2] for WS-ReliableMessaging is located 
    at… 
} 
[XML-Schema1] 
W3C Recommendation, "XML Schema Part 1: Structures," 2 May 2001. 
[XML-Schema2] 
W3C Recommendation, "XML Schema Part 2: Datatypes," 2 May 2001. 

    
The following reference is not 
    normative in line 839-841. It should be moved to Non-Normative Section. 
    

    
[WSSecurity] 
    
"OASIS Web Services Security: SOAP Message Security 1.0 
    (WS-Security 2004)", Anthony 
    Nadalin, 
Chris Kaler, 
    Phillip Hallam-Baker, Ronald Monzillo, eds, OASIS Standard 200401, March 
    2004. 

    
The following reference in Line 
    842-843 is not really normative either. Either the language in the spec that 
    uses it needs to change to SHOULD or it should be moved to Non-Normative. 
    

    
[RTTM] 
    
V. Jacobson, R. Braden, D. 
    Borman, "TCP Extensions for 
    High Performance", RFC 1323, 
    May 1992. 

    
[WSDL] 
    
W3C Note, "Web Services Description Language (WSDL 
    1.1)," 15 March 2001. 
    

    
Note: We deferred this one. 
    

    
[WS-Addressing] 
D. Box, et al, "Web 
    Services Addressing (WS-Addressing)," August 2004. 

    
6.2 
    Non-Normative 
[WS-Policy] 
D. 
    Box, et al, "Web Services 
    Policy Framework (WS-Policy)," September 2004. 
[WS-PolicyAttachment] 
D. Box, et al, "Web Services Policy Attachment (WS-PolicyAttachment)," September 2004. 
[SecurityPolicy] 
G. Della-Libra, "Web Services Security Policy Language 
    (WS-SecurityPolicy)," 
    December 2002. 
[SecureConversation] 
S. Anderson, et al, "Web Services Secure Conversation Language 
    (WS-SecureConversation)," May 
    2004. 

    
-----------------------------------------------------------------------------------------------------------------------------

    
WSRMP (02) from PDF: 

    
Since all the references were non-normative, here 
    is my proposed classification: 

    
4 References 
    
4.1 Normative 
    
[KEYWORDS] 
    
S. Bradner, "Key words for use 
    in RFCs to Indicate Requirement Levels," RFC 2119, Harvard 
    University, 
March 
    1997. 
[SOAP] 
W3C 
    Note, "SOAP: Simple Object Access Protocol 1.1," 08 May 2000. 
    
[URI] 
    
T. Berners-Lee, R. Fielding, L. 
    Masinter, "Uniform Resource Identifiers (URI): Generic Syntax," RFC 
    2396, 
MIT/LCS, U.C. 
    Irvine, Xerox Corporation, August 1998. 
[WS-RM] 
R. Bilorusets, et all, "Web Services 
    Reliable Messaging (WS-ReliableMessaging)," February 2005. 
    
[WS-Policy] 
    
D. Box, et al, "Web Services 
    Policy Framework (WS-Policy)," September 2004. 
[WS-PolicyAttachment] 
    
D. Box, et al, "Web Services 
    Policy Attachment (WS-PolicyAttachment)," September 2004. 
    
[WSDL 1.1] 
    
W3C Note, "Web Services 
    Description Language (WSDL 1.1)," 15 March 2001. 
[XML] 
W3C Recommendation, "Extensible Markup 
    Language (XML) Third Edition," 4 February 2004. 
[XML-ns] 
W3C Recommendation, "Namespaces in XML," 
    14 January 1999. 

    
Again we do not have any 
    references to the [XML Schema1] and [XML Schema2] (lines: 251-254). But we 
    have references to XML Schema Part1 and XML Schema Part2 and align the spec 
    in the lines. I suggest we change the names in lines 251-254 to 

    
[XML-Schema 
    Part1] 
W3C 
    Recommendation, "XML Schema Part 1: Structures," 2 May 2001. 
    
[XML-Schema 
    Part2] 
W3C 
    Recommendation, "XML Schema Part 2: Datatypes," 2 May 2001. 

    
4.2 
    Non-Normative 
[WSS] 
OASIS 
    Web Services Security: SOAP Message Security 1.0 (WS-Security 2004)", Chris 
    Kaler, Phillip 
Hallam-Baker, Ronald Monzillo, eds, OASIS Standard 200401, March 
    2004. 

    
---------------------- 

    
Dr. Umit Yalcinalp 
Standards Architect 
    
NetWeaver Industry Standards 
SAP Labs, LLC 
 
Tel: (650) 
    320-3095