[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[open-cobol-list] Access to PL22.4 documents

From: Bill Klein
Subject: [open-cobol-list] Access to PL22.4 documents
Date: Mon, 29 Dec 2008 21:45:31 -0600

to: comp.lang.cobol and OpenCOBOL people

In the past (and as of today), all people (users, vendors, whatever) who
interested in seeing the DETAILS of the work being done by PL22.4
(formerly J4) 
could do so by going to the web-page:

This provided access to such things as "drafts" of the ongoing revision
work and 
details on the specific revision and defect processing that J4 / PL22.4
was (is) 

Due to either a "change in policy" or a "stricter enforcement of what
thought was already the policy", INCITS (the parent of PL22 which is the

Technical Committee that is the parent of PL22.4) is now trying to
the benefits of being a member and/or to limit access to "internal"
documents by 

To read the exact rules (as of today)  of this parent body, go to the
document at:

and look for the section,
  "2.2 Policy Regarding Document Access and Membership Benefits"

The bottom-line (as I see it), is that if you now OR IN THE FUTURE,
think you 
will want to see documents such as those currently posted on the PL22.4
I would suggest that you do one of the following:

A) Join PL22.4 (or get an existing member organization to designate you
as an 
B) Contact the PL22.4 chair at:

    bobkarlin <at>

and request:
  - that he communicate your interest in PL22.4 going to the "public
 - that when PL22.4 does go on that model, that you would like access to
public documents

* * * * *

As usual, if you (like many in these groups) don't care at all about the
COBOL Standardization process, then you need do nothing - and nothing
change for you!

P.S.  Rules are also changing if you think you might ever want to
"visit" a 
PL22.4 meeting.  Contact me off list if you think this might impact you.

P.P.S.  WG4 (the ISO-ish group) has always had more restrictive document
and meeting attendance rules.  These have not changed.)

Bill Klein
 wmklein <at> 

reply via email to

[Prev in Thread] Current Thread [Next in Thread]