Re: [admin] Publication Rules [Was Re: Call for Consensus: CORS to Candidate Recommendation]

[Glenn Adams]

Unless I've missed it, I don't believe the #PubRules provides guidelines on
what documents are referenced by a spec and whether the reference is
normative or non-normative. If I'm wrong, please point out the policy or
pubrules text that addresses this issue.

Just to be clear, I don't object to including a non-normative reference to
the WHATWG variant specification; however, if it is to be a normative
reference, I'd like to insist it be the official W3C document that is
referenced.

On Fri, Nov 16, 2012 at 7:14 AM, Arthur Barstow wrote:

> The W3C's process documents (e.g. #PubRules) define the policies for
> publications and this issue will be addressed if/when the CR is actually
> published.
>
> WebApps is simply a user of the publication policy. If you want to discuss
> W3C processes such as PubRules, please use some other list - and not any of
> WebApps' lists - such as public-w3cprocess #ProcCG.
>
> -Thanks, AB
>
> #PubRules 
> 
> >
> #ProcCG 
> 
> >
>
> On 11/16/12 8:51 AM, ext Ms2ger wrote:
>
>> I object to making such a change.
>>
>> On 11/16/2012 02:32 PM, Glenn Adams wrote:
>>
>>> Before going to CR, I believe the [HTML] entry in the references section
>>> needs to be changed to reference an appropriate W3C specification. A
>>> present, it reference a non-W3C document.
>>>
>>
>

[admin] Publication Rules [Was Re: Call for Consensus: CORS to Candidate Recommendation]

[Arthur Barstow]

The W3C's process documents (e.g. #PubRules) define the policies for 
publications and this issue will be addressed if/when the CR is actually 
published.


WebApps is simply a user of the publication policy. If you want to 
discuss W3C processes such as PubRules, please use some other list - and 
not any of WebApps' lists - such as public-w3cprocess #ProcCG.


-Thanks, AB

#PubRules 
#ProcCG 

On 11/16/12 8:51 AM, ext Ms2ger wrote:

I object to making such a change.

On 11/16/2012 02:32 PM, Glenn Adams wrote:

Before going to CR, I believe the [HTML] entry in the references section
needs to be changed to reference an appropriate W3C specification. A
present, it reference a non-W3C document.