[802SEC] +++ LMSC P&P Revision Straw Poll+++ Editorial
I want to take a straw poll, but first a reminder:
There will be a teleconference this Thursday (2/19/06) at 12 PM EST to
discuss the 'Editorial' P&P revision. I will be on the road again, but
will attempt to have a webex up and running. I'll provide details later
Should we replace existing occurrences of the term 'WG/TAG'
The biggest issue raised on the editorial ballot was the question of
using WG as opposed to WG/TAG in the P&P. Sometimes we use WG, and
sometimes we use 'WG/TAG'. A couple of folks objected to my suggestion
of uniformly using WG rather than sometimes using WG/TAG. The general
objection was that ambiguities might creep in.
My problem is that there are already a very large number of uses of
'Working Group' to refer to a WG/TAG in the existing P&P. To 'clean'
all that up would be a very large task and I think will greatly clutter
the P&P. Some of the subclauses I feel currently suffer from these
ambiguities are: 126.96.36.199 (letter e and g) 8.1.1 9.1, 10.1, 14.1.2.
Interesting while most of 7.2 uses only WG subcluase 188.8.131.52 use WG/TAG
and sometimes just WG. This is not an exhaustive list, just some of the
place that might currently be considered ambiguous.
So, I wish to first draw attention to the following line for Subclause
7.3 'LMSC Technical Advisory Groups (TAGs)'
"The TAGs operate under the same rules as the Working
Groups, with the following exceptions:"
The text then goes on to identify a bunch of exceptions. It is possible
that through time additional exceptions might have been identified
elsewhere in the P&P (I'd prefer that we collect them all in 7.3 if
others exist). But fundamentally, this subclause says that any rule
that applies to a WG (not explicitly called out as an exception in this
clause of the P&P) also applies for a TAG. As such, I'd prefer to
define things in the P&P as explicitly for a WG and implicitly for a
TAG. If there are exceptions, they should really be called out in 7.3.
I want to see if I have enough support to pass a ballot on this before I
invest the effort in it.
Please review some of the subclauses I've identified for ambiguous use
of the terms and comment on my straw poll. If you prefer an alternate
resolution please provide it.
Matthew Sherman, Ph.D.
Senior Member Technical Staff
BAE SYSTEMS, CNIR
Office: +1 973.633.6344
This email is sent from the 802 Executive Committee email reflector. This list is maintained by Listserv.