Skip to content

Minutes 18 october 2012

mazlo edited this page Oct 19, 2012 · 8 revisions

###identifying use-cases

  • identified attributes for Study(/StudyGroup) from the open issues list
  • new properties and use-case descriptions are documented in the google doc
  • by agency: "Find data published by a specific organization"
  • identified differences between dct:creator, dct:publisher, distributor, producer
  • added one more use-case motivated by the distinction of the terms
  • "by agency" became "by publishing agency", e.g. "Find data published by a specific organization"
  • added "by creator/contributor", e.g. "Find data attributed to a specific researcher"
  • by study: "Find study by free text search in title or abstract, kind of data, or unit of analysis, …"
  • skipped "versioning" and "dct:provenence" to model it properly in future
  • added attribute "dct:available": people want to know what the publication date is, or when the study will be available
  • added attribute "dct:purpose": paragraph that states why the study was conducted
  • added attributes "dct:subject", "dct:title", "subtitle" and "dct:alternative" functioning as the alternative title
  • added attribute "kindOfData" and "analysisUnit" according to the DDI model
  • identified "dct:Dataset" to be a superclass of our "disco:DataFile"
  • discussion: difference between universe and coverage
  • universe: is the population that you've studied, e.g. "children born in one week in 1970 in UK"
  • coverage: application to the datafile in terms of topic; study level thing
  • group agrees to have that distinction and that it is modelled correclty
  • by coverage: "Find data which was collected on a specific part of population or geographic location"
  • added to Coverage "dct:spatial", "dct:temporal", "dct:subject"
  • discussion: is Universe actually a skos:Concept?
  • yes.
  • added to Universe "skos:broader/narrower"
  • by instrument: "Find data collected by a specific “device” (e.g., survey)"
  • added "rdfs:label", "rdfs:comment", "externalDocument", i.e. URL, that points to the documentation
  • by variables: "Find datasets by searching the properties of variables, e.g., their associated concepts and data elements, representation, description and analysis unit"
  • introduced element "AnalysisUnit" being a subclass of "skos:Concept"; since "analysisUnit" as an property is used in various places
  • relationship to Study
  • relationship to Variable
  • by concepts: "Find variables of a specific topic (e.g. education)"
  • by questions: "Find all variables which are populated by specific questions (description)."
  • added "collectionMode" to Questionnaire, according to DDI. values are blank nodes or "skos:Concept"
  • Study - Instrument: cardinality might have to be changed if we want to have reusable instruments in the future
  • by concepts (Questions): .. missing ..
  • by variables (Questions): "Find questions (name, labels) and their response categories which are using a specific variable (e.g. age)"
  • by question text: "Find questions by searching on the question text or name"
  • by universe/coverage (Questions): "Find questions by searching on the related coverage in the universe links of studies"

###Further Design Issues

  • Datatype Properties
  • citation (Instrument): dropped it, since it is not used in this context
  • name (Universe): added
  • citation (LogicalDataSet): discussion: do we need this?
  • added "disco:ddiFile" attribute to Study pointing to foaf:Document. Represents a human-readable form
  • citation is not introduced in LogicalDataSet
  • checked the other datatype properties and erased unused

###Summurization/Conclusion

  • We have walked through all of the open issues identified at the last meeting
  • the most important issues were
  • the ontology base url and prefix
  • checking consistency, basically the naming conventions and cardinalities
  • building up use-cases
  • we than started to walk through all datatypeProperties and objectProperties which were left for discussion after the last meeting
  • identified a small set of use-cases and tried to find these in the model; some properties were added and removed respectively.
  • updated the turtle file along with modifications on the model
Clone this wiki locally