15,627
edits
Changes
Jump to navigation
Jump to search
Line 1:
Line 1: − Work in progress.+ − * How do we structure [https://en.wikipedia.org/wiki/Internet_of_things Internet of Things] (IoT) devices like Tesla Cars or [https://en.wikipedia.org/wiki/Amazon_Echo Amazon Echo] / [https://en.wikipedia.org/wiki/Amazon_Alexa Alexa]?+ − + − * One item by services? But what is the services? Typically Amazon Echo devices are linked to Alexa services, but they may differ in data collection. − * Can we do a type of data collection and inject it in all Tesla Cars Model? − − == Internet of Things & Connected Devices Ontology ==+ − Every devices have 3 "module" that seem interesting for personaldata:+ − * The device (for example ssn:Device or iot-o:SoftwareAgent) − * The sensing module, what kind of data is possible to record on a given device − * The service module. In many cases, the IoT and the programmable web are very close. Connected devices can be seen as service providers and consumers,and by specifying a notion of service, every aspect of an IoT system can be represented. <ref>[https://hal.archives-ouvertes.fr/hal-01467853v2 IoT-O, a Core-Domain IoT Ontology to Represent Connected Devices Networks]</ref> − === Literature ===+ − + − + − + − − === Use cases === − The Ontology need to be suitable for data entries and the usages of those data. We need to identify use case and test the ontology against those. − * For a given '''device''' I want to know what the device's '''sensors''' may record+ − * For a given '''device''' I want to know what the device's '''sensors''' may transmit to third party+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
→defining properties for a type
This project has two levels of reflexion:
* how to model the offline and online world, and their interface;
* Should we make on item by model? Group of model?
* how to make this model fit into our wiki instance.
* How do we index data controllers? Etc?
The two are likely to involve different types of contributors and contributions. Both should listen to each other, and to [[Project:Tools]] which critically depends on both levels of choices.
For clarity at the moment, rather than dividing along those two levels, we currently divide matters along "sectors". We hope that eventually this will change.
* [[Project:Vocabulary/IoT]]
* https://www.w3.org/Submission/iot-lite/
* [[Project:Vocabulary/GDPR]]
* https://www.w3.org/2005/Incubator/ssn/ssnx/ssn
* [[Project:Vocabulary/Adtech]]
* https://arxiv.org/abs/1707.00112 (A study of existing Ontologies in the IoT-domain)
* your own subdomain of interest, which should really be documented here by the time tools depend on it
* https://hal.archives-ouvertes.fr/hal-01467853v2 (IoT-O, a Core-Domain IoT Ontology to Represent Connected Devices Networks)
== Documenting ==
To get started quickly, we recommend simply different phases:
1. pointing to "good enough in class" examples (the best in class examples risk being overly complex)
2. document how this is done using the Q and P templates
== Defining properties for a type ==
{{SPARQL|query=
SELECT ?class ?classLabel ?wikidataQid ?property ?propertyLabel ?wikidataPid WHERE {
?class pdiot:P291 ?property.
OPTIONAL {?class pdiot:P103 ?wikidataQid}
OPTIONAL {?property pdiot:P104 ?wikidataPid}
SERVICE wikibase:label {
bd:serviceParam wikibase:language "en" .
}
}
ORDER BY ASC(?classLabel)
LIMIT 100
|label=expected properties
}}
{{SPARQL|query=
#defaultView:Graph
SELECT ?class ?classLabel ?rgb ?property ?propertyLabel WHERE {
?class pdiot:P291 ?property.
BIND ("111177" AS ?rgb)
SERVICE wikibase:label {
bd:serviceParam wikibase:language "en" .
}
}
ORDER BY ASC(?classLabel)
LIMIT 100
|label=graph of expected properties
}}