SourceForge : View Wiki Page: WebServicesResourceLifetimeV1.2

Search Wiki Pages Project: scrm-wg Wiki > WebServicesResourceLifetimeV1.2 > View Wiki Page

wiki1523: WebServicesResourceLifetimeV1.2

Standard

1. The name of the specification

Web Services Resource Lifetime 1.2

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

The relationship between Web services and stateful resources is defined in WS-Resource. This specification defines message exchanges to standardize the means by which a WS-Resource may be destroyed, and resource properties WS-ResourceProperties that may be used to inspect and monitor the lifetime of a WS-Resource. This specification defines two means of destroying a WS-Resource: immediate destruction and time-based, scheduled destruction.

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

WSRL V1.2, OASIS standard in April 2006

OASIS Committe Draft Primers: WSRF Primer

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

The purpose of the OASIS WSRF TC is to define a generic and open framework for modeling and accessing stateful resources using Web services. This includes mechanisms to describe views on the state, to support management of the state through properties associated with the Web service, and to describe how these mechanisms are extensible to groups of Web services. The set of specifications is know as the 'WS-Resource Framework'.

5. URI for the normative text of the specification

WS Resource Lifetime 1.2: wsrf-ws_resource_lifetime-1.2-spec-cs-01.pdf

WSRF Primer: http://docs.oasis-open.org/wsrf/wsrf-primer-1.2-primer-cd-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 Standard

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).

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

These specifications are referred to in a normative way.

WS-Addressing http://www.w3.org/TR/ws-addr-core/

WS-BaseNotification http://docs.oasis-open.org/wsn/wsn-

WS-BaseFaults http://docs.oasis-open.org/wsrf/wsrf-

WS-Resource http://docs.oasis-open.org/wsrf/wsrf-

WS-ResourceProperties http://docs.oasis-open.org/wsrf/wsrf-

WS-Topics http://docs.oasis-open.org/wsn/wsn-

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

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

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).

OGSI GGF GFD.15 ‚ÄúOpen Grid Services Infrastructure (OGSI) Version 1.0‚Äù. Available at http://forge.gridforum.org/projects/ogsi-wg SOAP 1.1 http://www.w3.org/TR/2000/NOTE-SOAP-20000508/

WS-Security http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0.pdf

WS-I Basic Profile 1.1 http://www.ws-i.org/Profiles/BasicProfile-1.1.html.

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