Time filter

Source Type

Reading, United Kingdom

The Open Group is a vendor and technology-neutral industry consortium, currently with over four hundred member organizations. It was formed in 1996 when X/Open merged with the Open Software Foundation. Services provided include strategy, management, innovation and research, standards, certification, and test development.The Open Group is most famous as the certifying body for the UNIX trademark, and its publication of the Single UNIX Specification technical standard, which extends the POSIX standards and is the official definition of a UNIX system. The Open Group also develops and manages the TOGAF standard, which is an industry standard enterprise architecture framework.The Open Group members include a range of IT buyers and vendors as well as government agencies, for example Capgemini, Fujitsu, Oracle, Hitachi, HP, Orbus Software, IBM, Kingdee, NEC, SAP, US Department of Defense, NASA and others. Wikipedia.

The Open Group | Date: 2010-12-14

A light source detection method and system are provided. The method includes receiving incident light sources through light passing holes formed in a light spot forming board to form a light spot on an imaging board; capturing the image of the light spot and detecting the intensity thereof into divided zones so as to transmit such information that is calculated by preset algorithms to a processing device for identification, thereby improving on the drawbacks of prior techniques to achieve better accuracy of light sources and efficiency in use.

The Open Group | Date: 2010-12-14

A wind power device is provide that includes a first carrier with a first active layer disposed thereon, a second carrier with a second active layer disposed thereon, at least a wind-receiving member connected to the first and second active layers and at least a power unit. The wind-receiving member takes in wind energy for activating the first and second active layers to drive the power unit to generate power. The wind power device advantageously provides ease in assembly and maintenance and is suitable to environments with variable wind directions and capable of being flexibly adjusted to adapt to varying wind speeds and thus achieve optimal power generating efficiency.

The Open Group | Date: 2010-03-17

A system and method of managing light energy are provided. A detecting apparatus detects input information related to input light energy and environmental information related to efficiency of inputting light energy. Then, an analysis and management apparatus calculates, analyzes, classifies, manages or optimizes the input information and environmental information by predetermined parameters or rules, and determines whether to take a corresponding action according to results of analysis or management. Accordingly, drawbacks of prior arts, that the source of light energy cannot be handled accurately and difficulties in controlling and optimizing light energy persist, can be solved.

A method and system for energy management of a composite battery are provided to control and manage products of reaction going on in the composite battery. During the reaction, the gas products are usually exhausted and wasted. If the gases could be recycled, battery effectiveness would be improved. According to the present invention, the gases are collected and then recycled by an exhaust gas recycling device. In addition, the method and system involve analyzing data of the generated electrical energy, data of the produced gases, operational data of the composite battery and device data for the exhaust gas recycling device. Thus, the composite battery is controlled and managed according to the analysis, and its effects are improved.

News Article | July 12, 2013
Site: www.zdnet.com

Along with security, one of the most difficult issues with cloud platforms is the risk of vendor lock-in. By assigning business processes and data to cloud service providers, it may get really messy and expensive to attempt to dislodge from the arrangement if it's time to make a change. There are ways enterprises, as well as the industry in general, can address these lock-in issues. Solutions to potential vendor lock-in were recently surfaced in a new guide from The Open Group. The guide, compiled by a team led by Kapil Bakshi and Mark Skilton, provides key pointers for enterprises seeking to develop independently functioning clouds, as well as recommendations to the industry on standards that need to be adopted or extended. Here are 10 key problems and recommendations identified by The Open Group team for achieving cloud formations based on standards, rather than on vendor technology: Platform-platform interfaces:  A universally used standard for platform-platform interfaces — the Internet, HTTP and message envelope layers of web service APIs — "would provide a major part of the basis for real cloud interoperability," the guide states.  The two styles of web service interface handled by platforms — WS-I and raw HTTP — each has strengths for specific applications. "Many small-scale integrations that originally used WS-I with SOAP and XML, because JSON was not mature enough at the time, are now moving towards raw HTTP and JavaScript Object Notation because it is better suited to their needs. However, for enterprise-level integrations, SOAP is still king." Application-platform interfaces: "Currently, there are a number of programming languages that might be used for the interface; there is no agreement on what functionality is needed; there are no commonly-accepted application-platform interface standards that cover the full range of functionality; however, it might be agreed. There are, however, products, both commercial and open source, that implement parts of the functionality, such as Enterprise Service Buses (ESBs), and some vendor-independent interface standards for part of the functionality, such as the Java Message Service (JMS)." Service descriptions: The accepted standard for service descriptions, the Web Service Description Language (WSDL), has limitations, the guide says: "Its descriptions are machine-readable rather than human-friendly; it describes the functional characteristics of services, but does not cover non-functional characteristics such as quality of service and conditions of contract; it has no real ability to describe service data models; and it applies to services that use the WS-I approach, but not to services that use the direct HTTP approach." Bodies working to develop standards for service descriptions that address some of these limitations include the Web Application Description Language (WADL) authors, the Open Data Center Alliance (ODCA), the SLA@SOI Consortium, and the OASIS TOSCA Technical Committee. Service management interfaces: "Standardization of these interfaces will enable the development of cloud management systems as commercial off-the-shelf products," according to the guide." Initiatives alreday underway include the "DMTF Cloud Infrastructure Management Interface (CIMI) and Virtualization Management (VMAN) standards, the OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA), the Open Grid Forum Open Cloud Computing Interface (OCCI), and the SNIA Cloud Data Management Interface (CDMI). The Openstack APIs may also provide de facto standards." Data models: "These do not cover the new 'NoSQL' paradigms that are increasingly being used in cloud computing," the guide states. "Also, the schema standards do not enable correspondences between different data models to be established, and this is crucial for interoperability. The semantic web standards and the Universal Data Element Framework (UDEF) can be used to define correspondence between data models, but their application is not widely understood, and they are little used." Loose coupling: "Tightly-coupled components are difficult and expensive to integrate, particularly over the lifetime of a system that undergoes change (as most do)." Service orientation: "Cloud offerings are packaged as services (IaaS, PaaS, SaaS). Cloud platform-platform interfaces, whether in the WS-I or raw HTTP style, assume client-server interaction. Service orientation encompasses and reinforces other principles – loose coupling, service descriptions, and described interfaces." Marketplaces: "Use of marketplaces and app stores is growing, but there are as yet no standards or established good practice for their operation," according to the guide. "This means that product vendors must cater for the different requirements and practices of all the marketplaces in which their products appear, that customers must understand the different features of all the marketplaces that they use, and that marketplace operators are spending effort on unnecessary differentiation." Representational State Transfer (REST): "There is a need for robust and scalable services that are loosely-coupled and have stable interfaces that are easy to describe." Machine image formats: "The ability to load a machine image containing an application together with its application platform onto different cloud infrastructure services is a new form of portability that is made possible by cloud computing. A standard machine image format makes portability possible across different infrastructure service providers, as well as across infrastructure services of a single provider.

Discover hidden collaborations