Re: JSON-LD Working Group Charter Approved; Call for Participation

> On Jun 7, 2018, at 11:50 AM, David I. Lehn <dil@lehn.org> wrote:
> 
> On Thu, Jun 7, 2018 at 8:55 AM, Ivan Herman <ivan@w3.org> wrote:
>> If you are part of a member company, you should join right away. If you think of applying for an Invited Experts' position, you should contact the chairs (Rob & Benjamin) and me, and we can then take it from there…
>> ...
>> -------- Forwarded Message --------
>> Subject: JSON-LD Working Group Charter Approved; Call for Participation
>> ...
>> The Director is pleased to announce the approval of the JSON-LD Working
>> Group charter:
>>  https://www.w3.org/2018/03/jsonld-wg-charter.html
>> ...
>> Use this form to join the group; the form will also instruct you how to
>> nominate participants:
>>  https://www.w3.org/2004/01/pp-impl/107714/join
>> ...
>> More information on the JSON-LD Working Group can be found on its homepage:
>>  https://www.w3.org/2018/json-ld-wg/
>> ...
> 
> Hi,
> Can we get an explanation on how we are using various resources going
> forward in the WG?  I understand the idea of using w3c scoped
> resources for this WG, but it's very confusing right now as there is
> duplication of every possible thing.
> 
> email:
> There is public-linked-json and now public-json-ld-wg.  Which topics
> go to which group?

The CG still exists, but is dormant. I will certainly continue to follow public-linked-json@w3.org <mailto:public-linked-json@w3.org>, but WG related emails should go to the appropriate WG list (public-json-ld-wg).

> irc:
> Now there's both freenode and w3c #json-ld channels.  Which is used for what?

The w3c is for WG related discussions, but there’s obviously some overlap.

> specs:
> The github json-ld org had everything.  Now there are a handful of new
> spec and site repos in the w3c org.  What content and issues go where?
> How are we managing all the current issues in the json-ld org?  Are
> these new w3c repos the primary spec sources going forward forever?
> It's a shame to not copy over the spec commit history if so.

We certainly need to discuss this in the WG, but I presume that each spec has it’s own issue list, but we could consolodate and use https://github.com/json-ld-wg/issues <https://github.com/json-ld-wg/issues> for all, which would allow for better cross-linking.

> sites:
> What's supposed to be on the json-ld.org site now?  Are the latest
> spec links supposed to point at w3c repos now?  Or have both CG spec
> links and WG spec links?  Lots of links and info on json-ld.org need
> to be updated so people understand all these resource changes.

Before the CG was reactivated, the “latest” links were sent to w3.org/TR/ <http://w3.org/TR/>, so I suppose we’ll do the same thing, but for the automated Echidna copies, or whatever is common for other WGs.

> test suite:
> Currently tests are in github json-ld group in json-ld.org,
> normalization, and/or tests repos.  Where is all this living going
> forward?

Good question, the WG may want these in it’s space, but they’re a well-known place for people to look at, and were used for the 1.0 docs. So, to be determined.

> post-WG:
> What happens with all the above after the WG is done?

As with the 1.0 effort, the CG should be reactivated. Replaying the commits back into the json-ld.org <http://json-ld.org/> repo may be problematic, as we’ll be loosing the history when moving into the WG repos.

> Did I miss anything?  If someone figures all this out, maybe make a
> checklist of all email, irc, and repos that everyone needs to now join
> and follow.

The WG homepage at https://www.w3.org/2018/json-ld-wg/ <https://www.w3.org/2018/json-ld-wg/> should list everything used by the group.

Gregg

> Thanks.
> 
> -dave
>