Considering a Community Group "Report"

When we started regular meetings in April, I was thinking we'd be able 
to operate this group like a Working Group, quickly getting into the 
details of producing specifications for necessary vocabulary terms.  It 
has turned out there was a lot of other groundwork we needed to cover 
first, more like a typical Community Group. So be it.

So how to capture the work we have been doing?  The usual answer is a 
Community Group Report.

I'm not a big fan of reports.  I don't usually like writing them and I 
don't like reading them.

But, maybe this is an exception.   I took at stab at writing something.  
I'll be very interested to hear what people think of it.  (Some parts 
are more polished than others.) Ideally, we can get it into a version we 
feel comfortable "publishing" as a draft-for-public-review in September, 
before JTI and TPAC.  It doesn't have to be complete or final at that 
point - it can have places that are still marked TBD.

I wrote it as a Google doc, which is a bit easier for me, and has pretty 
nice comment handling.  I also wrote a little program to convert that to 
a normal W3C-style document, for people who don't want to deal with a 
Google doc.  They are both linked from: https://credweb.org/report/

       -- Sandro

Received on Sunday, 26 August 2018 17:10:46 UTC