OASIS SOA Repository Artifact Model and Protocol (S-RAMP) TC
What is S-RAMP?
The S-RAMP specification defines an SOA repository artifact data model together with bindings that describe the syntax for interacting with an SOA repository.
What companies are currently involved with the S-RAMP standardization effort?
S-RAMP is now being advanced through the OASIS S-RAMP Technical Committee. Members include the joint authors of S-RAMP version 1.0, HP, IBM, Software AG, and TIBCO, along with other Committee proposers, Active Endpoints, Web Layers, and WS02, as well as other organizations worldwide. See the S-RAMP Committee Roster for a current list.
Who should join the OASIS S-RAMP Technical Committee?
Anyone interested in addressing customer requirements for interoperable interfaces for SOA repositories is welcome to participate in this work. All companies, government agencies, research institutes, consulting firms, and individuals are invited to join this open standards initiative.
What are the IP terms associated with the S-RAMP specification?
The OASIS S-RAMP Technical Committee operates under the "Royalty Free on Limited Terms" mode of the OASIS IPR Policy.
Why does the specification reference The Open Group's SOA Ontology?
S-RAMP is not intended to define a general purpose ontology for SOA. Instead, the specification references the work of The Open Group, defining how it is integrated and used in the context of S-RAMP.
How is S-RAMP different from UDDI?
S-RAMP is focused on publication and query of documents based on their content and metadata. UDDI (also an OASIS Standard) describes how to store and access service metadata in a registry. UDDI does not provide any protocol support for storage and access of physical documents.
S-RAMP focuses on document publication and query based on document content, whereas "CMDB Federation describes the architecture and interactions for federating data repositories together to behave as a data store that satisfies the role of a Configuration Management Database (CMDB)."1
How does S-RAMP differ from the Reusable Asset Specification (RAS) from the OMG?
RAS focuses on the reuse of assets, specifying a way to organize structure, and describe and package files comprising an asset. S-RAMP does not focus on specifying the packaging of a common definition for arbitrary reusable components and how they are used in conjunction with each other to form a specific solution within a given context, nor on support for binary/executable code.
Will there only be an Atom Binding defined for S-RAMP or will other bindings be added?
S-RAMP has been structured to enable multiple bindings to be defined, although the initial focus has been on Atom since it can address many customer needs. The OASIS S-RAMP TC Charter cites other potential bindings.
How do I provide feedback?
OASIS maintains a public mailing list for providing input to the OASIS S-RAMP Technical Committee members. Everyone is invited to send comments or view archives.