This HTML5 document contains 7 embedded RDF statements represented using HTML+Microdata notation.

The embedded RDF content will be recognized by any processor of HTML5 Microdata.

PrefixNamespace IRI
dctermshttp://purl.org/dc/terms/
n4http://dbkwik.webdatacommons.org/ontology/
n7http://dbkwik.webdatacommons.org/resource/19tSpAANsdrZ7y0svVlUCg==
n6http://dbkwik.webdatacommons.org/resource/3Xyh9uzRsGHUvpPGzXNOSw==
rdfshttp://www.w3.org/2000/01/rdf-schema#
n2http://dbkwik.webdatacommons.org/resource/n-theIF_Na4z9d-JKGA5xw==
n10http://dbkwik.webdatacommons.org/resource/D6ZRrikdCxK9BH1dyfDrlA==
rdfhttp://www.w3.org/1999/02/22-rdf-syntax-ns#
n5http://dbkwik.webdatacommons.org/sca21/property/
xsdhhttp://www.w3.org/2001/XMLSchema#
n9http://dbkwik.webdatacommons.org/resource/Zv_46RnBaskh9wZ2IwoHRA==
Subject Item
n2:
rdfs:label
Preparing for OSCD conferences
rdfs:comment
For example an agenda can be created through open collaboration on a wiki such as this one. The agenda should be open as soon as possible from when the conference is proposed. There may be tensions here which need to be worked through. For example objections (to openness) which tend to be of the kind - "people won't come" without certainty over various aspects * purposes of the conference * expected outcomes * key topics * timing and duration
dcterms:subject
n9: n10:
n5:wikiPageUsesTemplate
n6: n7:
n4:abstract
For example an agenda can be created through open collaboration on a wiki such as this one. The agenda should be open as soon as possible from when the conference is proposed. There may be tensions here which need to be worked through. For example objections (to openness) which tend to be of the kind - "people won't come" without certainty over various aspects * purposes of the conference * expected outcomes * key topics * timing and duration