Meeting minutes
Meeting minutes: https://
purl for this meeting: https://
DPV 2.0
Version Naming
<ghurlbot> Issue 45 Preserving older versions of DPV and other resources (by coolharsh55)
harsh: the folders and IRIs for versions have been renamed from v1 and v2 to 1.0 and 2.0 following best practices for semantic versioning
<ghurlbot> Issue 133 w3id update for dpv2 (by coolharsh55)
harsh: w3id has been updated with PR by beatrizEsteves, it will go live as soon as it is aproved by the w3id group
Changelog
harsh: We have a changelog for v2 which can be viewed at https://
Search Index
harsh: We have a searcheable index of all concepts from DPV and extensions on a single page - this is the same implementation that was presented earlier but hadn't been merged and updated into the DPV repo. Link is: https://
Miscellaneous
harsh: implemented syntax highlighting for examples in the documents - see examplehttps://
<ghurlbot> Issue 132 Landing page for DPV (by coolharsh55)
harsh: implemented DPV landing page https://
harsh: created a concise version of the primer https://
harsh: OOPS! validation for best practices doesn't show any issues, and FOOPS! validation gives a score of 79% with 2 items to be completed after publishing DPV regarding registering DPV in LOV (Linked Open Vocabularies) service. 2 items are false positives as they relate to not detecting SKOS annotations in OWL ontologies - an issue has been opened about this in FOOPS! github repo oeg-upm/
harsh: various fixes in typos, iris, text (implemented)
julianFlake: should the README that is currently visible at https://
harsh: no, we do not control that url as it is under W3C/Github, and we can replace that with an index.html or redirect but that would mean the README is no longer visible to people who may use the url accidentally.
Diagrams
<ghurlbot> Issue 166 Update diagrams for v2 (by coolharsh55)
harsh: we have implemented everything else in the documents, only the diagrams are left to be updated
julianFlake: we can use UML based diagrams? For example - see diagrams updated in the Primer. UML diagrams will give a consistent look and interpretation as it is a standardised representation of concepts.
harsh: yes, UML is good, and we should have a consistent approach for updating diagrams as the concepts change. Currently the existing diagrams need to be updated as they are incorrect for the latest version
steveHickman: good to use diagrams in a consistent and known representation
paulRyan: merit in UML for long term maintainence
group agreed to go ahead with using UML based diagrams
Release Schedule
harsh: we have two options - 1) We release it right now (with updated diagrams); or 2) We release it as a beta version with a period for feedback and fixing any specific issues found.
paulRyan: pre-release seems pragmatic
group is in agreement about releasing 2.0 as a beta release first with a feedback period until JUL-31. If no major issues are found, we will continue with the final release.
Next meeting
The next meeting will be in 1 week on WED 03 JUL 14:00 WEST / 15:00 CEST. Agenda will be DPV v2.0 beta release and future tasks.