Meeting minutes
VSSo BG Report and FPWD
Daniel: I've prepared three documents for publication, first is a primer explaining what we are defining and why
… you have a core ontology that describes the constructs of VSS and then fuller ontology generated from VSS YAML
… I'm using W3C Respec to facilitate publishing and maintenance and created scripts for generating the spec from ttl
… those changes are in my repo at present, will do a few minor changes and then submit a pull request
<caribou> we should clean up https://
Ted describes plan to publish VSSo as a BG report and FPWD, encourages Daniel to make PR and Carine and Ted can make tweaks
Daniel reminds group of interest to hold a lightweight workshop or webinar. Discussion on bringing in more from W3C SemWeb community and EDM Council
Issues and Pull Requests
Ulf: we have two documents CORE and Transport with various cross references either in general or to specific chapters
… right now it is just by textual mention instead of linked
… one way would be to use links but unsure what is best with respect to future and multiple versions (github.io, w3.org etc)
Ted: for github and github.io they are in the same directory so relative link would work well and wondering if respec has some mechanism
Carine: I think I fixed the links manually at publication time and in respec there is a variable we can probably use to maintain better and will look
https://
https://
Ulf: based on Wonsuk's feedback made a number of minor improvements
https://
… Erik also has been providing feedback
… noticed Respec complains about how I did a reference
Magnus and Carine moved VISSv2 from Melco repo to https://
Ulf: I noticed some significant increase in statistics for those viewing this repo
Paul: any way to find out who?
Adnan: I was working with the team on Beta platform including VISS, we can schedule for next week