[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: Issue 070 - DPWS - Content negotiation for PresentationUrl
I’d like to propose the following text as a resolution
to Issue 070. It is basically what Gottfried originally proposed, except that
the use of HTTP content negotiation (Section 12 of RFC 2616) is permitted
rather than being mandated. Our investigation indicated that content
negotiation based on ACCEPT headers is not universally supported in browsers.
This text at least provides guidance that multiple presentation page formats
can be supported and that at least an HTML page must be supported, and suggests
that HTTP content negotiation is one way to select between multiple presentation
pages. --
Toby Proposed Resolution (changes in red): wsdp:ThisModel/ wsdp:PresentationUrl URL to a
presentation resource for this DEVICE. It MAY be relative to a base URL
and MUST have fewer than MAX_URI_SIZE octets. If PresentationUrl
is specified, the DEVICE MAY provide the resource in multiple formats, but MUST
at least provide an HTML page. CLIENTs and DEVICEs MAY use HTTP content
negotiation [HTTP/1.1] to determine the format and content of the presentation
resource. Subject: Issue 070 - DPWS - Content negotiation for
PresentationUrl
Toby Nixon | Senior Standards Program Manager
| Windows Device and Storage Technologies | Microsoft
Corporation toby.nixon@microsoft.com
| www.microsoft.com | V: +1 425
706 2792 | M: +1 206 790 6377 | F: +1 425 708 4811 |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]