ATTENDEES: Wendy, Dan S., Taina, Darren, Julian, Jon, Sanda, Steve McCecern

Review of changes in citation content:
Go through and find alternative way to test new xsd content to verify. Maybe deal with technical validation in TC.

Best Practice document:
Best Practices Lifecycle example
https://ddialliance.org/sites/default/files/DDI%203.2%20Best%20Practices_0.pdf

A technical Best Practices in the area of identification, language, and places where there are multiple ways to handle content, to provide a best practice to ensure interoperability on tools and versions. Also of concern is consistency within the community. 

Feedback needed:
--Are there known issues in terms of interoperability?
--At what level are they describing for example specific fields such as CV use or just general? There are certain structures in codebook that are confusing.
--Focus is the point where it affects interoperability - bleed over a bit into content. 

ACTION ITEMS:
--TC draft up questions to collect information
--Top 10 issues
--Content vs Technical

Concern: Far more people using stand alone versions of Codebook than Lifecycle so there is less technical support - what are important to developer and to the user. If we get broader feedback there will be a home for it in high level document.

CONTROLLED VOCABULARIES
Practical problems: 
--Problem with people who use the term and resolve
--People who will only use what is in the metadata no resolution
--Provide content to those who resolve and those who don't
--Mapping between thesaurus' 

Issues activities:
DDICODE-73 Resolved
DDICODE-64 Resolved
DDICODE-68 Resolved
DDICODE-44 Resolved
DDICODE-38 Resolved
DDICODE-51 Agreed on general solution - draft specifics
DDICODE-49 Agreed on general solution - draft specifics

ACTION ITEMS:
--Wendy will draft specifics for DDICODE-49 and -51 and post for approval
--Once approved draft of codebook.xsd will be made available
--Examples will be provided for citation and for controlled vocabulary changes to help verify that intended resolution was achieved
--TC will be responsible for validating technical changes before merging to master copy