March 09, 2006

Devices Profile Republished

Today we republished the Devices Profile for Web Services spec based on community feedback received and implementation experience. Mostly it's to clean up some things around device metadata, plus some other minor housekeeping.

This version of the Devices Profile specification is expected to be the last revision before submission to a standards organization, and it matches what will be shipping in Windows Vista.

The Change Log from the previous version is below, for those who are interested.

Change Log for 2006-02 republication of Devices Profile for Web Services

General Clarifications and Tidy-up

  • Corrected use of urn:uuid URIs (R0004)
  • Enforce request-response semantics for HTTP messaging (R0031)
  • Clarified the default wsa:RelatesTo header value of wsa:Reply should not appear on the wire for request-response (R0019)
  • More consistent use of the phrase "HOSTED SERVICE"

Device Metadata & Retrieval Cleanup

  • Switched to using wsdp:Device to indicate a DEVICE type in WS-Discovery sign-on and probe responses (R1020)
  • Switched to using WS-Transfer Get to access DEVICE or SERVICE metadata
  • Clarified there is no requirement to support other WS-Transfer operations other than Get (R2045)
  • Clarified a DEVICE must use wsx:Metadata format when responding to metadata retrieval operations (R2044)
  • Clarified a DEVICE must return ThisModel data when responding to metadata retrieval operations (R2012)
  • Clarified a DEVICE must return ThisDevice data when responding to metadata retrieval operations (R2014)
  • Clarified a DEVICE must return Relationship data when responding to metadata retrieval operations (R2029)
  • Clarified meaning of the wsdp:Relationship data for HOSTED SERVICEs
  • wsdl:ServiceId is mandatory for both wsdp:Host and wsdp:Hosted
  • wsdl:ServiceId values must be unique within a DEVICE
  • wsdp:Host and wsdp:Hosted can include more than one endpoint reference
  • Clarified meaning of single vs multiple wsdp:Hosted sections
  • Clarified a HOSTED SERVICE must return Relationship data when responding to metadata retrieval operations (R2029)
  • Clarified a HOSTED SERVICE must return WSDL data when responding to metadata retrieval operations (R2016)
  • Clarified that a HOSTED SERVICE is not required to provide WSDL containing endpoint addressing data already provided in device metadata (R2043)
  • Clarified that HOSTED SERVICEs have multiple ways to return WSDL info by reference (R2031)
  • Removed the requirement to increment MetadataVersion value whenever WSDL data changes (R2021)
  • Clarified a HOSTED SERVICE that used WS-Policy must return policy data when responding to metadata retrieval operations (R2025)
  • Removed the requirement to increment MetadataVersion value whenever WS-Policy data changes (R2022)

Clean up Device Policy Assertions

  • Removed DP-specific policy assertions for MTOM - wsdp:OptimizedMimeSerialization flag in device policy data (R2011)
  • Removed DP-specific policy assertions for WS-Eventing - wsdp:PushDelivery, wsdp:DurationExpiration and wsdp:ActionFilter (R2032, R2033, R2034)
  • Removed DP-specific security policy assertions - wsdp:Tls and wsdp:X509Cert
Entry categories: Microsoft Standards Web Services
Posted by Jorgen Thelin at March 9, 2006 10:00 AM - [PermaLink]
 
Traceback List
Another Busy Time for Web Services Standards
Excerpt: It's been another busy few weeks in the Web Services Standards Team at Microsoft recently! Last week, we did another republication of the Devices Profile and WS-Policy specs. Today the W3C acknowledged and published our Member Submissions of the WS-Ev...
Weblog: TheArchitect.co.uk - Jorgen Thelin's weblog
Tracked: March 15, 2006 04:53 PM