Describing Scholarly Works with Dublin Core: A Functional Approach

This article describes the development of the Scholarly Works Application Profile (SWAP)—a Dublin Core application profile for describing scholarly texts. This work provides an active illustration of the Dublin Core Metadata Initiative (DCMI) “Singapore Framework” for Application Profiles, presented at the DCMI Conference in 2007, by incorporating the various elements of Application Profile building as defined by this framework—functional requirements, domain model, description set profile, usage guidelines, and data format. These elements build on the foundations laid down by the Dublin Core Abstract Model and utilize a preexisting domain model (FR-BR—Functional Requirements for Bibliographic Records) in order to support the representation of complex data describing multiple entities and their relationships. The challenges of engaging community acceptance and implementation will be covered, along with other related initiatives to support the growing corpus of scholarly resource types, such as data objects, geographic data, multimedia, and images whose structure and metadata requirements introduce the need for new application profiles. Finally, looking to other initiatives, the article will comment on how Dublin Core relates to the broader scholarly information world, where projects like Object Re-use and Exchange are attempting to better equip repositories to exchange resources

The GOOSE Protocol

The majority of the electrical substations built today conform to the international standard IEC 61850 that uniformly defines the communication between the various intelligent electronic devices (IEDs) of the substation automation system. The success of the standard in substation automation has expanded its application to new areas, such as wind power, hydro power, and smart grids. For this thesis, the most intriguing use of the standard is its application to the communication between the control system of internal combustion engines and other equipment in a power plant. The main objective of this thesis is to gain early experience on the use of the Generic Object Oriented Substation Events (GOOSE) protocol, which is often considered the most prominent communication protocol of IEC 61850. In this thesis, the standard IEC 61850 is described, and its most fundamental concepts are illustrated by clear examples. An application based on open source software has been developed in the Linux-environment in conjunction with this thesis. The application enables two IEDs from different manufacturers to exchange GOOSE messages. The emphasis of the thesis is thus on the presentation of the GOOSE protocol and the developed application. The results show that the GOOSE protocol provides compatible interfaces for information exchange between IEDs provided by different manufacturers, and can be seen as a viable option as a future communication protocol. IEC 61850 will likely be put into service in engine power plants, in the near future. The schedule partially depends on the development of the markets and the requirements of the customers.fi=Opinnäytetyö kokotekstinä PDF-muodossa.|en=Thesis fulltext in PDF format.|sv=Lärdomsprov tillgängligt som fulltext i PDF-format

Integration, management and communication of heterogeneous design resources with WWW technologies

Recently, advanced information technologies have opened new pos-sibilities for collaborative designs. In this paper, a Web-based collaborative de-sign environment is proposed, where heterogeneous design applications can be integrated with a common interface, managed dynamically for publishing and searching, and communicated with each other for integrated multi-objective de-sign. The CORBA (Common Object Request Broker Architecture) is employed as an implementation tool to enable integration and communication of design application programs; and the XML (eXtensible Markup Language) is used as a common data descriptive language for data exchange between heterogeneous applications and for resource description and recording. This paper also intro-duces the implementation of the system and the encapsulating issues of existing legacy applications. At last, an example of gear design based on the system is il-lustrated to identify the methods and procedure developed by this research

Ship product modelling

This paper is a fundamental review of ship product modeling techniques with a focus on determining the state of the art, to identify any shortcomings and propose future directions. The review addresses ship product data representations, product modeling techniques and integration issues, and life phase issues. The most significant development has been the construction of the ship Standard for the Exchange of Product Data (STEP) application protocols. However, difficulty has been observed with respect to the general uptake of the standards, in particular with the application to legacy systems, often resulting in embellishments to the standards and limiting the ability to further exchange the product data. The EXPRESS modeling language is increasingly being superseded by the extensible mark-up language (XML) as a method to map the STEP data, due to its wider support throughout the information technology industry and its more obvious structure and hierarchy. The associated XML files are, however, larger than those produced using the EXPRESS language and make further demands on the already considerable storage required for the ship product model. Seamless integration between legacy applications appears to be difficult to achieve using the current technologies, which often rely on manual interaction for the translation of files. The paper concludes with a discussion of future directions that aim to either solve or alleviate these issues

Including widespread geometry formats in semantic graphs using RDF literals

The exchange of building data involves both geometric and non-geometric data. A promising Linked Data approach is to embed data from existing geometry formats inside Resource Description Framework (RDF) literals. Based on a study of relevant specifications and related work, this toolset-independent approach was found suitable for the exchange of geometric construction data. To implement the approach in practice, the File Ontology for Geometry formats (FOG) and accompanying modelling method is developed. In a proof-of-concept web application that uses FOG, is demonstrated how geometry descriptions of different existing formats are automatically recognised and parsed

Graphical display and data structure for virtual prototyping

One of the goals of engineering firms is to bring better products to market faster. Although concurrent engineering can aid in this endeavor, it requires that all areas of an organization work simultaneously. Thus, current product data must be accessible to everyone. Virtual prototyping allows this simultaneous exchange of information. Virtual prototyping not only replaces the physical model in product development with a virtual model, but also it goes further by allowing data associated with each part of the model to be accessed. This data is not limited to just geometric properties but could contain other quantifiable properties, such as materials, features, and manufacturing notes. Later in the design process, the virtual model could be used for checking for interferences and stresses or for running simulations. The research presented in this dissertation outlines the development of software that provides a foundation for developing virtual prototyping software at Louisiana Tech University. Microsoft Visual C++ and the Microsoft Foundation Class library are utilized for developing this Windows98 application. OpenGL is used as the software interface to the graphics hardware. Although C++ is used in writing most of the source code, C has to be used when interfacing with OpenGL to display the solid models. A linked list is used as the data structure for storing the individual objects. Geometric information is stored for each object, but the structure is flexible and extensible so that other information, such as features and functions, can be added in the future. To relate one object to another, a hierarchical tree has been implemented. This tree structure allows the user to specify the “parent-child” relationships that exist in the model. Several different file formats are available to the user of the software to save and retrieve the objects contained in the model. Foremost of these formats is the DXF format that allows the exchange of data between different graphics packages. Importing DXF files into the application is the typical means of adding objects to the model. The sequential format provided in the serialization process of the Microsoft Foundation Class library allows for saving both object and hierarchy data

The Tool for Object Oriented Petri Nets

Tato práce se zabývá tvorbou nástroje pro práci s Objektově orientovanými Petriho sítěmi za použití dvou rozdílných jazyků PNML a PNtalk. PNML slouží pro popis Petriho sítě, je založený na XML a jeho výhodou je, že dokáže každý prvek Petriho sítě popsat pomocí svých elementů. PNtalk je konkrétní implementací OOPN a je založený na jazyce Smalltalk. Nástroj pro práci s OOPN bude komunikovat s externí aplikací systémem PNtalk z důvodu výměny modelů. Na závěr budou navržena rozšíření nástroje.This thesis deals with creation of the tool for Object Oriented Petri Nets which uses two different languages PNML and PNtalk. PNML is an XML-based interchange format for Petri nets. Its advantage is that it is possible to describe each element of Petri net by element of PNML language. PNtalk is based on the formalism of Object Oriented Petri Nets and also on Smalltalk language. The tool for OOPN will communicate with the external application PNtalk system in order to exchange models between these two applications. There will be discussed possible extensions for the tool at the end of the thesis.

Realising the open virtual commissioning of modular automation systems

To address the challenges in the automotive industry posed by the need to rapidly manufacture more product variants, and the resultant need for more adaptable production systems, radical changes are now required in the way in which such systems are developed and implemented. In this context, two enabling approaches for achieving more agile manufacturing, namely modular automation systems and virtual commissioning, are briefly reviewed in this contribution. Ongoing research conducted at Loughborough University which aims to provide a modular approach to automation systems design coupled with a virtual engineering toolset for the (re)configuration of such manufacturing automation systems is reported. The problems faced in the virtual commissioning of modular automation systems are outlined. AutomationML - an emerging neutral data format which has potential to address integration problems is discussed. The paper proposes and illustrates a collaborative framework in which AutomationML is adopted for the data exchange and data representation of related models to enable efficient open virtual prototype construction and virtual commissioning of modular automation systems. A case study is provided to show how to create the data model based on AutomationML for describing a modular automation system

DRIVER Technology Watch Report

This report is part of the Discovery Workpackage (WP4) and is the third report out of four deliverables. The objective of this report is to give an overview of the latest technical developments in the world of digital repositories, digital libraries and beyond, in order to serve as theoretical and practical input for the technical DRIVER developments, especially those focused on enhanced publications. This report consists of two main parts, one part focuses on interoperability standards for enhanced publications, the other part consists of three subchapters, which give a landscape picture of current and surfacing technologies and communities crucial to DRIVER. These three subchapters contain the GRID, CRIS and LTP communities and technologies. Every chapter contains a theoretical explanation, followed by case studies and the outcomes and opportunities for DRIVER in this field

BDEF : the behavioral design data exchange format

BDDB is a Behavioral Design Data Base that manages the design data produced and consumed by different behavioral synthesis tools. These different design tools retrieve design data from BDDB, manipulate the data, and then store the results back into the data base. BDDB thus needs to address the following two issues: (1) a design data exchange approach and (2) customized design data interfaces. To address the first issue, we have developed a textual description format for describing design data objects and relationships. This language, referred to as the Behavioral Design Data Exchange Format (BDEF), is used as common format for exchanging design data between BDDB and the design tools in the behavioral synthesis environment. To address the second issue, we have developed a behavioral object type description language (generally referred to as schema definition language) for describing the global data structures required by design tools as well as the desired design subviews of this global BDDB design information. One design view class, namely, BDEF, is the topic of this report.In this report we give a formal definition of the BDEF format. Then we describe a comprehensive example of applying BDEF to the behavioral synthesis domain. That is, we present the complete BDEF syntax for the Extended Control/Data Flow Graph Model (ECDFG), which is the design representation model used by most behavioral synthesis tools in the UCI CADLAB synthesis system. We also present several example descriptions of designs using this ECDFG model. A parser/graph compiler from BDEF into the generalized ECDFG design representation as well as a BDEF generator from the ECDFG data structures into the BDEF format have been implemented