| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
Dear SEC, I happen to disagree with Bob and Pat.
For those intimately familiar with the structure, topics and projects of 802 using tools such as the PAR database are helpful. Similarly for those who have time
to invest in using the tools for their personal research. For the other 400,000 IEEE members and friends of the family that is not true and having a single consolidated list is very helpful – even if there are occasionally
a few errors to be cleaned up. So, I’d ask that you consider the world outside 802 when deciding how to maintain, or whether to keep at all, the 802 project database – and of course, I believe
you should keep it even if there need to be disclaimers and pointers to more official resources. Bruce From: ***** IEEE 802 Executive Committee List ***** [mailto:STDS-802-SEC@ieee.org]
On Behalf Of Pat (Patricia) Thaler John,
I tend to agree with Bob on this.
What is the driving need for doing this? Can it be met by just using MyProject?
If not, how much is needed to fill the gap? For example something much lighter weight listing current status of active projects might be interesting because that isn’t entirely covered in the PAR Standard
report. Se for example the “Sanity check” slide of the 802.1 closing plenary slides (page 14):
file:///C:/Users/pthaler/802/8021/minutes/2015-03-closing-plenary-slides.pdf That lists project number, subject, stage, current draft #, Next action and PAR end date (to keep track of whether a PAR extension may be needed). It is very handy for seeing where the projects are – especially as they proceed through pre-Sponsor ballot stages.
Regards, Pat From: ***** IEEE 802 Executive Committee List ***** [mailto:STDS-802-SEC@ieee.org]
On Behalf Of ROBERT GROW John: I have to question the wisdom in creating a separate database of standards and projects when those two lists are easily accessed in myProject. The only thing I observe you have included that isn’t in the PAR/Standard Report is the amendments
that are part of a revision. If we want to make the information available on our web site, it should simply be a copy of what is in myProject, not a separate database. Having noted that, I would note the following discrepancies on 802.1 and 802.3: P802.1AB revision no on your list P802.1Qca amendment not on your list P802.1ASbt since it is withdrawn, it shouldn’t be on your list, it isn’t an active project P802.3bw you have listed as a new standard, it is an amendment You noted RAC Required on Std 802, but not on other projects (the RAC is a mandatory coordination for any standard and RAC review is triggered by the PAR, by MEC or by RAC request so I find no value in that additional information). —Bob On Jul 6, 2015, at 8:21 AM, Benjamin A. Rolfe <ben@BLINDCREEK.COM> wrote: A couple corrections I found: On 7/6/2015 7:33 AM, John_DAmbrosia@dell.com wrote:
---------- This email is sent from the 802 Executive Committee email reflector. This list is maintained by Listserv.
---------- This email is sent from the 802 Executive Committee email reflector. This list is maintained by Listserv.
|