We are pleased to announce that today OAGi announced it has
launched a Cloud Computing Initiative to ensure that the Open Applications
Group Integration Specification (OAGIS) enables complete support for Cloud Computing.
The Cloud Computing Initiative is led by the Architecture Council within OAGi and is looking at additions or revisions that OAGi members think is important to continue to evolve the specification. As part of the Cloud Computing initiative, OAGi has taken a decision to support Java Script Object Notation (JSON) as a data exchange format for the data exchange data model defined by OAGIS. OAGi has released a Position Paper on this support for JSON and it is available for free today on the OAGi web site at http://www.oagi.org.
Over a 15 year period of time, OAGi has supported several technical expressions of their data exchange data model. In 1996, when the first release of the Open Application Group Integration Specification (OAGIS) was published, the expression form of the data exchange data model was a proprietary meta data format invented by OAGi.
Since then, many improved forms of data expression have been developed and the OAGIS technology evolved to support XML Document Type Definitions (DTD) in 1987 and then XML Schema (XSD) in 2002. In 2005, OAGi elected to evolve OAGIS to support a stricter Schema expression as defined by the UN/CEFACT Naming and Design Rules (NDR) and Core Component Technical Specification (CCTS). This change again improved the grammar expressions in OAGIS, reduced ambiguity, and improved both intra and inter supply chain interoperability.
“Oracle (ORCL) applauds the recognition of JSON by the Open Applications Group, Inc. (OAGi) as a data exchange format that complements EDI and XML for data integration. The canonical OAGIS data model expressed in XML and carried through in JSON adds the ability to enable end to end integration – integration from the back office applications to integration on the glass,” said Michael Rowell, Oracle Standards Architect. “Using JSON, data from heterogeneous applications, clouds, and partners are presented cohesively so that end users can better perform their job functions.”
“Devices coupled with pervasive networks are driving the need for exposing cloud-based data services to enable ‘any where’, ‘any time’ computing in the ecosystem,” added Abhijeet Ranadive, Enterprise B2B Architect, Cisco Systems (CSCO). “APIs that enable this integration paradigm will need to have a standardized light payload format and JSON fits the requirement. Defining OAGi standard in a JSON format is a way to bring together two best in class solutions to meet the information needs.”
The Cloud Computing Initiative is led by the Architecture Council within OAGi and is looking at additions or revisions that OAGi members think is important to continue to evolve the specification. As part of the Cloud Computing initiative, OAGi has taken a decision to support Java Script Object Notation (JSON) as a data exchange format for the data exchange data model defined by OAGIS. OAGi has released a Position Paper on this support for JSON and it is available for free today on the OAGi web site at http://www.oagi.org.
Over a 15 year period of time, OAGi has supported several technical expressions of their data exchange data model. In 1996, when the first release of the Open Application Group Integration Specification (OAGIS) was published, the expression form of the data exchange data model was a proprietary meta data format invented by OAGi.
Since then, many improved forms of data expression have been developed and the OAGIS technology evolved to support XML Document Type Definitions (DTD) in 1987 and then XML Schema (XSD) in 2002. In 2005, OAGi elected to evolve OAGIS to support a stricter Schema expression as defined by the UN/CEFACT Naming and Design Rules (NDR) and Core Component Technical Specification (CCTS). This change again improved the grammar expressions in OAGIS, reduced ambiguity, and improved both intra and inter supply chain interoperability.
“Oracle (ORCL) applauds the recognition of JSON by the Open Applications Group, Inc. (OAGi) as a data exchange format that complements EDI and XML for data integration. The canonical OAGIS data model expressed in XML and carried through in JSON adds the ability to enable end to end integration – integration from the back office applications to integration on the glass,” said Michael Rowell, Oracle Standards Architect. “Using JSON, data from heterogeneous applications, clouds, and partners are presented cohesively so that end users can better perform their job functions.”
“Devices coupled with pervasive networks are driving the need for exposing cloud-based data services to enable ‘any where’, ‘any time’ computing in the ecosystem,” added Abhijeet Ranadive, Enterprise B2B Architect, Cisco Systems (CSCO). “APIs that enable this integration paradigm will need to have a standardized light payload format and JSON fits the requirement. Defining OAGi standard in a JSON format is a way to bring together two best in class solutions to meet the information needs.”
No comments:
Post a Comment