|
Anzeige # |
|
1 |
Serviceorientierte Architektur
Beschreibung der Serviceorientierte Architektur (SOA), engl. service oriented architecture, auch dienstorientierte Architektur, bei Wikipedia.
|
|
2 |
OSOA - Open Service Oriented Architecture
The Open SOA Collaboration represents an informal group of industry leaders that share a common interest: defining a language-neutral programming model that meets the needs of enterprise developers who are developing software that exploits Service Oriented Architecture characteristics and benefits.
|
|
3 |
Service Component Architecture (SCA): Build systems using SOA
Service Component Architecture (SCA) is a set of specifications which describe a model for building applications and systems using a Service-Oriented Architecture. SCA extends and complements prior approaches to implementing services, and SCA builds on open standards such as Web services.
|
|
4 |
OASIS Commitees by Category: SOA
Service Oriented Architecture (SOA) represents a collection of best practices principles and patterns related to service-aware, enterprise-level, distributed computing. SOA standardization efforts at OASIS focus on workflows, translation coordination, orchestration, collaboration, loose coupling, business process modeling, and other concepts that support agile computing.
|
|
5 |
SOA-Know-How.de
Die herstellerübergreifenden Informationsplattform SOA-Know-How.de
|
|
6 |
SOA Patterns
A community site dedicated to SOA design patterns and the on-going development and expansion of the SOA design pattern catalog. Provided by the Prentice Hall Service-Oriented Computing Series from Thomas Erl.
|
|
7 |
OASIS SOA Reference Model TC
The OASIS Service Oriented Architecture TC will develop a Reference Model for Service Oriented Architecture. This is primarily to address SOA being used as a term in an increasing number of contexts and specific technology implementations. Sometimes, the term is used with differing - or worse, conflicting - understandings of implicit terminology and components. This Reference Model is being developed to encourage the continued growth of different and specialized SOA implementations whilst preserving a common layer of understanding about what SOA is.
|
|
8 |
ebXML - Enabling A Global Electronic Market
ebXML enables enterprises of any size, in any location to meet and conduct business through the exchange of XML-based messages.
|
|
9 |
OASIS ebXML Core (ebCore) TC
Managing modifications and maintenance for several ratified ebXML specifications.
|
|
10 |
OASIS ebXML Business Process TC
Providing a standards-based business process foundation that promotes the automation and predictable exchange of business collaboration definitions using XML.
|
|
11 |
OASIS ebXML Registry TC
The OASIS ebXML Registry TC develops specifications to achieve interoperable registries and repositories, with an interface that enables submission, query and retrieval on the contents of the registry and repository.
|
|
12 |
OASIS ebXML Messaging Services TC
The purpose of the OASIS ebXML Messaging Services TC is to develop and recommend technology for the transport, routing and packaging of business transactions using standard Internet technologies.
|
|
13 |
OASIS ebXML Collaboration Protocol Profile and Agreement (CPPA) TC
The ebXML Collaboration Protocol Profile and Agreement OASIS Standard provides definitions for the sets of information used in business collaborations.
|
|
14 |
OASIS ebXML Implementation Interoperability and Conformance (IIC) TC
The IIC TC will provide a means for software vendors to create infrastructure and applications which adhere to the ebXML specifications and are able to interoperate.
|
|
15 |
OASIS UDDI Specification TC
The purpose of the OASIS UDDI Specification TC is to continue work on the Web services registry foundations developed and published by UDDI.org. The UDDI specifications form the necessary technical foundation for publication and discovery of Web services implementations both within and between enterprises.
|
|
16 |
Web Services Description Language (WSDL) Version 1.1
WSDL is an XML format for describing network services as a set of endpoints operating on messages containing either document-oriented or procedure-oriented information. The operations and messages are described abstractly, and then bound to a concrete network protocol and message format to define an endpoint. Related concrete endpoints are combined into abstract endpoints (services). WSDL is extensible to allow description of endpoints and their messages regardless of what message formats or network protocols are used to communicate, however, the only bindings described in this document describe how to use WSDL in conjunction with SOAP 1.1, HTTP GET/POST, and MIME.
|
|
17 |
Web Services Description Language (WSDL) Version 2.0
This document describes the Web Services Description Language Version 2.0 (WSDL 2.0), an XML language for describing Web services. This specification defines the core language which can be used to describe Web services based on an abstract model of what the service offers. It also defines the conformance criteria for documents in this language.
|
|
18 |
OASIS Security Services (SAML) TC
The Security Assertion Markup Language (SAML), developed by the Security Services Technical Committee of OASIS, is an XML-based framework for communicating user authentication, entitlement, and attribute information. As its name suggests, SAML allows business entities to make assertions regarding the identity, attributes, and entitlements of a subject (an entity that is often a human user) to other entities, such as a partner company or another enterprise application.
|
|
19 |
OASIS eXtensible Access Control Markup Language (XACML) TC
The XACML Technical Committee will define a core XML schema for representing authorization and entitlement policies, also called XACML.
|
|
20 |
Web Service Modeling Ontology (WSMO)
This document presents an ontology called Web Service Modeling Ontology (WSMO) for describing various aspects related to Semantic Web Services. Taking the Web Service Modeling Framework (WSMF) as a starting point, we refine and extend this framework, and develop an ontology and a description language.
|
|
Seite 1 von 2 |
Weblinks 