Standard

1. The name of the specification

WS-naming Specification

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

This document follows the recommendations of “OGSA Profile Definition Version 1.0” and describes an extension to the WS-Addressing specification to include extensibility elements for abstract names and for resolvers, as well as port types for the WS-Naming resolution services.

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

1.0

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

N/A

5. URI for the normative text of the specification

http://forge.gridforum.org/sf/sfmain/do/downloadAttachment/projects.ggf-editor/tracker.submit_ggf_draft/artf5659?id=atch4423

SOURCE

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

Open Grid Forum (OGF)

7. URI for the SDO

http://www.ogf.org

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

GFSG final review for Proposed Recommendation Grid Forum Document (GFD-R.P) (due date: May 22nd)

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

English

SUBJECT

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

N/A

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 )

• Presentation layer

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

N/A

OPTIONAL

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

• GFSG final review

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

http://www.ogf.org/ggf_abt_policies.htm

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.

http://www.ogf.org/ggf_abt_policies_ipr.htm

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.

• M. Duerst, M. Suignard, “Internationalized Resource Identifiers (IRIs)”, http://www.ietf.org/rfc/rfc3987.txt IETF RFC 3987, January 2005.
• K. Ballinger, D. Ehnebuske, C. Ferris, M. Gudgin, C.K. Liu, M. Nottingham, and P. Yendluri (ed.) Basic Profile Version 1.1, Web Services Interoperability Organization Final Material, 24 August 2004. http://www.ws-i.org/Profiles/BasicProfile-1.1.html
• M. Gudgin, M. Hadley, T. Rogers (eds.) Web Services Addressing 1.0 – Core (WS-Addressing), W3C Recommendation, 9 May 2006, http://www.w3.org/TR/2006/REC-ws-addr-core-20060509/

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.