Difference between revisions of "Project:Vocabulary"

From Wikibase Personal data
Jump to navigation Jump to search
 
(5 intermediate revisions by the same user not shown)
Line 7: Line 7:
 
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
  
  
Line 15: Line 17:
 
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
 +
}}

Latest revision as of 01:39, 11 February 2020

This project has two levels of reflexion:

  • how to model the offline and online world, and their interface;
  • how to make this model fit into our wiki instance.

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.


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

PREFIX pdio: <https://wiki.personaldata.io/entity/>
PREFIX pdiot: <https://wiki.personaldata.io/prop/direct/>
PREFIX pdiop: <https://wiki.personaldata.io/prop/>
PREFIX pdiops: <https://wiki.personaldata.io/prop/statement/>
PREFIX pdiopq: <https://wiki.personaldata.io/prop/qualifier/>
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

expected properties (embedded)


PREFIX pdio: <https://wiki.personaldata.io/entity/>
PREFIX pdiot: <https://wiki.personaldata.io/prop/direct/>
PREFIX pdiop: <https://wiki.personaldata.io/prop/>
PREFIX pdiops: <https://wiki.personaldata.io/prop/statement/>
PREFIX pdiopq: <https://wiki.personaldata.io/prop/qualifier/>
#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

graph of expected properties (embedded)