- From: bergi <bergi@axolotlfarm.org>
- Date: Sun, 13 Mar 2022 23:16:47 +0100
- To: "Ruben Taelman (UGent-imec)" <Ruben.Taelman@UGent.be>, public-rdfjs <public-rdfjs@w3.org>
Thanks Ruben for pushing this topic. Below would be my proposal for the agenda, including some initial thoughts from my side: - Which steps should we take? - Cleanup the specs or add missing features? - My proposal can be found on Github [1] - Who would participate and is willing to take a specific role? - Time frame and milestones - From my experience, if we agree upon a shorter time frame, there is a higher chance for success, and people stay motivated. - Optional: More technical cleanup vs. missing features discussion. [1] https://github.com/w3c/strategy/issues/102#issuecomment-1036492918 Best, bergi Am 07.03.22 um 10:37 schrieb Ruben Taelman (UGent-imec): > Dear all, > > Recently, W3C asked us about the status of the RDF/JS [1], and the possibility to publish a final report, and perhaps even get started on a REC-track. > > Since there may be some ideas and thoughts about this process by people in the RDF/JS CG, > it might be good to have a call to talk about next steps. > If you would like to join this call, please fill in the following Doodle by Monday March 14: > https://doodle.com/meeting/participate/id/QdJXBZDa/vote > > Feel free to reply to reply to this email thread with your expectations or other suggestions of things we should add to the meeting’s agenda. > > [1] https://github.com/w3c/strategy/issues/102 > > Kind regards, > Ruben Taelman >
Received on Sunday, 13 March 2022 22:17:11 UTC