Re: WS-I Basic Profile Version 1.0

[Randy Charles Morin <randymorin@xxxxxxxxx>]

Further to my previous post on WS-I Basic Profile

http://www.imc.org/atom-syntax/mail-archive/msg03758.html

 

Here are the items that I think AtomAPI should address, not SOAP/WSDL specific, for interop sake, that I don't believe have already been addressed in the AtomAPI spec.
http://bitworking.org/projects/atom/draft-gregorio-09.html

 

R4001 A RECEIVER MUST accept messages that include the Unicode Byte Order Mark (BOM).C

http://www.ws-i.org/Profiles/BasicProfile-1.0-2004-04-16.html#R4001

R1008 A MESSAGE MUST NOT contain a Document Type Declaration. C
http://www.ws-i.org/Profiles/BasicProfile-1.0-2004-04-16.html#R1008

R1009 A MESSAGE MUST NOT contain Processing Instructions. C
http://www.ws-i.org/Profiles/BasicProfile-1.0-2004-04-16.html#R1009

R1012 A MESSAGE MUST be serialized as either UTF-8 or UTF-16.
http://www.ws-i.org/Profiles/BasicProfile-1.0-2004-04-16.html#R1012
I hate this one, as per my previous posts.

R1140 A MESSAGE SHOULD be sent using HTTP/1.1.
http://www.ws-i.org/Profiles/BasicProfile-1.0-2004-04-16.html#R1140

R1141 A MESSAGE MUST be sent using either HTTP/1.1 or HTTP/1.0.
http://www.ws-i.org/Profiles/BasicProfile-1.0-2004-04-16.html#R1141

R1132 A HTTP request MESSAGE MUST use the HTTP POST method.
http://www.ws-i.org/Profiles/BasicProfile-1.0-2004-04-16.html#R1132

R1110 An INSTANCE MAY accept connections on TCP port 80 (HTTP).
http://www.ws-i.org/Profiles/BasicProfile-1.0-2004-04-16.html#R1110

R1130 An INSTANCE MUST use HTTP status code "307 Temporary Redirect" when redirecting a request to a different endpoint.
http://www.ws-i.org/Profiles/BasicProfile-1.0-2004-04-16.html#R1130

R1131 A CONSUMER MAY automatically redirect a request when it encounters a "307 Temporary Redirect" HTTP status code in a response.
http://www.ws-i.org/Profiles/BasicProfile-1.0-2004-04-16.html#R1131

R1114 An INSTANCE SHOULD use a "405 Method not Allowed" HTTP status code if the request method was not "POST".
http://www.ws-i.org/Profiles/BasicProfile-1.0-2004-04-16.html#R1114

R1115 An INSTANCE SHOULD use a "415 Unsupported Media Type" HTTP status code if the Content-Type HTTP request header did not have a value consistent with the value specified for the corresponding binding of the input message.
http://www.ws-i.org/Profiles/BasicProfile-1.0-2004-04-16.html#R1115

R1121 An INSTANCE SHOULD NOT require consumer support for Cookies in order to function correctly.
http://www.ws-i.org/Profiles/BasicProfile-1.0-2004-04-16.html#R1121

R5000 An INSTANCE MAY require the use of HTTPS.
http://www.ws-i.org/Profiles/BasicProfile-1.0-2004-04-16.html#R5000

Notes

• AtomAPI is not WSDL 1.1 capable, but it looks like it'll be WSDL 2.0. That's why I left out the WSDL interop concerns. No use shooting a dead horse.
• The REST version of AtomAPI is not SOAP, so I left out the SOAP interop concerns, but the SOAP Atom interface should be fully compliant. Not addressed here.

Thanks,

Randy
http://www.kbcafe.com

PS. Sorry for any Yahoo! footer that follows, but GMail was non-functional when I was sending.

---

Do you Yahoo!?
SBC Yahoo! - Internet access at a great low price.