![]() The CNO model provides four dimensions for describing the network: Structural – to identify participants in the interactions and their roles Componential – describing the resources supporting the network Functional – describing the major operations or processes of the network, and Behavioral – specifying the principles, policies and governance of the network. By reference architecture, we mean a prescriptive (abstract) model for developing concrete enterprise architectures - a strategic information asset-base, which defines the mission, the information necessary to perform the mission, the technology necessary to perform the mission, and the transitional processes for implementing new technologies in response to changing mission needs. They present complementary views of the required semantic support for collaborations: (i) Network View, based on Collaborative Network Organizations (CNO) discussed in, and (ii) Participant View based on the traditional enterprise architecture framework. To address the requirements, a pair of complementary reference architectures was developed to guide collaborating organizations and the central coordination entity in developing semantic interoperability capabilities. Based on the requirements in Section 3, this section presents the Semantic Interoperability Architecture Framework, its scope and notation (Section 4.1), and two architectures representing the network (Section 4.2) and participant (Section 4.3) views. R17) Interfacing with Collaboration Platforms : The Semantic Gateway, Clearinghouse and other infrastructural elements would be required to interface with collaboration platforms such as messaging gateways and workflows. Semantic differences arise in various aspects of a service delivery process, in particular with respect to evidences, evidence placeholders, preconditions or rules, effects and outputs of services, selection of service providers, customer characterization and security. The gateway must be able to semantically validate data with respect to a semantic asset and also mediate semantic conflicts arising in different information exchange scenarios such as: collaboration parties could have different labels or names for the same information parties use same terms but with different meanings and one party requests information or service with no direct equivalence to the receiving party. The gateway services rely on the semantic assets provided through the clearinghouse in resolving these differences. R16) Semantic Gateway : To enable semantic translation (mediation) of information between collaborating parties, there is a need to provide semantic gateway services. R15) Semantic Discovery – Collaborating organizations should be able to search the central metadata registry for required data, services and other resource types, through the clearinghouse. The Clearinghouse is expected to provide search and retrieval capabilities for semantic assets in the central repository as well as those in local repositories managed by individual organizations. R14) Clearinghouse - There is a need to develop a clearinghouse (central metadata registry) which manages the lifecycle of semantic assets on the central semantic asset repository. R13) Central Semantic Asset Repository – There is a need to establish a repository of semantic assets at the community and whole-of-government levels. These organizations should be able to push updates of their local registries to the clearinghouse (or the central metadata registry). R12) Local Metadata Registry – There is a need for collaborating (or participating) organizations to provide a Local Metadata Registry for publishing and managing the lifecycle of semantic assets. R11) Local Semantic Asset Repository – There is a need to provide storage services for semantic assets at different organizations or collaboration parties. Such assets include dictionaries, taxonomies, mapping tables and XML schemas and ontologies. Semantic descriptions will be based on agreed government-wide specifications and ontologies. requirements are cataloged in this section: R10) Semantic Description – Collaborating organizations should be able to provide semantic descriptions of core enterprise elements as semantic assets, including: shared data, collaborative processes (both required and provided), services and related regulations. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |