Re: Final CG report publication form is confusing

Hi Ian,

FYI, I love the whole web site setup for CGs. It's really clean and easy and enables us CGers us focus on the work. The only reason I expected publishing to be fully automated is that everything else is! :-)

Two other things, more long term, for when you get to CG/BG website 2.0 (if ever!):

1. GitHub integration: I think the big W3C switch to GitHub happened after CG/BG sites were launched. François made us a posting on our front page to point to our three GitHub repos, with a link to each spec and a link to each issues list. Of course that posting will scroll down. An additional standard area on CG/BG home pages that list the one or more GitHub repositories along with a link to the specs and issues lists would probably become the number one link clicked on CG home pages.

2. IG integration: Having used the CG site for some time, my IG co-editors and I agreed that we wished that IGs were part of this same web home page structure. I think Kaz may have already related that to the team. There's so few IGs, the existing CG/BG web site structure would be fine, rather than a special one. Most things (maybe not all) would work the same across CG/BG/IG.

Thanks,
mav

> On Jan 3, 2018, at 3:31 PM, Ian Jacobs <ij@w3.org> wrote:
> 
> Hi François,
> 
> Thanks for writing up the feedback. I plan to look into these items; just letting you know here.
> 
> Ian
> 
> 
>> On Dec 21, 2017, at 12:25 AM, Francois Daoust <fd@w3.org> wrote:
>> 
>> Hello there,
>> 
>> The Web Media API Community Group just published a final report of the Web Media API Snapshot 2017 specification. Exchanging with Mark Vickers, CG chair, while preparing that publication, we noted that the instructions on the publication form are somewhat misleading:
>> 
>> 1. The description of the "URI of Final Specification" does point out that the report must be published on w3.org, but the existing text makes it sound as if our system will just handle the actual publication itself, and copy the latest version of the draft report somewhere on w3.org. The FAQ is not any clearer. The text should clearly say that the actual publication is a prerequisite to filling out this form, and should provide some guidance for how this can be done (be it only with a "get in touch with your nearest W3C team contact", which may be enough given that most CGs that publish final reports somehow have a connection with someone on the team. Sending an email to site-comments@w3.org could be an option too). That first step will give the URI to enter in the form.
>> 
>> 
>> 2. The use of the term "publishing" is ambiguous. It can mean "copying the doc to a location" and "filling out the form". Typically, the term is used with both meanings in the description:
>> - "Final Reports must be *published* on the W3C web site" (copying the doc)
>> - "Learn more about how to *publish* a report" (filling out the form)
>> The former term could perhaps be replaced by "copying". The latter term could perhaps be replaced by "announcing".
>> 
>> 
>> 3. Looking at the FAQ for possible instructions on how to get a URI on the w3.org domain name, one will bump into "Can I use W3C namespaces in our Specification?":
>> https://www.w3.org/community/about/faq/#can-i-use-w3c-namespaces-in-our-report

>> 
>> This entry states that the URI https://www.w3.org/ns/[shortname] may be used. That will only add to the confusion:
>> - the notion of namespace can be somewhat foreign to "API people"
>> - as such, it reads like an invitation to use that URI for the final report, which is not what we want.
>> 
>> The notion of namespaces could perhaps be clarified by linking to the Namespaces in XML spec that defines what we mean by namespaces, as done in our URIs for W3C Namespaces policy for W3C Technical Reports:
>> https://www.w3.org/2005/07/13-nsuri

>> (although the dependency on "XML" feels a bit outdated nowadays)
>> 
>> Thanks,
>> Francois.
>> 
>> 
> 
> --
> Ian Jacobs <ij@w3.org>
> https://www.w3.org/People/Jacobs/

> Tel: +1 718 260 9447
> 
> 
> 
> 
>

Received on Thursday, 4 January 2018 01:27:36 UTC