Extending a database system with procedures
ACM Transactions on Database Systems (TODS)
Typed query languages for databases containing queries
PODS '98 Proceedings of the seventeenth ACM SIGACT-SIGMOD-SIGART symposium on Principles of database systems
On specifying security policies for web documents with an XML-based language
SACMAT '01 Proceedings of the sixth ACM symposium on Access control models and technologies
On propagation of deletions and annotations through views
Proceedings of the twenty-first ACM SIGMOD-SIGACT-SIGART symposium on Principles of database systems
Data integration: a theoretical perspective
Proceedings of the twenty-first ACM SIGMOD-SIGACT-SIGART symposium on Principles of database systems
The description logic handbook
Conceptual modeling with description logics
The description logic handbook
Applications for Expression Data in Relational Database Systems
ICDE '04 Proceedings of the 20th International Conference on Data Engineering
MONDRIAN: Annotating and Querying Databases through Colors and Blocks
ICDE '06 Proceedings of the 22nd International Conference on Data Engineering
Towards practical meta-querying
Information Systems
Intensional associations between data and metadata
Proceedings of the 2007 ACM SIGMOD international conference on Management of data
A context-based model for the interpretation of polysemous terms
OTM'10 Proceedings of the 2010 international conference on On the move to meaningful internet systems: Part II
| Hi-index | 0.01 |
Attributes, a.k.a. slots or properties, are the main mechanism used to define associations between concepts or individuals modeling real world entities in a knowledge base. Traditionally, an attribute is defined by an explicit statement that specifies the name of the attribute and the entities it associates. This has three main limitations: (i) it is not easy to apply to large amounts of data, even if they share the same characteristics, since explicit definitions are needed for each concept or individual; (ii) it cannot handle future data, i.e., when new concepts or individuals are inserted in the knowledge base their attributes need to be explicitly defined; and (iii) it assumes that the data engineer, or the user that is introducing a new attribute, has access and privileges to modify the respective objects. The above may not be practical in many real ontology application scenarios. We are introducing a new form of attribute in which the domain and range are not specified explicitly but intensionally, through a query that defines the set of concepts or individuals being associated. We provide the formal semantics of this new form of attribute, describe how to overcome syntax constraints that prevent the use of the proposed attribute, study its behavior, show efficient ways of implementation, and experiment with alternative evaluation strategies.