User Activity

  • Modified ticket #15 on SDC

    QName handling is partially undefined for DPWS/WS-Discovery

  • Modified ticket #30 on SDC

    Add means to identify a consumer in RR & Eventing

  • Posted a comment on ticket #30 on SDC

    Added optional mdpws:ClientInfo SOAP header block for consumer identification, type, friendly metadata, and priority in request and Eventing messages. The mdpws26:ClientInfo SOAP header block has the following form: (01)<mdpws26:clientinfo consumerid="xs:anyURI" ?="" clienttype="xs:anyURI" priority="xs:nonNegativeInteger" ...=""> (02) <dpws:thismodel> ... </dpws:thismodel>? (03) <dpws:thisdevice> ... </dpws:thisdevice>? (04) … (05) </mdpws26:clientinfo>

  • Modified ticket #29 on SDC

    Basic Profile requirement unfulfillable

  • Posted a comment on ticket #29 on SDC

    Clarified that STREAMs excluded by R0009 are not WSDL operations for bp20:R2710 operation-signature uniqueness evaluation. NOTE 2—STREAMs excluded by R0009 are not described as WSDL Notification or Solicit-Response operations by this standard. Therefore, those STREAMs are not WSDL operations for which bp20:R2710 operation-signature uniqueness is evaluated. bp20:R2710 continues to apply to other WSDL operations.

  • Modified a comment on ticket #28 on SDC

    Added a note in Eventing clause. NOTE 2—WS-Eventing [B32] permits wse:Expires values in Subscribe, SubscribeResponse, Renew, RenewResponse, and GetStatusResponse MESSAGEs to be expressed as xs:dateTime or xs:duration. For MDPWS deployments, use of xs:duration values for wse:Expires is recommended because a relative subscription lifetime avoids a dependency on synchronized clocks between the CLIENT and SERVICE. As with other xs:duration values, implementations can restrict accepted values to day and...

  • Modified ticket #27 on SDC

    Enforce UUIDs for device EPR addresses

  • Posted a comment on ticket #27 on SDC

    Added an informative note recommending urn:uuid scheme endpoint reference addresses; no requirement changed for backwards compativility reasons. NOTE—dpws:R0004 recommends that a DEVICE use an IRI with the urn:uuid scheme as the [address] property of its endpoint reference. Use of an IRI with the urn:uuid scheme is also recommended for MDPWS DEVICEs because it provides a stable, globally unique identifier with a predictable lexical form for discovery correlation, storage, indexing, and use in external...

View All

Personal Data

Username:
schlich09
Joined:
2011-11-24 09:55:41
Location:
CEST
Gender:
Male

Projects

This is a list of open source software projects that Stefan Schlichting is associated with:

  • PoCSpec   Last Updated:
  • SDC SDC facilitates development of dist. systems of medical devices. Last Updated:

Personal Tools

Monday.com Logo