Newer
Older
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix xml: <http://www.w3.org/XML/1998/namespace> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix vann: <http://purl.org/vocab/vann/> .
@prefix voaf: <http://purl.org/vocommons/voaf#> .
@prefix s4ehaw: <https://saref.etsi.org/core/v3.1.1/> .
@prefix s4envi: <https://saref.etsi.org/saref4envi/> .
@prefix s4wear: <https://saref.etsi.org/saref4wear/> .
<https://saref.etsi.org/saref4ehaw/> rdf:type owl:Ontology ;
dcterms:description """The objective of SAREF4EHAW is to extend SAREF ontology for the eHealth/Ageing-well (EHAW) vertical. Clause 4.1 of the present document shortly introduces a high level view of the envisioned SAREF4EHAW semantic model and modular ontology, with the retained concepts (i.e. classes) and their relations.
SAREF4EHAW extension has been specified and formalised by investigating EHAW domain related resources, as reported in ETSI TR 103 509, such as: potential stakeholders, standardization initiatives, alliances/associations, European projects, EC directives, existing ontologies, and data repositories. Therefore, SAREF4EHAW modular ontology shall both:
- Allow the implementation of a limited set of typical EHAW related use cases already identified in ETSI TR 103 509, i.e.
- Use case 1 “elderly at home monitoring and support”,
- Use case 2 “monitoring and support of healthy lifestyles for citizens”,
- Use case 3 “Early Warning System (EWS) and Cardiovascular Accidents detection”.
- Fulfil the eHealth Ageing Well related requirements provided in ETSI TR 103 509, mainly the ontological ones that were mostly taken as input for the ontology specification.
SAREF4EHAW mainly reuses the following existing ontologies: SAREF, ETSI SmartBAN reference model, SAREF 4 Environment extension, SAREF 4 Wearables extension, SAREF4health ontology which is a very first try to somehow extend SAREF ontology for the health vertical (it has nothing to do with ETSI SAREF4XYZ naming convention). The following figure presents the high level view of SAREF4EHAW ontology.
For semantic interoperability handling purposes, an ontology based solution, combined with sensing-as-a-service and WoT strategies, is retained for SAREF4EHAW. Therefore, an upper level ontology, at service level, shall also behas been fully modelled (Service class and sub-classes depicted in the previous figure).
For embedded semantic analytics purposes, SAREF4EHAW shall behas been designed using the modularity principle (see ETSI TR 103 509) and can thus be mainly described by the following self-contained knowledge sub-ontologies (or modules): HealthActor, Ban, HealthDevice, Function (measured data related concepts included) and Service."""^^<http://www.iana.org/assignments/media-types/text/markdown> ;
dcterms:issued "date when the document is online"^^xsd:date ;
dcterms:modified "do not set this"^^xsd:date ;
dcterms:title "SAREF4EHAW: an extension of SAREF for eHealth Ageing Well domain"@en ;
vann:preferredNamespaceUri "https://saref.etsi.org/saref4ehaw/" ;
vann:preferredNamespacePrefix "s4ehaw" ;
dcterms:creator <http://www-public.imtbs-tsp.eu/~girodgen/> ;
dcterms:contributor <http://www-public.imtbs-tsp.eu/~girodgen/> ,
<https://www.linkedin.com/in/lina-nachabe-2b292457/> ,
<https://research.utwente.nl/en/persons/jo%C3%A3o-luiz-moreira> ,
<https://pdi.fbk.eu/people/profile/dragoni> ,
<http://www.maxime-lefrancois.info/> ;
dcterms:license <https://forge.etsi.org/etsi-software-license> ;
dcterms:source <https://forge.etsi.org/rep/SAREF/saref4ehaw/> ;
rdfs:seeAlso <https://www.etsi.org/deliver/etsi_tr/103500_103599/103509/01.01.01_60/tr_103509v010101p.pdf> ;
owl:imports <https://saref.etsi.org/core/v3.1.1/> ;
dcterms:publisher <https://www.etsi.org/> .
#################################################################
#################################################################
rdfs:comment "A Body Area Network or BAN contains one or multiple health devices"@en ;
rdfs:domain s4ehaw:Ban ;
rdfs:range s4ehaw:HealthDevice .
### https://saref.etsi.org/s4ehaw/followsUser
s4ehaw:followsUser rdf:type owl:ObjectProperty ;
rdfs:label "follows user"@en ;
rdfs:comment "A helper may follow one or multiple users that can in particular be patients."@en ;
rdfs:range s4ehaw:Helper ;
s4ehaw:hasActivity rdf:type owl:ObjectProperty ;
rdfs:label "has activity"@en ;
rdfs:comment "A health actor may have one or multiple activities."@en ;
rdfs:range s4ehaw:Activity ;
rdfs:domain s4ehaw:HealthActor .
### https://saref.etsi.org/s4ehaw/hasBanApplicationDomain
s4ehaw:hasBanApplicationDomain rdf:type owl:ObjectProperty ;
rdfs:label "has ban application domain"@en ;
rdfs:comment "The BAN application domain - healthcare, telemedicine, assisted living, sport training, pervasive computing, safety and emergency... -."@en ;
rdfs:domain s4ehaw:Ban ;
rdfs:range s4ehaw:BanApplicationDomain .
### https://saref.etsi.org/s4ehaw/hasCommunicationFunction
s4ehaw:hasCommunicationFunction rdf:type owl:ObjectProperty ;
rdfs:label "has communication function"@en ;
rdfs:comment "A BAN has a communication function that is the type of communication carried out between BAN devices and BAN Hub."@en ;
rdfs:domain s4ehaw:Ban ;
rdfs:range s4ehaw:CommunicationFunction .
### https://saref.etsi.org/s4ehaw/hasComputingPower
s4ehaw:hasComputingPower rdf:type owl:ObjectProperty ;
rdfs:comment "A health device type has computing power describing the processing power or capabilities of the device (e.g. processor ID and manufacturer, duty cycle, available flash/RM memory, maximum flash/RAM memory...)."@en ;
### https://saref.etsi.org/s4ehaw/hasConstraint
s4ehaw:hasConstraint rdf:type owl:ObjectProperty ;
rdfs:comment "Data has constraints (validity, operating, security...)."@en ;
rdfs:range s4ehaw:Constraint ;
rdfs:domain s4ehaw:Data .
s4ehaw:hasContact rdf:type owl:ObjectProperty ;
rdfs:label "has contact"@en ;
rdfs:comment "A BAN has one or multiple contacts (e.g. the patient or user that is monitored through this BAN, the caregiver that is using this BAN for monitoring purposes)."@en ;
rdfs:domain s4ehaw:Ban ;
rdfs:range s4ehaw:Contact .
rdfs:label "has data"@en ;
rdfs:comment "A function has one or many data, for example a tracking function shall include latitude, longitude and speed data."@en ;
rdfs:range s4ehaw:Data ;
rdfs:domain saref:Function .
### https://saref.etsi.org/s4ehaw/hasDeviceType
s4ehaw:hasDeviceType rdf:type owl:ObjectProperty ;
Loading full blame...