Versions Compared

Old Version 25

changes.mady.by.user Wendy Thomas

Saved on

compared with

New Version 26

changes.mady.by.user Wendy Thomas

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

2020-2021 Minutes Page, 2018-2019 Minutes Page, 2016-2017 Minutes Page, Pre-2016 Minutes Page

Expand
title2022-07-21

ATTENDEES: Wendy, Jon, Jeremy, Darren, Flavio

1-Notified TC on the content of the ISI IPS proposal
25 years of DDI working with statistical agencies
Enthusiastic response from invited speakers/agencies

2-Implementation Meeting (around EDDI)
Practical perspective: Jon will talk to Alaina about space
Send outline of meeting to Arofan

3-Codebook: update on preparations
Send to Jared for review announcement
Finish CV and Geography sections of high-level documents

4-Review of workplan for TC August meeting

https://docs.google.com/spreadsheets/d/19er_IoEyLm-YhNdkegDy7CcYJXMaRDWuRwV40FjcGTs/edit?usp=sharing
Ambitious, but nothing missing
Specifics will arise during discussions
Good to bring in the overall process workflows and tooling information

Expand
title2022-06-23

ATTENDEES: Wendy, Dan, Jon, Darren, Flavio

Implementation Language meeting around EDDI

Funding for Fall meeting on Implementation Languages has been approved. We need to develop a more fully developed outline for this meeting to discuss with CDI later in July.

  • Week after would be better due to room availability

  • EDDI Right after Thanksgiving (Wednesday-Thursday)

  • Hackathon (check with Ingo)

  • More generic meeting on the Friday for broader contribution and gory details the next week (3 days?)

  • Identify specific implementations

  • What needs to be done in a consistent manner

  • What can be flexible

  • Explanation of usage needed

Codebook 2.6 review

  • wlt provide Jon with link - upload

COGS

No Jon next two weeks - no actions on COGS until then

August meeting of TC in Minneapolis

Funding has been approved

Specific goals and outputs from August meeting:

--Document changes in structure
--XML, RDF, JSON, UML/XMI (canonical), Sphinx and restructured text documentation
--Rules and output where possible - reconciling between the schema and outputs
--when we cut the cord that we are able to get back to the 3.3 schema
--What the different serializations look like - just doing vanilla transformations are a bit pointless
--Technical review - can roll out serializations separately
--XML and JSON are currently the most used and most stable and are probably ready first for review
--RDF and UML/XMI has been tested by EA
--If we wanted canonical XMI we have to change output or use the translation tool used by CDI
--Build in canonical XMI as an output (currently has 2 - Normative 2.4.2, 2.5 with diagram and diagram exchange) new flavor would be canonical
--Discussion of TC future leadership and roles
--Change log of XML structure between 3.3 and 3.4 to see what changed and why (supporting multiple serializations)
--Talking about changes - tree hierarchy is still the same but there are other things that are being updated to XML centric (CHOICE models) - substitution groups, removing a few things that are remnants of 3.0 and 3.1 (Identification and Reference properties)

CANCEL Next two meetings - June 30, July 7

...

Expand
title2022-05-19

ATTENDEES: Wendy, Jon, Darren, Oliver, Dan S.

Annual Report

No additional comments, will leave available through Sunday and then send in

Codebook

  • Field level documentation HTML version has been completed

  • Wendy will review Change Log and update, set up review page and create the google page for the high level documentation draft

  • Review should start by end of May. This should last to the middle or end of August

  • Anticipate easy review because there has been a lot of consultation - this should mean that developers can begin work using the Review version we some certainty

COGS work

Reference:

  • Reference properties outside of the identification is the issue

  • Reference is an entity and will act differently with serialization - RDF is a URI, XML / JSON model

  • Review specifics of properties - Wendy will document

    • Example: Where you need to know a context of what you are referencing add another reference for context.

    • Including extra properties

  • Option is to create Complex types

    • Reference becomes an element in the complex

    • Where is such extended content needed

Identifiers:

  • don't think there is any difficulty by serialization. Some have their own identification (URI in RDF)

  • Drop the difference between Versionable and Maintainable. There is only one way to identify an item (URN, AGENCY, ID, VERSION)

  • Additional properties

    • Describable class extension of versionable

    • Properties found in versionable - review

  • Identification is injected during creation of serializations

    • Inject identfication into any item type will have identification

    • Complex data types DON'T get Identification

  • Another area of confusion for additional properties is the use of Name/Type/Description and Citation (currently used singularly or together in some elements)

    • Look at where citation is used and how. OtherMaterialTypes (clean-up later) Group? StudyUnit? ResourcePackage, Instance, etc.

CHOICE issues are being sorted

PhysicalDataProduct

  • Add NCubeInstance to the basic RecordLayout now in the main schema

  • Make the others derivatives of the BaseRecordLayoutType with unique element names and move the content to PhysicalDataProduct

  • This will get everything in AND let us use one PhysicalDataProduct to import

Representations

  • Recreate the few representation types that are not in the ManagedRepresentations.

  • This gives them the same structure and we can determine later if we want to continue this division between representations that have references to other objects or what.

CV and RDF resolver:
The sandbox will be set up end of next week

https://rdf-vocabulary.ddialliance.org/cv
e.g. https://rdftest-vocabulary.ddialliance.org/cv/ModeOfCollection/1.0.1

...