- Agent Registry
- Conceptual Content
- Controlled Vocabulary
- Custom Metadata
- Data Capture Instrument
- Data Description
- Data Management
- Descriptive Codebook
- Sampling
- Statistical Classification
- Structured Geography
| - Agents
- Business Workflow
- Collections Pattern
- Complex Data Types
- Conceptual
- Custom Metadata
- Data Capture
- Discovery
- Enumerations
- Format Description
- Geographic Classification
- Identification
- Logical Data Description
- Methodologies
- Methodology Pattern
- Primitives
- Process Pattern
- Regular Expressions
- Representations
- Sampling Methodology
- Signification Pattern
- Simple Codebook
- Simple Methodology Overview
- Study Related
- Utility
- Workflows
| - Codebook
- Data capture - simple questionnaire content and flow, non-question based data (register data, simple protocols, internet, etc.)
- Data description - various formats
- Data processing
- Data transformations
- Archive a study (repository)
- Simple study description (catalog)
- Statistical classifications
- Geographic classifications
| - The Model: although this is at the heart of the documentation, we would also like to have a processable version of the model in XMI (an XML format for describing models). This will be in canonical XMI, a flavor of that format supported across many UML tools. There will only be an XML file for the entire model being published – there is no sub-set for each View, etc. as for some other deliverables.
- XML Schemas: Descriptions of both the full class library and subset XML Schemas for each identified Functional View (groupings of objects to support specific functions).
- RDF-S/OWL Vocabulary for RDF: There will be a vocabulary for the entire library, and a set of Functional View-level vocabularies. These would be expressed using OWL.
- Documentation: (additional details in this linked document from Dagstuhl sprint)
- High-level overview document describing the model and how it functions. This will include the definition and description of the views (however they are formed)
- Class-level descriptions in Drupal that include language about examples
- Individual document for each use case to include description and method/rationale along with an example in xml:
- Codebook
- Simple questionnaire and flow
- Non-question based data
- Data description - should we include the various formats in one document or separate them?
- Data processing/transformation - separate or together?
- Statistical classification
- Geographic classification
- Archived study/study description
- Mapping to DDI v2.5
- Mapping to DDI v3.2 (or v3.3?)
- Mapping to GSIM v1.1
- RDF-S/OWL Vocabulary
|