Re: [Editors] Upcoming Editor's call

Minutes for the meeting (such as they are), are available at https://www.w3.org/2023/02/08-rdf-star-minutes.html. Presumably, they’ll be attached to the meeting page at some point.

Thanks for participating, this seemed to be useful, and we’ll plan to meet again in two weeks.

The outstanding action item is recorded at https://github.com/w3c/rdf-star-wg/issues/16 to better document the process for working with GitHub.

Gregg Kellogg
gregg@greggkellogg.net

> On Feb 7, 2023, at 12:38 PM, Gregg Kellogg <gregg@greggkellogg.net> wrote:
> 
> We have a call scheduled for Wednesday at 18:00 CET/9:00 PST. Pierre-Antoine uploaded the agenda (copied below), but I just wanted to preface this meeting.
> 
> * Introductions, contributions and expectations - roundtable
> * The editor process (see https://github.com/w3c/rdf-star-wg/wiki/Editor%27s-guide)
> * Next steps
> * Next sync : 2 weeks?
> 
> This call is intended to sync up the editing process for the over twenty docs we’re working on with a large number of editors. I’ve created an Editor’s Guide wiki page [1] that would probably be useful to go over before the meeting.
> 
> Consider attending if you signed up to edit one or more documents, need some suggestions to get started using ReSpec and help us set standard style guidelines for consistency across the different specs. There’s far to much to go through in one meeting, but the Wiki is intended to cover the basics.
> 
> I’d like to keep this and future calls informal; we can create actions to report back on, but otherwise not worry about the typical hassles of scribing. But, we will be on IRC, and minutes can be produced from whatever is put there, even if not done as in a typical WG meeting.
> 
> For those new to the role of Editor of W3C Specs, I’ll note this bit about roles at W3C [2]:
> 
> Editors manage documents and their publication. Editors play different roles in different groups, at times reflecting decisions of the group, at other times leading by drafting proposals and responding directly to reviewers. Learn more about the Role of Editor.
> 
> At some point, we’ll need to talk about integrating testing, and having tests for normative statements. The data-tests attribute [3] can be used effectively, which helps when it comes time to transition to be sure we have tests for normative statements. I’ve used this in YAML-LD [4] based on work elsewhere. This creates a Tests detail with references to specific tests for a given normative statement. Tooling can reverse this, so that the HTML version of the test manifest links back to the statement in the spec [5]. This would be onerous to do retrospectively, but we might consider using this for new normative language. It comes in handy when doing transitions and showing that each statement has a corresponding test.
> 
> Lastly, we’ll eventually need to consider what it means to be a "Living Standard”. Phillipe Le Hégret gave a presentation on this at the 2020 TPAC [6] and the 2021 Process Document has a section on revising recommendations [7].
> 
> Gregg Kellogg
> gregg@greggkellogg.net
> 
> [1] https://github.com/w3c/rdf-star-wg/wiki/Editor%27s-guide
> [2] https://www.w3.org/wiki/Guide/Roles
> [3] https://github.com/w3c/respec/wiki/data-tests
> [4] https://json-ld.github.io/yaml-ld/spec/
> [5] https://json-ld.github.io/yaml-ld/tests/basic-manifest.html#cr-well-formed-1-positive
> [6] https://www.w3.org/2020/10/TPAC/w3c_2020_living_standards_and_reviews.html
> [7] https://www.w3.org/2021/Process-20211102/#revising-rec
>