898
results
  • An ontology containing additional terminology for structuring and annotating RDFS/OWL taxonomies for describing constructions (components, materials, spatial zones, damages, construction tasks and properties). It also functions as an index for known taxonomies starting from root classes and properties. @en
  • The Construction Tasks Ontology (CTO) describes tasks operating on construction elements, spatial zones and/or damages. The tasks are either planned or executed depending on the dataset metadata context of the dataset its used in. Five different types of tasks are defined: instalment, removal, modification, repair and inspection. Consequences of tasks on the dataset, i.e. added and/or deleted triples, are modeled using reified statements. The tasks can link to a reified statement using the CTO relations. @en
  • The ontology, presented here in a beta version, is based on the analysis of the documentation and descriptive requirements of the Intesa Sanpaolo Historical Archive and is intended to describe the content of historical banking documents and of some of the activities carried out by the bank, particularly in relation to third parties (loans, charity donations, seizures and confiscations, etc.), which involve the initiation of processes or the production of documents. The focal point of the descriptive model is the bank - an entity that initiates different types of processes, whose common feature is that they are structured into various stages/events - and the relationship between the documentation produced and the information it contains. In fact, this ontology is based on information collected from archived documents which describe various processes and activities carried out by banking institutions: the starting point for its construction were the inventories and databases of documentation stored in the Historical Archive which was produced by the various banks that over time were merged into Intesa Sanpaolo. The ontology was created to provide a sufficiently abstract representation and model for describing the processes of various banking activities from which the documentation was produced - from a company's request for financing and its outcome, to the preparation of seizure, confiscation and asset restitution filings, to charitable contributions, just to mention a few examples - reusing models that were already well established and widely used. The structure of the proposed ontology is in fact intended to adapt to the various activities, described in the archive files that a banking institution performs in relation to third parties. The proposed ontology is therefore not an ontology on banking activity in general, but on the relationship between this activity and the documents that are produced. Moreover, its objective is not to describe the documents in the strict sense of the term, for which reference is made to OAD ontology. The purpose of this project is to lay the initial, and fundamental, building blocks for describing the complexity, variety, and breadth of the domain of archiving bank records and the data they contain. Despite having data from different banks relating to different activities and having already made arrangements for the integration of third-party datasets and ontologies, before completing the project we will have to wait for the processing of representations based on other types of documents and banking institutions, including non-Italian ones. @en
  • domOS Common Ontology (dCO) represents a common information model to share a unified understanding for humans and machines and to ensure semantic interoperability in a heterogeneous IoT infrastructure. This ontology allows the decoupling of the infrastructure from the software services and applications. @en
  • This ontology describes wildlife observations generated by sensors. @en
  • An ontology for describing changes between OWL ontology versions @en
  • The DINGO ontology (Data Integration for Grant Ontology) defines the terms of the DINGO vocabulary and provides a machine readable extensible framework to model data relative to projects, funding, project and funding actors, and, notably, funding policies. It is designed to yield high modeling power and elasticity to cope with the huge variety in funding and project practices, which makes it applicable to many areas where funding is an important aspect: first of all research, but also the arts, cultural conservation, and many others. @en
  • The scope of the DIO is the domain of design intent or design rationale that needs to be documented while undertaking the design of any artifact @en
  • Ontology that defines the topology of damages in constructions. @en
  • The Data Privacy Vocabulary (DPV) provides terms (classes and properties) to represent information about processing of personal data, for example - purposes, processing operations, personal data, technical and organisational measures. @en
  • Extension to the Data Privacy Vocabulary (DPV) providing additional categories of personal data @en
  • To ensure comparability between schemas from different data models, the Description of a Data Source (DSD) vocabulary has been developed. @en
  • The DNS Security Ontology (DSecO) project is a data model for representing and reasoning on Domain Name System (DNS) data. The ontology is developed using web technologies (e.g. RDF, OWL, SKOS) and is intended as a structure for realizing a DNS Knowledge Graph (KG) for administration and security assessment applications. The model has been developed in collaboration with operational teams, and in connection with third parties linked vocabularies. Alignment with third parties vocabularies is implemented on a per class or per property basis when relevant (e.g. with `rdfs:subClassOf`, `owl:equivalentClass`). Directions for direct instanciation of these vocabularies are provided for cases where implementing a class/property alignment is redundant. Alignment holds for the following vocabulary releases: - [ORG](https://www.w3.org/TR/vocab-org/) 0.8 - [UCO](https://github.com/ucoProject/uco) Release-0.8.0 @en
  • This ontology is a composition of some content design patterns for the semiotic triangle. Its structure is extracted from DOLCE-Ultralite (DOLCE+c.DnS), but it uses a different terminology, @en