Date: Thu, 28 Mar 2024 21:07:18 +0000 (UTC) Message-ID: <88077080.43.1711660038507@bcb5fc83a2b5> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_42_1856466903.1711660038507" ------=_Part_42_1856466903.1711660038507 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
2022-2023 Minutes Page, 2020-2021 Minutes Page, 2018-2019 Minutes Page= , 2016-2017 Minutes Page, Pre-2016 Minutes Page
ATTENDEES: Wendy, Jon, Oliver, Darren, Dan
A=
POLOGIES: Flavio
1-Codebook pull request
ok and merged
2-Funding requests (Deadline is 26 of April)
Face-to-Face again
Infrastructure costs - flag and could suggest it should be a regular bud= get line; software contingency budget as well as on-going costs
10K last year was infrastructure contingency from which a couple of mont= hs of AWS
Alliance pays Colectica and this will move to AWS at some point
As part of the move to AWS a bit of work needs to be done to convert from z=
one file to AWS (route 53) - Dan will write up
Admin data meeting - talk to Flavio about meeting next year; funding req= uest
3-Strategic Plan
Looks good - no questions or specific concerns from TC members at meeting=
p>
4-Administrative documents
Not ready for discussion
5-CDI submission to TC and production process review
Darren talked with Arofan about RDF URLs and everything is in line
Other:
CV work is done ready to make the change after confirming a few minor po=
ints with ICPSR and the CV group
https://ddicv.ukdataarchive.co.uk/ new format for the CV page (do=
main to be changed obviously)
No ISI proposal but will look at the IAOS conferences coming up
FUTURE:
No Oliver until April 18
No meeting on 11th due to COSMOS conflict
ATTENDEES: Wendy, Dan, Oliver, Darren, Christophe
AGENDA
Resolution system
CV system
Access to https=
://github.com/ddialliance/ddi-cv-platform (am hoping that Oliver will b=
e at TC tomorrow).
All is in hand
Misalignment of version numbers in https://github.com/ddialliance/ddi-cv - logged at https://github.co= m/ddialliance/ddi-cv-platform/issues/1
This has been resolved, however there is a problem with the resolving th= e old version numbers x.x rather than x.x.x
They will check with CESSDA after talking to Sanda identify where the pr= oblem is in terms of inaccurate extensions
RDF hosting/resolution
RDF hosting/resolution for CDI (upcoming) is not a dependent on the CESS= DA CV version issue being fixed.
DB will contact Arofan to clarify CDI RDF serialization=E2=80=99s readin= ess and double-check required URI patterns for CDI
All CVs have unique URIs based on version numbers and are stored in Fuse= ki default graph. For non-CV products e.g. CDI or DDI4 (that don=E2= =80=99t necessarily have versioned URIs) we will create individual graphs f= or each product.
Codebook pull request review
OK and merged
4.0 BETA issues - Comments also added to issue discussion in Git= Hub
Item 8
Changing from internal CV to external could be a Lifecycle 4.1 task
<= /li>Identify those that could be CV
Add enumeration documentation to the item type
Group ones should probably be taken over by CV group
Dan will look through to make sure enumerations are coming through corre= ctly - OWL specs may require URIs for enumerations (this would be an issue = for next round of review - how referenced
Wendy will look at CV options now. Darren can look at later. This is not= urgent.
Adding documentation on lists that are currently there. Create notes of = what should be added to each README file.
Item 23
Not critical in short term. Good to get multiple eyes on this.
Item 36
Should be addressed in 4.0 BETA 2
Add additional notes on previous discussions
Group instances to see what could be managed in the same way
FUTURE
Administrative documents (Jon) as available (Jon not on call)
ATTENDEES: Wendy, Dan, Flavio
POST-MEETING W=
RAPUP (due to forgetting US change to DST): Jon, Darren, Oliver, C=
hristophe
Review of approach to issues 8, 23, and 32:
Issue 8: (spreadsheet has been added to issue)
Identify good canditates for conrolled vocabulary
Group itesm need either documentation of definitions of types or use a c= ontrolled vocabulary. This is true of internal enumerations currently conta= ining documentation.
Issue 23: (spreadsheet has been added to issue)
When versionables reference other versionables looking for order needs -= assigning of contents is required or used
DISCUSSION: How explicit order gets injected - clearly =
needed in some serializations but XML has two camps (order implied, order n=
ot implied)
First step is identifying where order is needed
Additional Topics:
ISI presentation:
ISI do we want to propose something on DDI like last year in Ottawa?
Does TC want to send something - IPS
We have 3 weeks - kick around an idea for a topic
Something beyond use cases
Parts of DDI - multiple serializations
How content fits together and can move between products
3-4 people with or without discussant
XKOS:
Best Practice ready to go so look for email on that
ATTENDEES: Wendy, Jon, Oliver, Dan, Jeremy, Darren, Fla= vio, Christophe
Codebook
Pull request has been amended and content is now correct
Looking forward, the concept/conceptualText will be posted immediately f= ollowing the resolution of the current pull request
This will be followed by the remaining issues which are more targeted
ACTION ITEM:
Dan will note items that are NOT documentation change so they can be review=
ed next week
DDI-L 4.0 Beta 1 Issues
Another beta the middle or end of April after gathering COSMOS feedback<= /p>
An issue on representing sentinel variable values in Represented Variabl= e
All new content issues should go into GitHub. They will be tagged for re= leases.
This will also allow broader discussion of content issues in clearer way= than we have been able to do before.
ACTION ITEMS:
Wendy:
#36 - go back and pull together the earlier discussion of dealing with exte=
nded reference and review current need for continued use of this content
#8 - review enumerations as converted to CSV and conversion to outputs
#23 - locations of ordered attributes
Jon:
Administrative documents - add content on #16, #17, #30, #31, #32, #33, #34=
ATTENDEES: Wendy, Jon, Oliver, Darren, ChristopheAPPOLOGIES: Dan, Flavio
Webinar review
A lot of people who we seldom or never seen
Good suggestion:
Guidance on pull requests
We can set up templates
Contributors guidance document
Missing documents
What is the model
Master?
Development version
In terms of code the past published specifications can be compared
= li>Between 3.2 and 3.3 we could do a dif but we can't track between 3.3 and= 4.0 because each generation is structurally different (dependent on mappin= g and change documentation)
The ability to track individual changes
How do we want to do this? If we publish 4.0 as a package
Track each time only model changes not differences in different serializ= ations
We could do this locally [there will be so many structural changes a dif= won=E2=80=99t work]
At the moment published versions are in Bitbucket so we need a separate = repository to hold published versions in GitHub to replace this
Jon has started adding files (citation, license, contribution guidance, = form for contributions
One issue about having a missing license file we use cc-by [Note that th= e Alliance has determined that this is the license to be used by all produc= ts. We will need to check license on production programs (cc-by was not on = the list of options]
Document how things move through approval and that people can build on t= heir own branch
There is a GitHub project called DDI-CDI and DDI-CDI-resources
Needs to be on DDI Alliance set of repositories
There is no governance on the Alliance site
ACTION: Jon will start drafting governance documents
Status on CV and pipeline
We have Simon George booked on 17-18th
Can we have a repository for DDI-CV-platform (have DDI-CV-publishing)
Public
https://github.com/orgs/=
ddialliance/repositories?type=3Dall
Promo from Postman
Codebook
Pull request for ddi-c_2
https://github.com/ddialliance/ddi-c_2
Note that the first ff3481b is bogus. It is the second commit 0cce353 that =
contains the documentation changes to codebook.xsd
How to process through these?
People could put in comments in before next meeting for the documentatio= n
The documentation content and the next (Concept/ConceptualText) are larg= e. Some review should take place outside of meeting and then deal with ques= tionable areas with group. Future edits should be more localized.
Oliver will check to see if there is a clear way to correct and entry er= ror (alt is to reject pull request, kill this Fork and start over)
NEXT WEEK:
Codebook - Documentation review
FUTURE AGENDA ITEMS (as ready):
GitHub administration and guidance
Publication repository on Bitbucket - options/plan
ATTENDEES: Wendy, Jon, Darren, Flavio, Christophe, Jare=
d (guest)
APOLOGIES: Dan
GitHub:
Darren contacted Jared about AWS account and he needs clarification
<= /li>Background:
Trying to detach those things that are difficult to do with ICPSR infras= tructure (underlying databases for examples, etc.; field level documentatio= n; XML schema; etc.)
Set up AWS instances where these can be held
example: DDI Lifecycle model generates a lot of output and AWS is a solu= tion
Separate web site for documentation and links to sources (docs.ddi= aaliance.org)
Automation of creation pipeline of CV content from CESSDA output
Currently we have 5 or 6 administrators already on GitHub - so we can ma= nage rights for individuals
ACTIONS:
Need to set up an account on AWS so that we can begin organizing this
Jared needs to set up the account with appropriate permissions
Darren will ask Michael for the DNS zones
Wendy and Jon will create a list of items that might move from ICPSR to = this new site
Clarification of document repository approach
CDI will have a place to run their infrastructure
Outputs will go on AWS
ACTIONS:
Build a spreadsheet of where things are
Start a TC ticket and add Darren as a watcher on that
DDI-L 4.0 BETA review of webinar
Jon has done slides
In middle of the webinar Jon would like to demo a change on a fork and g= enerate
35-40 people are attending
This is a BETA and there are already errors which need correction
Public review in summer at the earliest
Questions regarding spreadsheet
Specific example:
The blue items on the spreadsheet are only removals
Some are serialization specific and therefore need to be documented
<= /li>ACTIONS:
Add to key meaning of a,e,b in 3.3 column
Finish sumamry of purpose of moving to Version 4.0 / use of COGS
Get these posted and link information to Jon so he can add to slides (by= Friday)
What is the current status of CDI - finalizing documentation review chec= king images, Arofan is wrapping up the documentation and pulling together= p>
XKOS update:
XKOS best practices document almost finished integration of issues - pro= bably out before COSMOS, maybe next week
They will create an announcement and we can get this out and posted on t= he web page
ATTENDEES: Wendy, Jon, Darren, Dan, Oliver, Jeremy
<=
strong>APOLOGIES: Flavio
Infrastructure:
Set up account - and we need someone to work with Jared
In terms of setting up environment - need someone - Darren is willing to do=
set up
Getting permissions to the right people
Contact Olof and look for a person to follow-up and manage over time
Apache server serving a static site
Separate containers for different things - keep it simple
cover docs.ddialliance.org instances
AWS issue:
Darren - we can get Simon 2 weeks in March 11-18th) to get the CV set up at=
UKDA
Moving pipeline off Bitbucket to GitHub: Oliver has already moved it to Git=
Hub and Oliver will send URL of repository
https://github.com/ddialliance/ddi-cv
The creation of repo content is still manual but should be turned into a pi=
peline in the nexts
Sanda can check out the html specifications. Pascal can also do checks
Webinar
Spreadsheet 3.3 to 4.0 - post for TC and webinar support
Jon has updated the presentation outline based on TC comments
Add Demo of COGS showing how easy it is to make changes and then generate t=
heir content for testing
Members planning to attend need to register
FUTURE AGENDA:
Next week: review of=
webinar in prep
Two weeks: Check in on CV, RDF, and re=
po pipeline - sanity check
ATTENDEES: Wendy, Dan, Jeremy, Flavio, Oliver
APLOGIES: Jon
DDI-L 4.0 BETA webinar
As of last Friday, we had 35 sign-ups.
Draft of short presentation contents
https://docs.google.com/document/d/1jeqDxr_4P3HM-oeW4j-g-WYr3aAKQeUwNooyi=
lgGWbY/edit?usp=3Dsharing
See document for comments
AWS set up
TC budget for AWS has been approved, so we need to get moving on setting=
up an account, presumably we need to get Jared to put the Alliance down to=
pay that.
Uses funding requested this year for infrastructure support. Next fiscal ye=
ar this should be proposed as a new permanent budget line for association.<=
/p>
Talk to Darren and/or Olof about taking this on to get set up.
Regarding cloud deployment. Whoever sets it up we should management deploym=
ent using build scripts. The CV stuff is set up this way and there is somet=
hing to start with.
We will need to add in things on the documentation. See how long Jared woul=
d need to set up the account. Be clear what needs to get done prior to sett=
ing up the cloud space and moving things into it.
Product Page
Implications for how the content is made available on the download and d=
oc site for each product
Currently use docflex for the Field level documentation of the XML. Should =
this be continued with the COGS product. XML specific documentation as well=
as language specific documentation need for field level documentation.
Can we add to the doc site (links to specific output documentation)
A revised example will be made based on comments. Follow with examples o= f transfer of all product pages.
ATTENDEES: Wendy, Jon, Dan, Oliver, Christophe
DDI Lifecycle 4.0 BETA webinar
Went out on DDI Users Group and some socials
Put a reminder out 2 weeks before event
Check with Jared on numbers
Jon will draft up something for next week
DDI infrastructure proposal
Has contacted relevant working groups
CV XKOS and SDTL are fine
CDI group ok; some longer term issues that can be addressed as they come= up in terms of production line
Add some statement about governance around GitHub
Can start setting up landing page for development work so we can inform = people
Atlassian
Some worries
Many people are moving off it and this could cause the loss of open sour= ce support (due to lack of paying customers)
We have moved off in terms of Bitbucket
But we still have JIRA and Confluence
Clean up JIRA in the next year to drop unused and archive old issue trac= kers
Consider free support services we use to develop contingency plan across= the board
NEXT WEEK:
Product page mockup
Draft of 4.0 BETA webinar content
Administrative Data possibility of moving to next fiscal year
ATTENDEES: Wendy, Jon, Dan, Oliver, Flavio
Discuss page change drafts for products (TC-242, TC-243=
, TC-244)
Product Page list of versions OK Get this done first as this resolves th= e Google reference issue
The page of links for filing issues and how-to page are a good idea
<= /li>Product version page revision is a good first step by pushing critical i= nformation to the top and making it visible on the initial screen. Continue= to revise based on information from developers/implementers and prepare up= dated draft along with an example from Lifecycle. These need to get updated= prior to publication of CDI, new Codebook 2.6, and DDI Lifecycle 4.0.
<= /li>Issue to address in future: Current download packages are now served by = an on-site (ICPSR) copy of the product and XML is provided for validation p= urposes through the ICPSR site. How should this change with multiple serial= izations (XML, RDF, JSON, UML-XMI, etc.)? The Bitbucket repository of publi= shed products currently serves as an archive and is not linked to the produ= ct pages consistently.
Organization and ongoing management of GitHub content This was just a heads-up on the type of information TC needs to organize re= garding GitHub space. It is primarily management information (Guidelines fo= r development groups and users, tooling pipelines, space management, constr= aints regarding triggers for moving from free to fee based services, etc.).= This is still in a period where we are obtaining comment. These notes from= the CDI meeting will be more formally organized and provided in writing by= CDI. The Scientific Board is aware of this work and is primarily monitorin= g the process to ensure input from development groups affected by the shift= to GitHub.
TC pages under Learn dropdown on Alliance site
R=
esources:
We need to look at how examples, tools, and profiles are managed and organi=
zed in the new system. We will no longer have the on-site option of underly=
ing databases. Primary decision is which, if any, of these should be manage=
d off-site.
Getting Started:
See TC-245 for collecting information on determining the purpose of this pa=
ge, what information should be provided, and how to present it. Members wer=
e asked to think about these issues and add comments to the issue so that w=
e can move on revising this page in cooperation with the Training Group and=
probably future Marketing Group. This should be a priority. Jon will talk =
with Training leaders to get their initial thoughts.
NEXT WEEK:
Webinar for 4.0 Beta
No meeting was held. The following is the information s= ent out to the group for their attention and action:
TC issue tracker
I have reviewed and updated all entries
In particular see TC-242, TC-243, and TC-244 and add comments regarding lay=
outs provided in attachments
Use filter TC-outstanding to filter out completed issues
Notes from DDI-CDI meeting on 2024-01-17
Comments about Git repository raised during CDI meeting on 2024-01-17 - =
note that Achim was not present so there will be more
Git repository management - how does TC support product groups in this?
Guidelines
Informational materials
Help identify persons if group is unable to provide this
Deirdre is willing to be involved as setting this up
Back-up people
Git repository
Tools/workflows
Organizing BETA access, support repository, policy, pull requests
Coordinate how to organize
Working with input from outside of the group (developers work)
Making clear what things are
Granularity of pull requests (issue based)
Branching - readme on how to do this, what is supported
Pricing models for AWS (space is not the issue, but deploying own servers/=
code base)
Each product needs to provide a canonical expression of the product
CDI is the UML model expressed as canonical XMI
Each product needs to be clear on this - how to visualize the model in the=
case of COGS base
Canonical model has to be publicly distributed
ATTENDEES: Wendy, Jon, Dan, Jeremy, Flavio, Oliver
Update on CDI work
Variable Cascade issues - providing guidance through webinars, documenta= tion (it appeared there weren't direct predicates linking along the chain, = appeared there were just a single predicate used for different relationship= s)
Will this require additional review?
Topics for future webinars
Why are there various ways in dealing with the same content across produ= cts (classification/codelists etc)
DDI-L 4.0 BETA review
Supplemental content - changes in the content model; why and what was do= ne; update DDI Lifecycle Best Practices (how to use some of the schema stru= ctures to address 4.0 in addition to 3.x best practices)
Updating model - just raising issues and modifying at the end
EDDI session on priorities
Nothing specific struck a cord in terms of TC
Follow-up on - web pages and webinar with Jared
Wendy has recieved comments on pages
Jared has responded to Jon who will make arrangements for webinar on 4.0= BETA
ATTENDEES: Wendy, Jon, Dan, Jeremy, Flavio
Webinar of some description
Q&A - Highlight of why we moved to this and how they can interract wit=
h it
or Anticipation - presentation
Q&A seems best approach
A bit of introduction to version 4.0 (about 5 minutes)
Back end of February would be good timing
Discussion pieces out from mid-Jan to mid-Feb: get a list together and s= ee what is important to front-end
3:00 UK (10 eastern, 9 central) - 21st or 28th of Feb (Jon will follow-u= p on this)
It's about a small group zoom with google form for registration
We've only really asked about OWL serializations
Do we want something more on the model conceptualization?
On the serialization things?
Model is the same as 3.3 with only changes made to so only specific chan= ges for choice and physical description
ACTIVITY: (Wendy review and create list) pull discussio=
n pieces together, clean up, post, and send links
Roll out discussion pieces.
Product pages on Alliance Site
Overview of products page can be updated but is in good shape overall
ht=
tps://ddialliance.org/products/overview-of-current-products
Product pages:
Less wordy
More prominence for the access to the html documentation
Update links
Setting up pages that were held off the site (determine what should be o= ff site support - RDF resolution
All of the products have autogenerated documentation - move to a docs.do= cumentation site and link from the main pages
Examples, tools, etc are candidates for moving off-site
Get comments from Jared (contact him for what feedback he's gotten)
<= /li>