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

 


Help: OASIS Mailing Lists Help | MarkMail Help

ws-dd message

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


Subject: Proposed Resolution Issue 074 - DPWS - Purpose behind dup requirements?



DPWS - Purpose behind dup requirements?
 
 
Section 3.6 says:

R0036: A SERVICE MAY reject a MIME SOAP ENVELOPE if the Content-Transfer-Encoding header field mechanism of any MIME part is not "binary".

R0037: A SERVICE MUST NOT send a MIME SOAP ENVELOPE unless the Content-Transfer-Encoding header field mechanism of every MIME part is "binary"


There are several requirements like this.  Is the purpose behind this to allow a service to have more flexibility than the client, which might be constrained?  

If so we should probably say this up front so people don't view this as an inconsistency.


Proposed Resolution (changes in
red):
add clarification:


While DPWS-compliant services are required to support binary encoded MIME parts at a minimum, R0036 allows for them to support others (non-DPWS compliant clients) if they choose.  While a service might choose to support more than what is required in DPWS, a DPWS-compliant client cannot assume that the service it is interacting with supports anything beyond binary MIME parts
.


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