15,628
edits
Changes
Jump to navigation
Jump to search
Line 7:
Line 7: − + − + + + Line 15:
Line 17: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
→defining properties for a type
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.
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:Ontology/IoT]]
* [[Project:Vocabulary/IoT]]
* [[Project:Ontology/GDPR]]
* [[Project:Vocabulary/GDPR]]
* [[Project:Vocabulary/Adtech]]
* your own subdomain of interest, which should really be documented here by the time tools depend on it
1. pointing to "good enough in class" examples (the best in class examples risk being overly complex)
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
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
}}