Meeting minutes
Meeting minutes: https://
purl for this meeting: https://
DPV v2 reviewing
Fixes
harsh: added various fixes for typos in terms, labels, and descriptions. Found out that in the future we can do these right in Google Sheets by using spell check on specific fields.
harsh: For metadata, there are SHACL validation tests (see script 290) that look for missing terms e.g. if Purpose has a typo as Prpse then an error will be flagged that concept Prpse doesn't exist.
For typos in other documents e.g. HTML or otherwise, people can review and report them until Friday.
versioned IRIs
harsh: following last week's discussion, tried having versioned IRIs by creating two folders for v1.0 and v2.0 representing the two versions. See https://
harsh: the primer, guides, examples, etc. are not moved to the versioned folder as they won't change a lot across the version, and in any case the W3C publishing process keeps versioned copies of HTML reports online
harsh: The IRIs in the folders reflect the version, e.g. the v1.0 IRI now say https://
harsh: for now, I have copied over the media folder from root to v2.0 so there is duplicacy here - going ahead each version will keep its own diagrams and primer etc. will link to that
harsh: for managing versions in the future, the vocab_management script has a variable for indicating the version across all files being generated
everyone to review this by Friday to see if there are any important breaking changes in the versioned IRIs implementation
diagrams
The diagrams need to be reviewed and updated where needed. Harsh and Julian has volunteered to help with this.
w3id update
Beatriz will help with this. W3id needs to be updated to support v1 and v2 versioned IRIs and links.
Risk consequences
harsh: tried to implement the discussion from last week where we discussed removing consequence and impact taxonomy and moving all concepts under Risk. The rationale for this is that concepts such as the example of Misuse mentioned by Delaram can be risk source or consequence depending on the use-case. So to permit this, we shouldn't declare a concept to always be a consequence or impact. Benefits etc. are impacts but are not 'risks' as we limit risks to negative events.
discussed on whether to continue with this for v2.0 or to revert and take this up next time
Next meeting
The next meeting will be in 1 week on WED 26 JUN 14:00 WEST / 15:00 CEST. Agenda will be on deciding DPV v2.0 release. If we are okay with the concent - we will go ahead with publishing v2.0. Otherwise, we will publish but call it v2.0-beta and allow some time (e.g. 1 month) time for comments and feedback.