You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm going to agree with @dontcallmedom and disagree with @plehegar because a related term does in fact come from the Process:
The title, stable URL, and publication date of the document that was used as the basis for its most recent Exclusion Opportunity as per the W3C Patent Policy [PATENT-POLICY]. (labeled “Exclusion Draft”);)
Process needs to update to say something like "Exclusion Document" and then we can change "Draft State" to "Dcoument State" in the charter template.
The term exclusion draft may one day serve as a hook for extensions / refinements to the patent policy, but is currently not used by it, so we could rename it if we found it useful to do so.
Exclusion opportunities are called on non-finalized documents. FPWDs, CRs, the combination of a REC with some proposed corrections… All these are arguably, in some form or other, drafts. There may be a REC published after the Draft on which the exclusion was run (and its normative content should be identical), but the Exclusion Draft being "the document that was used as the basis for its most recent Exclusion Opportunity as per the W3C Patent Policy", it is not a REC.
They're also documents, so I don't think I'd object to the renaming, but I am unconvinced it is necessary.
However, "Adopted Draft" may indeed refer to non-draft things, as the adopted document by be a REC. I think that's the one that would be worth considering to rename to "Adopted Document" or something along these lines.
I'm going to agree with @dontcallmedom and disagree with @plehegar because a related term does in fact come from the Process:
Process needs to update to say something like "Exclusion Document" and then we can change "Draft State" to "Dcoument State" in the charter template.
Originally posted by @svgeesus in w3c/charter-drafts#627 (comment)
The text was updated successfully, but these errors were encountered: