SourceForge : View Wiki Page: WebServicesTopicsV1.3

Search Wiki Pages Project: scrm-wg Wiki > WebServicesTopicsV1.3 > View Wiki Page

wiki1521: WebServicesTopicsV1.3

Standard

1. The name of the specification

Web Services Topics (WS-Topics) 1.3

2. A short statement (<100 words) of the purpose and function of the specification

This document defines a mechanism to organize and categorize items of interest for subscription known as "topics". These are used in conjunction with the notification mechanisms defined in WS-BaseNotification. WS-Topics defines three topic expression dialects that can be used as subscription expressions in subscribe request messages and other parts of the WS-Notification system. It further specifies an XML model for describing metadata associated with topics.

3. The version number (or other distinct identifier) and date of the most recently approved version of the specification.

Public Review period for Committee Draft WS-Topics V1.3

4. If the specification is part of a group of explicitly related specifications from the same source, the name of the group of specifications.

WS-Notification is a family of related specifications that define a standard Web services approach to notification using a topic-based publish/subscribe pattern. It includes: standard message exchanges to be implemented by service providers that wish to participate in Notifications, standard message exchanges for a notification broker service provider (allowing publication of messages from entities that are not themselves service providers), operational requirements expected of service providers and requestors that participate in notifications, and an XML model that describes topics. The WS-Notification family of documents includes three normative specifications: WS-BaseNotification, WS- BrokeredNotification, and WS-Topics.

5. URI for the normative text of the specification

WS-Topics - http://docs.oasis-open.org/wsn/wsn-ws_topics-1.3-spec-pr-01.pdf

SOURCE

6. The name of the SDO that generated/authored/hosted the specification.

OASIS

7. URI for the SDO

http://www.oasis-open.org

8. The level of approval that the SDO has conferred on the specification as described by the SDO's process.

OASIS Committee Draft

9. The language or languages in which the specification is available.

US English

SUBJECT

10. Which of the ITU-T TMN FCAPS model layers does the specification's functionality address?

(http://en.wikipedia.org/wiki/FCAPS, http://www.futsoft.com/pdf/fcapswp.pdf) Fault Management: Fixing broken resources. Configuration Management: Controlling a resource's operational parameters. Accounting Management: Recording and analyzing resource use. Performance Management: Controlling speed and efficiency of resource use. Security Management: Controlling access to resources.

12. Where does the specification directly operate, as among the layers defined in the ISO Open System Interconnect (OSI) model?

(http://www.looselycoupled.com/opinion/2003/saruk-osi-infr0905.html ) Physical layer Data link layer Network layer Transport layer Session layer Presentation layer Application layer.

13. Which of the following (CIM based) functional areas does the model of the specification address?

(http://www.dmtf.org/standards/cim/)

Policy Management Infrastructure Physical Networks Logical Networks Physical Systems Logical Systems Physical Devices Logical Devices Physical Storage Logical Storage Operating Systems Databases Application Servers Applications Users Security Support

OPTIONAL

14. The level of approval of the specification in this generic lifecycle taxonomy: Product Availability

Proposed work Contributions received Preliminary SDO draft Initial public review Final approval Product availability End-of-life (superseded, withdrawn, etc.)

15. URI for the applicable SDO's patent and copyright rules, if any, applicable to development and use of the specification.

http://www.oasis-open.org/who/intellectualproperty.php

16. URI for the SDO's posting location, (if any) for notices from participants or individuals regarding claims under the rules stated under number 15.

17. Interoperability, conformance, or certification test activity for the specification (by owner name or URI).

18. Known implementations of the specification (by owner name or URI).

Open Source Apache Foundation Implementation with contributors: HP, Globus, Hitachi, and others

http://ws.apache.org/ws-fx/pubscribe/

19. A list (or URI pointer to same) of the other specifications* that are normatively referenced in the specification.

RFC2119 S. Bradner, Key words for use in RFCs to Indicate Requirement Levels, http://www.ietf.org/rfc/rfc2119.txt, IETF RFC 2119, March 1997.

WS-BaseNotification http://docs.oasis-open.org/wsn/wsn-ws_base_notification-1.3-spec-pr-02.pdf

WS-BrokeredNotification http://docs.oasis-open.org/wsn/wsn-ws_brokered_notification-1.3-spec-pr-02.pdf

WS-ResourceProperties http://docs.oasis-open.org/wsrf/wsrf-ws_resource_properties-1.2-spec-pr-02.pdf

XML http://www.w3.org/TR/REC-xml

XML-Infoset http://www.w3.org/TR/xml-infoset/

XML-Namespaces http://www.w3.org/TR/xml-names11/

XPATH http://www.w3.org/TR/xpath

20. A list (or URI pointer to same) of the other specifications* that are referenced in the specification (except the ones listed under number 19).

21. A list (or URI pointer to same) of other specifications* with which the specification may (speculatively) interoperate or act in complementary, compatible fashion.

22. A list (or URI pointer to same) of other specifications* similar to this specification. (Whether or not substitutable.)

: Please identify where reference specification is within SDO member organizations or not and current level of approval as the level of question.

Show Details