Unverified Commit 6a874ebb authored by Maxime Lefrançois's avatar Maxime Lefrançois
Browse files

updated documentation for V2.1.1

parent deae9025
Loading
Loading
Loading
Loading
Loading
+20 −1
Original line number Diff line number Diff line
This is the SAREF extension for automotive
 No newline at end of file
<div class="alert-warning">NOTE: The text in this section is extracted from ETSI TS 103 410-7 (V2.1.1) <a href="#[0]">[0]</a>, and therefore falls inside the <a href="https://www.etsi.org/intellectual-property-rights">ETSI IPR Policy</a></div>

The present document is a technical specification of SAREF4AUTO, an OWL-DL ontology that extends SAREF <a href="#[1]">[1]</a>  for the Automotive domain. 

The present document is a major revision of SAREF4AUTO ontology extension, developed in the context of the STF 653, using updated reference ontology patterns specified in ETSI TS 103 548 <a href="#[2]">[2]</a>  to solve the harmonization needs identified in ETSI TR 103 781 <a href="#[i.2]">[i.2]</a> , with updated development framework and tools defined in ETSI TS 103 673 <a href="#[3]">[3]</a> .

ETSI TS 103 410-7 (V1.1.1) <a href="#[i.1]">[i.1]</a>  has been developed in the context of the STF 566, an ETSI specialists task force that was established with the goal to extend SAREF for the domains of Automotive, eHealth/Ageing-well, Wearables and Water (see [https://portal.etsi.org/STF/STFs/STF-HomePages/STF566](https://portal.etsi.org/STF/STFs/STF-HomePages/STF566)). 

The intention of SAREF4AUTO is to connect SAREF with existing ontologies (such as W3C SSN, W3C SOSA, GeoSPARQL <a href="#[i.7]">[i.7]</a> , etc.) and important standardization initiatives and ontologies in the Automotive domain, as mentioned in the associated SAREF4AUTO requirements document ETSI TR 103 508 <a href="#[i.3]">[i.3]</a> , including: 

* ETSI TC ITS for V2V communications <a href="#[i.8]">[i.8]</a> . 
* The SENSORIS data model <a href="#[i.4]">[i.4]</a>  for exchanging data between vehicles and cloud services.
* The DATEX II standard <a href="#[i.5]">[i.5]</a>  for information exchange between traffic management centres, traffic information centres and service providers. 
* The DATEX II Parking Publications <a href="#[i.6]">[i.6]</a>  for specifying information about parking sites and individual parking vehicles. 

To show the potential of SAREF4AUTO, the present document focuses on adapting the common data dictionary ETSI TS 102 894-2 <a href="#[i.8]">[i.8]</a>  of ETSI TC ITS, and extend it with "platooning", and "Automated Valet Parking (AVP)" adapted from SAREF4AUTO V1.1.

As all the SAREF ontologies, SAREF4AUTO is a dynamic semantic model that is meant to evolve over time. Therefore, the stakeholders in the Automotive domain are invited to use, validate and provide feedback on SAREF4AUTO, collaborating with the SAREF ontology experts to improve and evolve SAREF4AUTO in an iterative and interactive manner, so that changes and additions can be incorporated in future releases of the present document.

The prefixes and namespaces used in SAREF4AUTO and in the present document are listed in [the Namespace Declarations section](#namespacedeclarations).
+1 −1
Original line number Diff line number Diff line
- Ramon Souza Schwartz ([TNO](https://tno.nl/))
 No newline at end of file
- [David Gnabasik](https://www.linkedin.com/in/david-gnabasik-0056a0ba/) ([MINES Saint-Étienne](https://www.mines-stetienne.fr/))
+1 −2
Original line number Diff line number Diff line
- [Laura Daniele](https://www.linkedin.com/in/lauradaniele) ([TNO](https://tno.nl/))
- [Michelle Wetterwald](http://netellany.fr/) ([Netellany/FBConsulting](http://netellany.fr/))
- [Maxime Lefrançois](http://maxime-lefrancois.info/me#) ([MINES Saint-Étienne](https://www.mines-stetienne.fr/))
+7 −2
Original line number Diff line number Diff line
<h3>General Overview</h3>

<p>The documentation for SAREF4AUTO is missing. Please refer to the corresponding technical specification for more information.</p> 
<p>An overview of the SAREF4AUTO ontology is provided in <a href="#Figure_1">Figure 1</a>. For all the entities described in <a href="#[0]">the technical specification ETSI TS 103 410-7</a>, it is indicated whether they are defined in the SAREF4AUTO extension or elsewhere by the prefix included before their identifier, i.e. if the element is defined in SAREF4AUTO, the prefix is s4auto, while if the element is reused from another ontology, it is indicated by a prefix according to <a href="#namespacedeclarations">the Namespace Declarations section</a>. Colour codes also help to distinguish the provenance of entities.</p>
<p>Diagrams are to be interpreted using the Chowlk notation <a href="#[3]">[3]</a>, clause 9.7.2.</p>
<div class="alert-info">NOTE: <a href="#Figure_1">Figure 1</a> aims at showing a global overview of the main classes of SAREF4AUTO and their mutual relations. More details on the different parts of <a href="#Figure_1">Figure 1</a> are provided in clause 5 and clause 6 of <a href="#[0]">the technical specification ETSI TS 103 410-7</a>. </div>

<strong>ETSI Technical Specification:</strong> <a href="https://www.etsi.org/deliver/etsi_ts/103400_103499/10341007/01.01.01_60/ts_10341007v010101p.pdf">ETSI TS 103 410-7 V1.1.1 (2020-07): "SmartM2M; Extension to SAREF; Part 7: Automotive Domain"</a>
<figure>
  <a href="diagrams/SAREF4AUTO_figures.Overview.png"><img src="diagrams/SAREF4AUTO_figures.Overview.png" alt="SAREF4AUTO overview"/></a>
  <figcaption id="Figure_1">Figure 1: SAREF4AUTO overview</figcaption>
</figure>
+27 −2
Original line number Diff line number Diff line
<h3>Normative references</h3>

<ul>
  <li id="[1]">[1] ETSI TS 103 264 (V3.1.1) (02-2020): "SmartM2M; Smart Applications; Reference Ontology and oneM2M Mapping".</li>
  <li><a id="[0]">[0]</a> <a href="https://www.etsi.org/deliver/etsi_ts/103400_103499/10341007">ETSI TS 103 410-7 (V2.1.1)</a>: "SmartM2M; Extension to SAREF; Part 7: Automotive Domain".</li>
  <li><a id="[1]">[1]</a> <a href="https://www.etsi.org/deliver/etsi_ts/103200_103299/103264/">ETSI TS 103 264</a>: "SmartM2M; Smart Applications; Reference Ontology and oneM2M Mapping".</li>
  <li><a id="[2]">[2]</a> <a href="https://www.etsi.org/deliver/etsi_ts/103500_103599/103548/">ETSI TS 103 548</a>: "SmartM2M; SAREF reference ontology patterns".</li>
  <li><a id="[3]">[3]</a> <a href="https://www.etsi.org/deliver/etsi_ts/103600_103699/103673/">ETSI TS 103 673</a>: "SmartM2M; SAREF Development Framework and Workflow, Streamlining the Development of SAREF and its Extensions".</li>
</ul>

<h3>Informative references</h3>

<ul>

  <li><a id="[i.1]">[i.1]</a> ETSI TS 103 410-7 (V1.1.1) (07-2020): "SmartM2M; Extension to SAREF; Part 7: Automotive Domain".</li>
  <li><a id="[i.2]">[i.2]</a> ETSI TR 103 781 (V1.1.1) (09-2023): "SmartM2M; Study for SAREF ontology patterns and usage guidelines".</li>
  <li><a id="[i.3]">[i.3]</a> ETSI TR 103 508 (V1.1.1) (10-2019): "SmartM2M; SAREF extension investigation; Requirements for Automotive".</li>
  <li><a id="[i.4]">[i.4]</a> SENSORIS: "<a href="https://sensor-is.org/">Sensor Interface Specification</a>".</li>
  <li><a id="[i.5]">[i.5]</a> EN 16157-2:2019: "Intelligent transport systems - DATEX II data exchange specifications for sqtraffic management and information - Part 2: Location referencing", produced by CEN.</li>
  <li><a id="[i.6]">[i.6]</a> "<a href="https://repo.datex2.eu/sites/default/files/ParkingPublications_v1.0a.pdf">The DATEX II Parking Publications Extension</a>".</li>
  <li><a id="[i.7]">[i.7]</a> OGC 11-052r4: "OGC GeoSPARQL - A Geographic Query Language for RDF Data". Version 1.0.</li>
  <li><a id="[i.8]">[i.8]</a> ETSI TS 102 894-2: "Intelligent Transport Systems (ITS); Users and applications requirements; Part 2: Applications and facilities layer common data dictionary".</li>
  <li><a id="[i.9]">[i.9]</a> <a href="https://www.sae.org/standards/content/j3016_202104/">SAE J3016™</a>: "Taxonomy and Definitions for Terms Related to On-Road Motor Vehicle Automated Driving Systems".</li>
  <li><a id="[i.10]">[i.10]</a> ISO/IEC 11578:1996: "Information technology -- Open Systems Interconnection -- Remote Procedure Call (RPC)".</li>
  <li><a id="[i.11]">[i.11]</a> Recommendation ITU-T X.667: "Information technology - Procedures for the operation of object identifier registration authorities: Generation of universally unique identifiers and their use in object identifiers".</li>
  <li><a id="[i.12]">[i.12]</a> ISO/IEC 9834-8:2014: "Information technology -- Procedures for the operation of object identifier registration authorities -- Part 8: Generation of universally unique identifiers (UUIDs) and their use in object identifiers".</li>
  <li><a id="[i.13]">[i.13]</a> European Agreement (Applicable as from 1 January 2011): "<a href="https://unece.org/adr-2011-files">Concerning the International Carriage of Dangerous Goods by Road</a>". </li>
  <li><a id="[i.14]">[i.14]</a> United Nations: "<a href="https://unece.org/rev-12-2001">Recommendations on the Transport of Dangerous Goods - Model Regulations</a>", Twelfth revised edition.</li>
  <li><a id="[i.15]">[i.15]</a> ISO 3779 (2011-07): "Road vehicles - Vehicle identification number (VIN) Content and structure".</li>
  <li><a id="[i.16]">[i.16]</a> ETSI TS 103 301: "Intelligent Transport Systems (ITS); Vehicular Communications; Basic Set of Applications; Facilities layer protocols and communication requirements for infrastructure services; Release 2".</li>
  <li><a id="[i.17]">[i.17]</a> UNECE/TRANS/WP.29/78/Rev.4: "Consolidated Resolution on the Construction of Vehicles (R.E.3)".</li>
  <li><a id="[i.18]">[i.18]</a> ETSI TS 103 300-2 "Intelligent Transport Systems (ITS); Vulnerable Road Users (VRU) awareness; Part 2: Functional Architecture and Requirements definition; Release 2".</li>
  <li><a id="[i.19]">[i.19]</a> ISO 8855: "Road vehicles -- Vehicle dynamics and road-holding ability -- Vocabulary".</li>
  <li><a id="[i.20]">[i.20]</a> ISO 3833: "Road vehicles -- Types -- Terms and definitions".</li>
  <li><a id="[i.21]">[i.21]</a> ISO/TS 19091:2019: "Intelligent transport systems -- Cooperative ITS -- Using V2I and I2V communications for applications related to signalized intersections".</li>
  <li><a id="[i.22]">[i.22]</a> IETF RFC 3966: "The tel URI for Telephone Numbers".</li>
  <li><a id="[i.23]">[i.23]</a> ENSEMBLE Project deliverable D2.3: "V2 Platooning use cases, scenario definition and Platooning Levels".</li>
</ul>