The AtomOWL ontology is inspired from the work done by the atom working group. This ontology is working off the rfc 4287 published among othe places at http://www.atompub.org/rfc4287.html . The AtomOWL ontology uses as much as possible the same terms as the format there to make the relation easy to understand. The AtomOWL name space is slightly different from the atom namespace [see post http://www.imc.org/atom-syntax/mail-archive/msg16476.html]. But this is a good thing as it helps distinguish the ontology from the rfc 4287 serialisation. @en
ccp- Vocabulary for prices options in Cloud Computing Services
http://cookingbigdata.com/linkeddata/ccpricing
Simple and direct pricing ontology for Cloud Computing Services. This ontology allows to define model of prices used in large cloud computing providers such as Amazon, Azure, etc., including options for regions, type of instances, prices specification, etc. @en
ccr- Vocabulary for Regions and Zones on Cloud Computing
http://cookingbigdata.com/linkeddata/ccregions
Ontology for the definition of regions and zones of availability on CloudComputing platforms and services. This ontology allows to define model of regions used in large cloud computing providers such as Amazon, Azure, etc. @en
ccsla- Service Level Agreement for Cloud Computing
http://cookingbigdata.com/linkeddata/ccsla
Service Level Agreement for Cloud Computing Services. This ontology allows to define model of SLA/SLO used in large cloud computing providers such as Amazon, Azure, etc., including terms, claims, credit, compensations, etc @en
cci- Ontology for Cloud Computing instances
http://cookingbigdata.com/linkeddata/ccinstances
Ontology for Cloud Computing Instances. Instance are classes of VM that comprise varying combinations of CPU, memory, storage, and networking capacity. This ontology allows to define the instantiation model of MVs used in large cloud computing providers such as Amazon, Azure, etc. @en
pni- SNaP Identifier Ontology
http://data.press.net/ontology/identifier/
The Identifier Ontology models non-RDF based Identifiers for resources. It is used to maintain a mapping between RDF resources identifiers and their equivalent IDs in an alternate, non-RDF based domain. @en
graphql- GraphQL Vocabulary
http://datashapes.org/graphql
A vocabulary to annotate RDF schemas (in particular SHACL shapes) with metadata to define mappings to GraphQL. @en
li- OWL representation of ISO 19115 (Geographic Information - Metadata - Lineage package)
An OWL representation of parts of the Geographic Metadata model described in ISO 19115:2003 with Corrigendum 2006 - LI Package @en
r4r- Relations for Reusing (R4R) Ontology
http://guava.iis.sinica.edu.tw/r4r
R4R is a light-weight ontology for representing general relationships of resource for publication and reusing. It asserts that a certain reusing context occurred and determined by its two basic relations, namely, isPackagedWith and isCitedBy. The isPackagedWith relation declares the resource is ready to be reused by incorporating License and Provenance information. The Cites relation is an exceptional to isCitedBy which occurs only two related objects cite each other at the same time. Five resource objects including article, data, code, provenance and license are major class concepts to represent in this ontology.
The namespace for all R4R terms is http://guava.iis.sinica.edu.tw/r4r/ @en
dogont- Ontology Modeling for Intelligent Domotic Environments
http://elite.polito.it/ontologies/dogont.owl
The DogOnt ontology supports device/network independent description of houses, including both controllable and architectural elements. @en
eupont- EUPont: an ontology for End User Programming of the IoT
http://elite.polito.it/ontologies/eupont.owl
EUPont is an ontology to model high level rules for Internet of Things End User Programming (IoT-EUP). @en
hr- hRESTS Ontology
http://iserve.kmi.open.ac.uk/ns/hrests
hRESTS is a vocabulary for describing RESTful Web services @en
msm- Minimal Service Model
http://iserve.kmi.open.ac.uk/ns/msm
A simple RDF(S) ontology able to capture (part of) the semantics of both Web services and Web APIs @en
ends- Vocabulary of endpoint status (availability, responseTime)
http://labs.mondeca.com/vocab/endpointStatus
Endpoint Status vocabulary intends to describe endpoint availability @en
kgc- KGRC Ontology
http://kgc.knowledge-graph.jp/ontology/kgc.owl
This vocabulary set can represent 5W1H (Who, What, When, Where, Why, How) in event (scene) descriptions. This file is also provided in Knowledge Graph Reasoning Challenge. @en