Add clarification to description of non-normative deliverables #74
Conversation
Signed-off-by: Brent Zundel <brent.zundel@gmail.com>
brentzundel
changed the title
There was a problem hiding this comment.
It's implied that the reason for doing this is that it's so that we have the ability to create notes as we choose when the WG is happening. However, I believe this is a misguided approach to the purpose of Notes and is actually regressive in terms of patent protection according to the W3C process document Notes section. Most notably Notes are "not intended to be a formal standard" which is not true from my understanding of many of these documents and Notes are not patent protected. I think we either need to actually make many of these documents REC track documents or we need to leave them as CCG reports so that they at least remain protected by the community group patent policy.
You are right for individual notes re patent issues. However... this is not, in my view, a discussion to have here and now. Instead, for each document the WG will have to make a decision whether it intends to work on a specific subject, and that decision will have to take into account the potential patent aspect, too. It is not up to the charter to make this decision, nor can it do it in abstract. As the proposed text says, this list is non-exhaustive, nor is it a requirement to publish these notes. (in fact, if this PR is acceptable, we may think of reducing the list).
What we cannot do easily, during the WG's life, is to decide whether a document would become REC track. Any such decision would require a re-chartering of the group. That decision is to be made now. Whether a document should be a CCG spec instead of a Note is then something the WG will have to decide, weighting the pros and cons of the choice. |
There was a problem hiding this comment.
In the case of what @iherman has said and the discussion on the call today, I believe this is fine.
| Other non-normative documents may be created such as: | ||
| Other non-normative documents may be created as time, attention, and resources permit. The following list is a | ||
| non-exhaustive selection of documents the Working Group may wish to produce as WG Notes or other documents. The Working | ||
| Group will use its discretion to decide which, if any, to work on, and may publish WG Notes or other documents not |
There was a problem hiding this comment.
probably paraphrase
Group will use its discretion to decide which, if any, to work on the documents not listed here.
There was a problem hiding this comment.
made a suggestion in a line above per a comment during VCWG call on 2022-Feb-16th.
|
The issue was discussed in a meeting on 2022-02-16
View the transcript4.2. Add clarification to description of non-normative deliverables (pr vc-wg-charter#74)See github pull request vc-wg-charter#74. Brent Zundel: pull title is Add clarification to description of non-normative deliverables #74. Kyle Den Hartog: unrequesting changes and now approve.. Kristina Yasuda: suggested some text. approved.. Brent Zundel: can merge with your suggestion as a comment.. |
Co-authored-by: Kristina <52878547+Sakurann@users.noreply.github.com>
|
The issue was discussed in a meeting on 2022-02-23
View the transcript4.2. Add clarification to description of non-normative deliverables (pr vc-wg-charter#74)See github pull request vc-wg-charter#74. Manu Sporny: kristina you asked for some changes, do you want you changes applied before we merge?.
Michael Jones: we need to merge 74. Manu Sporny: we are talking about 74. Michael Jones: merge 74. Brent Zundel: did you add kristina's comment?. Manu Sporny: yes. Brent Zundel: objection to mergeng 74?. |
This PR adds text to the non-normative deliverables section clarifying the status of listed items.
Thanks to @jricher for the opening line.
Signed-off-by: Brent Zundel brent.zundel@gmail.com
Preview | Diff