- From: Tara Athan <taraathan@gmail.com>
- Date: Wed, 3 Feb 2016 12:09:38 -0500
- To: public-rsp@w3.org
- Message-ID: <56B23452.9020801@gmail.com>
On 2/3/16 9:54 AM, Jean Paul Calbimonte wrote: > Hi, > > We have a scheduled call tomorrow at 15:00 CET. Do you really mean tomorrow (Thursday)? I was expecting the call on Friday > > As it was done last time, the skype group will be used: > https://join.skype.com/nRbgWpxbeloT > > As it was decided last time we already moved our two drafts to ReSpec > template, now on github. > > The two deliverables are: > > * RSP Overview document: > http://streamreasoning.github.io/RSP-QL/RSP_Requirements_Design_Document/ > It looks like you copied the editor/author section from the other document. I don't expect to be an author on this document (although I will review and make suggestions). > > * RSP model document: > http://streamreasoning.github.io/RSP-QL/Abstract%20Syntax%20and%20Semantics%20Document/ > > > > In github, this is on the "gh-pages" branch, as it provides a > convenient hosting service if it is located on that special branch. Thanks for setting up this gh-pages branch. The editing and publishing workflow based on respec and gh-pages is quite convenient. > > > For tomorrow, I propose to discuss the general outline, and assign > editing tasks by section. For the Abstract Syntax and Semantics document, I think the authoring team needs to work in a closely coordinated way, since everything is highly inter-related. I think we can identify and assign issues, but the modifications will likely include multiple sections, leading to unavoidable merge conflicts. I would like to use the github issue system to manage this, if the authoring team agrees. Tara > > > Cheers, > Jean-Paul >
Received on Wednesday, 3 February 2016 17:10:11 UTC