Congratulations to OCPP TC members for successful launch of the TC, including initial contribution(s).
This memo concerns proper citation of TC assets by URI reference (aka "hyperlinks") to support public access for TC resources. This is important per OASIS rules and ethos -- that all assets be made publicly accessible: documents, email messages, SVN commits, JIRA issues, ballots, ballot results, calendar agendas and minutes, etc.
The memo is is intended mainly for TC Co-Chairs and Secretaries, and for any others who regularly post to the OCPP TC's email list, or create/maintain TC assets. However, it applies equally to all TC members when posting to the TC's discussion list, and when creating any resources that become visible online, whether hosted at OASIS or not.
Succinctly: the Kavi collaboration tools generate hyperlinks (URI references) that are password-protected, and thus are private to OASIS members, making the resources appear inaccessible to non-Mambers. In most cases, Kavi also creates the equivalent public-access (not-password-protected) representations for URIs.
TC Members are asked to be attentive to the difference between "private" and "public" URIs, and to ensure that public-access URIs are always published, even if there is motivation to also cite a private, password-protected URI for some reason (e.g., pointing TC members to an open ballot)
Why be concerned about public URIs? It's about OASIS reputation as "OASIS Open". OASIS policies and best practice guiddlines require that anyone in the world, whether OASIS Member or not, be allowed to track a TC's technical activity via the published resources. If some non-Member discovers or is provided with a password-protected URI, the person (unfamilar with OASIS) may conclude that OASIS is not faithfully keeping its contract with the public, and may silently dismiss OASIS with frustration and annoyance ("feh... OASIS-closed"). With some frequency (we hear in public or on back channels) they will complain about OASIS being "closed - not open -- locking up resources behind password-protected interfaces". So we need to cite the URI references that are "open".
Further explanation is provided here:
Using Appropriate URI References
Thanks!
- Robin Cover
===========
Examples
===========
Examples of public-access (versus private-access, password-protected are provided below. In most cases,
if you use the TC's public-access "index" page, the correct public-access URI for
any resources will be visible. One needs just select-copy the URI from the public
"index" document and paste it into a document or email message.
* Home Page
* Kavi Documents
Other examples for Kavi documents:
Public URIs:
Private URIs (corresponding to "Public" above):
* Email messages
* TC ballot listing
* TC calendar entry
* TC Member Listing
--