The Experts below are selected from a list of 6 Experts worldwide ranked by ideXlab platform
Frx Software Corporation - One of the best experts on this subject based on the ideXlab platform.
-
Specification Used: XBRL Specification dated 2000-07-31
2000Co-Authors: Bill Levis, Robert W. Blake, Frx Software CorporationAbstract:Taxonomy for the creation of XML-based instance documents for business and financial reporting of not-for-profit organizations according to SFAS 116 and 117. Namespace identifier: Recommended Namespace Prefix: np Issued: Version of XBR
Bill Levis - One of the best experts on this subject based on the ideXlab platform.
-
Specification Used: XBRL Specification dated 2000-07-31
2000Co-Authors: Bill Levis, Robert W. Blake, Frx Software CorporationAbstract:Taxonomy for the creation of XML-based instance documents for business and financial reporting of not-for-profit organizations according to SFAS 116 and 117. Namespace identifier: Recommended Namespace Prefix: np Issued: Version of XBR
Robert W. Blake - One of the best experts on this subject based on the ideXlab platform.
-
Specification Used: XBRL Specification dated 2000-07-31
2000Co-Authors: Bill Levis, Robert W. Blake, Frx Software CorporationAbstract:Taxonomy for the creation of XML-based instance documents for business and financial reporting of not-for-profit organizations according to SFAS 116 and 117. Namespace identifier: Recommended Namespace Prefix: np Issued: Version of XBR
Efsoc Framework - One of the best experts on this subject based on the ideXlab platform.
-
EFSOC Framework Overview and Infrastructure Services
2003Co-Authors: Kees Leune, Efsoc FrameworkAbstract:this document, we will present an overview of the framework and its metamodel, followed by specification of the infrastructure services. We will also relate out work to existing standardization and industry initiatives. 1.1 Notational Conventions The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC 2119]. This document uses Namespace Prefixes througout; they are listed in table 1.1. Note that the choice of any Namespace Prefix is arbitrary and not semantically A working prototype is available at http://maximus.uvt.nl/kees/phd-kees/ 4 Prefix Namespace Notes wsdl http://www.w3.org/2003/06/wsdl WSDL 1.2 specification http http://www.w3.org/2003/06/wsdl/http HTTP bindings for WSDL 1.2 xs http://www.w3.org/2001/XMLSchema XML Schema specification bpws http://schemas.xmlsoap.org/ws/2003/03/business-process/ BPEL4WS specification Table 1.1: Prefixes and namepsaces used in this document. significant. 5 EFSOC Framework and Metamodel Figure 2.1: The EFSOC framework EFSOC is a multi-tiered framework for service-oriented computing as shown in figure 2.1. The figure uses UML notation to represent that the framework consists of a number of tiers, each of which may contain any number of infrastructure services and any number of elements elements. All infrastructure services are regular services, which allows us to describe and publish them clearly in a standard format, such as WSDL. The core assumption of our approach is that all all services, business processes and actors play a certain role in achieving business goals and that coordination between subjects takes place by exchanging events. This is represented in the metamodel by the relati..
Kees Leune - One of the best experts on this subject based on the ideXlab platform.
-
EFSOC Framework Overview and Infrastructure Services
2003Co-Authors: Kees Leune, Efsoc FrameworkAbstract:this document, we will present an overview of the framework and its metamodel, followed by specification of the infrastructure services. We will also relate out work to existing standardization and industry initiatives. 1.1 Notational Conventions The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC 2119]. This document uses Namespace Prefixes througout; they are listed in table 1.1. Note that the choice of any Namespace Prefix is arbitrary and not semantically A working prototype is available at http://maximus.uvt.nl/kees/phd-kees/ 4 Prefix Namespace Notes wsdl http://www.w3.org/2003/06/wsdl WSDL 1.2 specification http http://www.w3.org/2003/06/wsdl/http HTTP bindings for WSDL 1.2 xs http://www.w3.org/2001/XMLSchema XML Schema specification bpws http://schemas.xmlsoap.org/ws/2003/03/business-process/ BPEL4WS specification Table 1.1: Prefixes and namepsaces used in this document. significant. 5 EFSOC Framework and Metamodel Figure 2.1: The EFSOC framework EFSOC is a multi-tiered framework for service-oriented computing as shown in figure 2.1. The figure uses UML notation to represent that the framework consists of a number of tiers, each of which may contain any number of infrastructure services and any number of elements elements. All infrastructure services are regular services, which allows us to describe and publish them clearly in a standard format, such as WSDL. The core assumption of our approach is that all all services, business processes and actors play a certain role in achieving business goals and that coordination between subjects takes place by exchanging events. This is represented in the metamodel by the relati..
