feat: add scope of work

swicg / potential-charters

Discussion of potential CG and WG charters

2 stars 6 forks source link

feat: add scope of work #22

Open evanp opened 2 weeks ago

evanp commented 2 weeks ago

I added what I think is a minimal scope of work:

maintaining the outputs of the WG
document integrations with other parts of the stack
create extensions
educate implementers
contact point for other standards groups

I'd recommend merging this PR and making additional changes afterwards.

Closes #16

evanp commented 2 weeks ago

This is for #16

evanp commented 2 weeks ago

OK, I changed "editor's drafts" to "corrected drafts", per @gobengo 's request.

I want to note that we have multiple group resolutions to maintain an "editor's draft". As long as we understand the equivalence, I'm OK with the change.

https://github.com/swicg/meetings/blob/main/RESOLUTIONS.md

bumblefudge commented 2 weeks ago

Perhaps the solution to ^this knock-on problem is to mention it during today's call... and take a resolution to start calling them "Corrected drafts" going forward (which will thus appear in the list of Resolutions when the meeting gets minuted😄

evanp commented 1 week ago

I don't agree with the modification to the language around the OWL ontology. Although it is non-normative, it is one of the published outputs from the WG and needs maintenance, just like the others.

https://www.w3.org/TR/activitystreams-vocabulary/#non-normative-ontology-definition