Scrollbar
icons false

...

Page info
title title

Panel
title Contents of this Page
Table of Contents minLevel 2

...

The CT2 Development Framework (CTS2DF) is a Plugin-based Java toolkint. It is built on the OSGi

Multiexcerpt include
nopanel true MultiExcerptName ExitDisclaimer PageWithExcerpt wikicontent:Exit Disclaimer to Include

framework, which allows it to adopt a modular architecture. At the center, the CTS2DF is a web application, capable of being deployed to a web application server such as Tomcat

Multiexcerpt include
nopanel true MultiExcerptName ExitDisclaimer PageWithExcerpt wikicontent:Exit Disclaimer to Include

, Jetty

Multiexcerpt include
nopanel true MultiExcerptName ExitDisclaimer PageWithExcerpt wikicontent:Exit Disclaimer to Include

, WebSphere

Multiexcerpt include
nopanel true MultiExcerptName ExitDisclaimer PageWithExcerpt wikicontent:Exit Disclaimer to Include

, etc. At the core, the CTS2DF starts an Apache Felix

Multiexcerpt include
nopanel true MultiExcerptName ExitDisclaimer PageWithExcerpt wikicontent:Exit Disclaimer to Include

OSGi environment. This allows the OSGi framework to be self-contained, eliminating the need for special application servers to be used.

...

HTTP Requests are accepted and validated by a series of RestControllers. The responsibility of these RestControllers is to accept requests, parse parameters, and check all possible pre-conditions. They also connect the various HTTP requests to the appropriate CTS2 Profile Interfaces

Multiexcerpt include
nopanel true MultiExcerptName ExitDisclaimer PageWithExcerpt wikicontent:Exit Disclaimer to Include

. Once the RestControllers have accepted the requests and identified the needed CTS2 Profile Interfaces to fulfill it, The process of discovering the available implementations of those needed CTS2 Profile Interfaces begins.

Service Discovery happens via the ServiceProvider

Multiexcerpt include
nopanel true MultiExcerptName ExitDisclaimer PageWithExcerpt wikicontent:Exit Disclaimer to Include

interface. Each Service Plugin must register this Service as an OSGi Service. In this way, a Service Plugin advertises each CTS2 Profile that it implements.

...

LexEVS, implemented as a CTS2 Service Plugin, will implement the following CTS2 Profile Interfaces

Multiexcerpt include
nopanel true MultiExcerptName ExitDisclaimer PageWithExcerpt wikicontent:Exit Disclaimer to Include

. These Interfaces will delegate to LexEVS functionality as described below.

...

The CodeSystemVersionReadService

Multiexcerpt include
nopanel true MultiExcerptName ExitDisclaimer PageWithExcerpt wikicontent:Exit Disclaimer to Include

CTS2 Profile Interface will be implemented using the LexBIGService

Multiexcerpt include
nopanel true MultiExcerptName ExitDisclaimer PageWithExcerpt wikicontent:Exit Disclaimer to Include

.

Specifically, the resolveCodingScheme

Multiexcerpt include
nopanel true MultiExcerptName ExitDisclaimer PageWithExcerpt wikicontent:Exit Disclaimer to Include

method of the LexBIGService will be used

Multiexcerpt include
nopanel true MultiExcerptName ExitDisclaimer PageWithExcerpt wikicontent:Exit Disclaimer to Include

.

4.3.2 CodeSystemVersionQueryService

The CodeSystemVersionQueryService

Multiexcerpt include
nopanel true MultiExcerptName ExitDisclaimer PageWithExcerpt wikicontent:Exit Disclaimer to Include

CTS2 Profile Interface will be implemented using the LexBIGService interface

Multiexcerpt include
nopanel true MultiExcerptName ExitDisclaimer PageWithExcerpt wikicontent:Exit Disclaimer to Include

.

Specifically, the getSupportedCodingSchemes

Multiexcerpt include
nopanel true MultiExcerptName ExitDisclaimer PageWithExcerpt wikicontent:Exit Disclaimer to Include

method of the LexBIGService

Multiexcerpt include
nopanel true MultiExcerptName ExitDisclaimer PageWithExcerpt wikicontent:Exit Disclaimer to Include

interface will be used.

4.3.3 EntityDescriptionReadService

The EntityDescriptionReadService

Multiexcerpt include
nopanel true MultiExcerptName ExitDisclaimer PageWithExcerpt wikicontent:Exit Disclaimer to Include

CTS2 Profile Interface will be implemented using the LexBIGService

Multiexcerpt include
nopanel true MultiExcerptName ExitDisclaimer PageWithExcerpt wikicontent:Exit Disclaimer to Include

-> CodedNodeSet interface

Multiexcerpt include
nopanel true MultiExcerptName ExitDisclaimer PageWithExcerpt wikicontent:Exit Disclaimer to Include

.

4.3.4 EntityDescriptionQueryService

The EntityDescriptionQueryService

Multiexcerpt include
nopanel true MultiExcerptName ExitDisclaimer PageWithExcerpt wikicontent:Exit Disclaimer to Include

CTS2 Profile Interface will be implemented using the LexBIGService

Multiexcerpt include
nopanel true MultiExcerptName ExitDisclaimer PageWithExcerpt wikicontent:Exit Disclaimer to Include

-> CodedNodeSet interface

Multiexcerpt include
nopanel true MultiExcerptName ExitDisclaimer PageWithExcerpt wikicontent:Exit Disclaimer to Include

.

4.3.5 AssociationQueryService

The AssociationQueryService

Multiexcerpt include
nopanel true MultiExcerptName ExitDisclaimer PageWithExcerpt wikicontent:Exit Disclaimer to Include

CTS2 Profile Interface will be implemented using the LexBIGService

Multiexcerpt-include
nopanel true MultiExcerptName ExitDisclaimer PageWithExcerpt wikicontent:Exit Disclaimer to Include

-> CodedNodeGraph interface

Multiexcerpt include
nopanel true MultiExcerptName ExitDisclaimer PageWithExcerpt wikicontent:Exit Disclaimer to Include

.

4.3.6 MapReadService

The MapReadService

Multiexcerpt include
nopanel true MultiExcerptName ExitDisclaimer PageWithExcerpt wikicontent:Exit Disclaimer to Include

CTS2 Profile Interface will be implemented using a combination of the the MappingExtension interface and the LexBIGService. Specifically, the resolveCodingScheme

Multiexcerpt include
nopanel true MultiExcerptName ExitDisclaimer PageWithExcerpt wikicontent:Exit Disclaimer to Include

method of the LexBIGService

Multiexcerpt include
nopanel true MultiExcerptName ExitDisclaimer PageWithExcerpt wikicontent:Exit Disclaimer to Include

will be used, and the MappingExtension can be used to verify the CodingScheme is a Mapping or non-Mapping CodingScheme.

...

4.3.7 MapQueryService

The MapQueryService

Multiexcerpt include
nopanel true MultiExcerptName ExitDisclaimer PageWithExcerpt wikicontent:Exit Disclaimer to Include

CTS2 Profile Interface will be implemented using a combination of the the MappingExtension interface and the LexBIGService

Multiexcerpt include
nopanel true MultiExcerptName ExitDisclaimer PageWithExcerpt wikicontent:Exit Disclaimer to Include

. Specifically, the getSupportedCodingSchemes

Multiexcerpt include
nopanel true MultiExcerptName ExitDisclaimer PageWithExcerpt wikicontent:Exit Disclaimer to Include

method of the LexBIGService will be used, and the MappingExtension can be used to verify the CodingScheme is a Mapping or non-Mapping CodingScheme.

...

4.3.8 ValueSetReadService

The ValueSetReadService

Multiexcerpt include
nopanel true MultiExcerptName ExitDisclaimer PageWithExcerpt wikicontent:Exit Disclaimer to Include

CTS2 Profile Interface will be implemented using the LexEVS LexEVSValueSetDefinitionServices Interface.

4.3.9 ValueSetQueryService

The ValueSetQueryService

Multiexcerpt include
nopanel true MultiExcerptName ExitDisclaimer PageWithExcerpt wikicontent:Exit Disclaimer to Include

CTS2 Profile Interface will be implemented using the LexEVS LexEVSValueSetDefinitionServices Interface.Image Removed

4.3.10 ValueSetDefinitionReadService

The ValueSetDefinitionReadService

Multiexcerpt include
nopanel true MultiExcerptName ExitDisclaimer PageWithExcerpt wikicontent:Exit Disclaimer to Include

CTS2 Profile Interface will be implemented using the LexEVS LexEVSValueSetDefinitionServices Interface.

4.

...

3.

...

11 ValueSetDefinitionQueryService

The ValueSetDefinitionQueryService

Multiexcerpt include
nopanel true MultiExcerptName ExitDisclaimer PageWithExcerpt wikicontent:Exit Disclaimer to Include

CTS2 Profile Interface will be implemented using the LexEVS LexEVSValueSetDefinitionServices Interface.

5 URI Resolution

One of the requirements of Resource Oriented Architecture is that every resource must have an identifier. As the Universal Resource Identifier (URI) is the primary identifier used by the Semantic Web, the CTS2 specification calls for all of its resources to be identified by URIs. This results in the need to distinguish the identity of the resource being described from the identity of the description itself, and the basic requirement that all servers in a CTS2 ‘ecosystem’ need to use the same identifiers if information is to be aggregated and shared in a meaningful fashion. The EVS solution for this problem is a URI resolution service, which provides a canonical URI for any local URI and does so as a service.  For the EVS implementation of this service, a URI Resolver Service has been implemented and runs in conjunction with the EVS CTS2 implementation.  While CTS2 users may install their own resolving service, based on the installation instructions here, a service is also running at this location.  A thorough description of this service is to be found here.

6 Glossary

Service Plugin: An OSGi bundle capable of being loaded into the CTS2 Development Framework. In order to be recognized as a Service Plugin, the bundle must export one (and only one) Service of type ServiceProvider

Multiexcerpt include
nopanel true MultiExcerptName ExitDisclaimer PageWithExcerpt wikicontent:Exit Disclaimer to Include

. Note, however, that the bundle is no excluded from exporting other services – but it must at least export one and only one ServiceProvider Service.

...

Platform Specific Model (PSM): An implementation model targeted towards a specific technical platform.

...

Scrollbar
icons false