Contributors: Name Affiliation

Distributed and Parallel Databases, 2005

In this paper, we address how ebXML registry semantics support can be further enhanced to make it OWL aware. There are basically three ways of achieving this: The first one is mapping OWL constructs to ebXML registry information model constructs without modifying the registry architecture and implementation. In this way, the semantic explicitly stored in the registry can be retrieved through querying; yet, the application program must contain additional code to process this semantics. The second approach is additionally providing predefined stored procedures in the registry for processing the OWL constructs. We believe that this approach is quite powerful to associate semantics with registry objects: it becomes possible to retrieve knowledge through queries and the enhancements to the registry are generic. The capabilities provided move the semantics support beyond what is currently available in ebXML registries and it does so by using a standard ontology language. The third approach is changing the ebXML registry to support OWL with full reasoning capabilities. However, this approach requires considerable changes in the registry architecture.

2006

This document defines the ebXML Registry profile for enhancing ebXML Registry with OWL semantics to make it OWL aware.

2006

This document defines the ebXML Registry profile for enhancing ebXML Registry with OWL semantics to make it OWL aware.

2006

2004

Web services, like their real life counterparts have several properties and thus truly useful semantic information can only be defined through standard ontology languages. Semantic Web is an important initiative in this respect. However, although service registries are the major mechanisms to discover services, the semantic support provided by service registries is completely detached from the Semantic Web effort.

2002

There are several B2B frameworks at the market, ebXML being one of them. Market position of ebXML is getting stronger due to its interoperability and strong support by UN/CEFACT and OASIS. EbXML has modular architecture consisting of five layers: Core Components, Business Process, Trading Partner Agreement, Registry/Repository and T,R,P (Transport, Routing and Packaging). Modularity of ebXML specifications enables implementation of layers without the need to implement all of its functionality. This paper describes implementation model of Registry/Repository layer. Role of Registry/Repository in ebXML is vital as it stores all necessary information to perform B2B transactions and gives a standardized methodology for retrieval and storage of such information in distributed environment.

Proceedings of the 7th International Conference on Telecommunications, 2003. ConTEL 2003., 2003

Department of Telecommunications, Faculty of Electrical Engineering and Computing, University of Zagreb works on the research project named ''Networked Economy'', supported by Croatian Ministry of Science and Technology. The project is also recognized by corporate domain and was made a part of an e-business initiative by the Agrokor group. The Agrokor's intention is to use the ebXML Registry/Repository layer as the central point of integration among the many Agrokor's affiliates and partners. We have considered different approaches toward ebXML specifications describing Registry/Repository layer, not only to conform to specifications, but also with vision that careful architecture modeling will enable modularity and flexibility of our solution. This could be vital, as we must bear in mind that specifications are surely going to be improved over certain period of time. This paper describes modeling ebXML Registry/Repository architecture and concentrates on its Registry Service part.

Proceedings of the 5th International Information Technology Conference, 2003

The ebXML initiative is designed for electronic interoperability, allowing businesses to find each other, agree to become trading partners and conduct business. ebXML repository is used to store the ebXML resources and the ebXML registry is used to discover these resources. ebXML resources may be in the form of XML documents, Document Type Definitions, XML Schemas, UML models and various other forms. Therefore a proper tool is required for the management of these resources. Management of ebXML resources has to be done by the experts who create and modify and are in charge of these resources. If there is a tool for the management of these resources, the experts can concentrate more on the content of these resources rather than management of them. This paper describes the implementation of a graphical tool for the management of ebXML resources based on the proposed ebXML specifications. Two approaches are being used to discover these resources. Registry Navigator is one, which is in a tree structure and gives a full view of the registry. Query Manager is the other, which enables quick referencing to the resources if the user is fully aware of what resources are needed. The documents discovered in this manner are to be opened in the Editor pane of the tool. This editor facilitates the creation and modification of documents easily. The tool also incorporates capabilities to add and remove resources through the Life Cycle Manager. It also has a mechanism, which keeps track of different versions of the resources, so that the preferred version can be referred with minimum effort. Finally, it allows non-expert users to dynamically access the content of the registry over the web.

2002

This class is used as a simple wrapper class that associates a String with its locale. The class is needed in the InternationalString class where a Collection of LocalizedString instances are kept. Each LocalizedString instance has a charset and lang attribute as well as a value attribute of type String.

Web Semantics: Science …, 2008

Since achieving W3C recommendation status in 2004, the Web Ontology Language (OWL) has been successfully applied to many problems in computer science. Practical experience with OWL has been quite positive in general; however, it has also revealed room for improvement in several areas. We systematically analyze the identified shortcomings of OWL, such as expressivity issues, problems with its syntaxes, and deficiencies in the definition of OWL species. Furthermore, we present an overview of OWL 2-an extension to and revision of OWL that is currently being developed within the W3C OWL Working Group. Many aspects of OWL have been thoroughly reengineered in OWL 2, thus producing a robust platform for future development of the language.