object role modeling
Recently Published Documents


TOTAL DOCUMENTS

48
(FIVE YEARS 4)

H-INDEX

6
(FIVE YEARS 1)

Author(s):  
Rusul Yousif Alsalhee ◽  
Abdulhussein Mohsin Abdullah

<p>The Holy Quran, due to it is full of many inspiring stories and multiple lessons that need to understand it requires additional attention when it comes to searching issues and information retrieval. Many works were carried out in the Holy Quran field, but some of these dealt with a part of the Quran or covered it in general, and some of them did not support semantic research techniques and the possibility of understanding the Quranic knowledge by the people and computers. As for others, techniques of data analysis, processing, and ontology were adopted, which led to directed these to linguistic aspects more than semantic. Another weakness in the previous works, they have adopted the method manually entering ontology, which is costly and time-consuming. In this paper, we constructed the ontology of Quranic stories. This ontology depended in its construction on the MappingMaster domain-specific language (MappingMaster DSL)technology, through which concepts and individuals can be created and linked automatically to the ontology from Excel sheets. The conceptual structure was built using the object role modeling (ORM) modeling language. SPARQL query language used to test and evaluate the propsed ontology by asking many competency questions and as a result, the ontology answered all these questions well.</p>


Author(s):  
Terry Halpin

In natural language, individual things are typically referenced by proper names or definite descriptions. Data modeling languages differ considerably in their support for such linguistic reference schemes. Understanding these differences is important both for modeling reference schemes within such languages and for transforming models from one language to another. This chapter provides a comparative review of reference scheme modeling within the Unified Modeling Language (version 2.5.1), the Barker dialect of entity relationship modeling, Object-Role Modeling (version 2), relational database modeling, the Web Ontology Language (version 2.0), and LogiQL (an extended form of datalog). The authors identify which kinds of reference schemes can be captured within these languages as well as those reference schemes that cannot be captured. The analysis covers simple reference schemes, compound reference schemes, disjunctive reference, and context-dependent reference schemes.


Author(s):  
Shin Huei Lim ◽  
Terry Halpin

Fact-oriented modeling approaches such as Object-Role Modeling (ORM) include a rich graphical notation for capturing business constraints, allowing modelers to visualize fine details of their data models. These data models should be validated with domain experts who best understand the business requirements, even if unfamiliar with the graphical notation. Hence, the data models are best validated by verbalizing the models in a controlled natural language, and by populating the relevant fact types with examples. Comparatively little support exists for verbalizing fact-based models in non-English languages, especially Asian languages. This paper describes the authors' work on verbalizing ORM models in Bahasa Melayu (Malay) and Mandarin. The authors specify some typical transformation patterns, discuss features of these languages requiring special treatment (e.g. noun classifiers, repositioning of modal operators, and different uses for terms equivalent to “who” and “that” in English), and describe their current implementation efforts.


Author(s):  
Herman Balsters ◽  
Terry Halpin

This paper provides formal semantics for an extension of the Object-Role Modeling approach to support declaration of dynamic rules. Dynamic rules differ from static rules by involving state transitions, rather than simply individual states. This paper restricts application of dynamic rules to single-step transactions, with a previous state (input to the transaction) and a new state (the result of that transaction). These dynamic rules specify an elementary transaction type by indicating which kinds of objects or facts (being added, deleted or updated) are involved. Dynamic rules may declare pre-conditions relevant to the transaction, and a post-condition stating the properties of the new state. In this paper the authors provide such dynamic rules with a formal semantics based on sorted, first-order predicate logic. The key idea underlying their solution is the formalization of dynamic constraints in terms of static constraints on the database transaction history.


Sign in / Sign up

Export Citation Format

Share Document