Re: Final reports of spec(s) and next steps

Dear all,

Below, you can find the minutes of the meeting that took place yesterday.

Kind regards,
Ruben Taelman

——

# RDF/JS meeting April 13

https://ugent-be.zoom.us/j/96831993369?pwd=a0dPem00TDM0Z2UxeForWlliUGNnZz09


Participants:
- @bergos
- @elf-pavlik
- @pchampin 
- @rubensworks

Goal: Discuss next steps regarding final CG report and REC track? https://github.com/w3c/strategy/issues/102


Agenda:
- @pchampin explains next steps
    - not required
    - rdfjs is already here for a while and stable
    - next step: prepare a charter
    - not just rubber-stamping what has been done
    - REC's can be marked as "[open for new features](https://www.w3.org/2021/Process-20211102/#allow-new-features)", so not frozen as before.
    - WG can create multiple RECs with different scopes, they don't have to be finished at the same time.
- Proposal of @bergos: https://github.com/w3c/strategy/issues/102#issuecomment-1036492918

    - data-model, stream, and dataset (non-experimental part) cleanup and write final report
    - dataset
        - [WebIDL errors](https://github.com/rdfjs/dataset-spec/issues/65)
        - [Remove interface marked experimental](https://github.com/rdfjs/dataset-spec/issues/66)
    - data-model
        - [WebIDL errors](https://github.com/rdfjs/data-model-spec/issues/170)
    - streams
        - [WebIDL errors](https://github.com/rdfjs/stream-spec/issues/20)
        
- ACTION @rubensworks: create new repo on GH (community-group?) with global issue with checklist of what needs to be done before chartering (+send to mailinglist and let people vote on it)
    - share final report stuff on RDF/JS mailinglist, but chartering also other general lists.
- Question: Cleanup the specs or add missing features?
- Question: Finalize spec(s) as-is, and keep (major) changes for the WG?
- Who would participate and is willing to take a specific role?
    - TODO: charter (will require chairs, at least 2, to be determined upfront)
    - Chartering has 2 steps (advance notice to make everyone aware that charter is being worked on; submitted to a vote)
        - Chairs can still be selected after advance notice
- Time frame and milestones _(if we agree upon a shorter time frame, there is a higher chance for success, and people stay motivated)_
    - RC for final reports after one month (mid May)
    - Another month for feedback (mid June)
    - Start chartering in parallel
        - Template: https://github.com/w3c/charter-drafts/blob/gh-pages/charter-template.html

        - ACTION @bergos: create a new dedicated repo for this, but publish under rdf.js.org (@rubensworks will review)
- Optional: More technical cleanup vs. missing features discussion.


> On 15 Mar 2022, at 08:48, Ruben Taelman (UGent-imec) <Ruben.Taelman@ugent.be> wrote:
> 
> Dear all,
> 
> Thanks for filling in the Doodle.
> It looks like April 13 at 18:00 (Brussels time, should be CEST by then) is the best suitable slot.
> Please find the Zoom invite below (requires a Zoom account to join).
> See you all then!
> 
> 
> Agenda: https://hackmd.io/Gi-2Tq_CTM2gZRKqHbzA_A

> 
> 
> Ruben Taelman is inviting you to a scheduled Zoom meeting.
> 
> Topic: RDF/JS: Final reports of spec(s) and next steps
> Time: Apr 13, 2022 06:00 PM Brussels
> 
> Join Zoom Meeting
> https://ugent-be.zoom.us/j/96831993369?pwd=a0dPem00TDM0Z2UxeForWlliUGNnZz09

> 
> Meeting ID: 968 3199 3369
> Passcode: 47LuTzV5
> One tap mobile
> +3225884188,,96831993369# Belgium
> +3227880172,,96831993369# Belgium
> 
> Dial by your location
>        +32 2 588 4188 Belgium
>        +32 2 788 0172 Belgium
>        +32 2 788 0173 Belgium
>        +32 1579 5132 Belgium
>        +32 2 290 9360 Belgium
>        +32 2 585 5574 Belgium
>        +31 20 794 6520 Netherlands
>        +31 20 794 7345 Netherlands
>        +31 707 006 526 Netherlands
>        +31 20 241 0288 Netherlands
>        +31 20 794 0854 Netherlands
>        +31 20 794 6519 Netherlands
>        +33 1 7037 9729 France
>        +33 1 7095 0103 France
>        +33 1 7095 0350 France
>        +33 1 8699 5831 France
>        +33 1 7037 2246 France
>        +44 203 481 5237 United Kingdom
>        +44 203 481 5240 United Kingdom
>        +44 203 901 7895 United Kingdom
>        +44 208 080 6591 United Kingdom
>        +44 208 080 6592 United Kingdom
>        +44 330 088 5830 United Kingdom
>        +44 131 460 1196 United Kingdom
>        +1 346 248 7799 US (Houston)
>        +1 669 900 6833 US (San Jose)
>        +1 929 205 6099 US (New York)
>        +1 253 215 8782 US (Tacoma)
>        +1 301 715 8592 US (Washington DC)
>        +1 312 626 6799 US (Chicago)
> Meeting ID: 968 3199 3369
> Find your local number: https://ugent-be.zoom.us/u/aembihqGeN

> 
> 
> 
> Kind regards,
> Ruben Taelman
> 
>> On 13 Mar 2022, at 23:16, bergi <bergi@axolotlfarm.org> wrote:
>> 
>> 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://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fstrategy%2Fissues%2F102%23issuecomment-1036492918&amp;data=04%7C01%7CRuben.Taelman%40ugent.be%7C92a0379146db416e8beb08da053f5236%7Cd7811cdeecef496c8f91a1786241b99c%7C1%7C0%7C637828067523808062%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&amp;sdata=oQfV9F%2FPFA%2BAC5v3g49OmmCGBNGq31KGzZkZonisaAY%3D&amp;reserved=0

>> 
>> 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://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdoodle.com%2Fmeeting%2Fparticipate%2Fid%2FQdJXBZDa%2Fvote&amp;data=04%7C01%7CRuben.Taelman%40ugent.be%7C92a0379146db416e8beb08da053f5236%7Cd7811cdeecef496c8f91a1786241b99c%7C1%7C0%7C637828067523808062%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&amp;sdata=xPqftbAD%2BQPMgO7Q9XVk1P6RjLGt84ZlriedVtkcq0k%3D&amp;reserved=0

>>> 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://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fstrategy%2Fissues%2F102&amp;data=04%7C01%7CRuben.Taelman%40ugent.be%7C92a0379146db416e8beb08da053f5236%7Cd7811cdeecef496c8f91a1786241b99c%7C1%7C0%7C637828067523808062%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&amp;sdata=2VvZioFP0AbsLXQ9Ti7H7YkEuOQ7VO%2FN9O2Bxk6IyX4%3D&amp;reserved=0

>>> Kind regards,
>>> Ruben Taelman
>> 
> 

Received on Thursday, 14 April 2022 07:10:48 UTC