This is a static archive of the previous Open Grid Forum GridForge content management system saved from host forge.ogf.org file /sf/wiki/do/viewPage/projects.scrm-wg/wiki/ApplicationContentsServiceSpecification1.0 at Thu, 03 Nov 2022 00:17:07 GMT SourceForge : View Wiki Page: ApplicationContentsServiceSpecification1.0

Project Home

Tracker

Documents

Tasks

Source Code

Discussions

File Releases

Wiki

Project Admin
Search Wiki Pages Project: scrm-wg     Wiki > ApplicationContentsServiceSpecification1.0 > View Wiki Page
wiki1504: ApplicationContentsServiceSpecification1.0

Standard

1. The name of the specification

Application Contents Service Specification

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

In order to install and operate complex systems such as n-tier systems more efficiently and automatically, it is necessary to specify and manage, as a unit, a diverse set of application related information. The Application Contents Service (ACS) provides central management of such application information. The Application Contents Service specification will focus on two main topics: a) Application Repository Interface (ARI), specifying repository service and its interface to Application Contents; and b) Application Archive Format (AAF), specifying archive format to register a set of Application Contents to the ACS as a unit. The Application Contents include application binaries and related information; e.g. program binaries, configuration data, procedure descriptions for lifecycle management, requirements descriptions for the hardware and underlying middleware, policy rules, and anything needed to create a task on grid systems.

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://www.ogf.org/Public_Comment_Docs/Documents/Feb-2006/draft-ggf-acs-spec-1.0.pdf


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.

Grid Working Draft Recommendation Proposal (GWD-R.P)

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?

(http://en.wikipedia.org/wiki/FCAPS, http://www.futsoft.com/pdf/fcapswp.pdf)

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
  • Application layer

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

(http://www.dmtf.org/standards/cim/)
  • Management Infrastructure

OPTIONAL

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

  • Initial public 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).

N/A

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

N/A

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

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

OASIS SDD TC spec.

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

 




The Open Grid Forum Contact Webmaster | Report a problem | GridForge Help
This is a static archive of the previous Open Grid Forum GridForge content management system saved from host forge.ogf.org file /sf/wiki/do/viewPage/projects.scrm-wg/wiki/ApplicationContentsServiceSpecification1.0 at Thu, 03 Nov 2022 00:17:07 GMT