Is it not also the case that much of the URI is redundant?
It is sufficient to cite, for example:
rather than the more wordy:
to arrive at the same content…
Each artefact seems to have a unique identifier – can we rely on this as a stable identifier in the future?
Sent: Monday, 19 November, 2012 09:10
Cc: Robin Cover; Chet Ensign
Subject: Re: [chairs] How to select and cite public-access URIs versus password-protected URI references
Thanks for bringing this out. It is indeed important; I think there are easier ways (depending on your work style) than the workaround you mention.
Also, one key area that is not directly addressed is meeting agendae. While these are public, and are cited in a TC mailing list, I think it's worth calling agendae out separately.
Often the "related links" is not the best place to select these; the place to find the URIs is under "Documents" in the related links which is a very clumsy interface. If your TC has many documents, there are multiple steps to get the right one(s) (search for
a number greater than your number of documents, and sort)
For agendae or other single use, I use either the link in the posting (which is now always the public link, and on the TC list) or go to the archive, click the "actions" (down arrow) icon, details, and select "public URI for this revision."
In summary there are four ways to get the public URI:
Hand-edit a members link
Go to related links>documents on the TC public page
Use the public URI in the document posting notice (unless you've chosen not to post)
Use the public link from the document archive>Actions>Details>Public URI for this revision
For me #3 and #4 are the easiest and most consistent.
On 11/19/12 11:35 AM, Robin Cover wrote:
Chairs, Editors, TC Members:
This message provides a reminder about the importance of citing
public-access URIs for TC resources, and a simple recipe for
selecting the correct URI references from the TC's online indexes.
A revision to the Naming Directives document  will pressent
the recipe information in a clearer way, but meantime, this
separate reminder may be useful.
In support of the OASIS TC Process rules for public visibility
of all TC resources, TC Members must be careful to select an
appropriate form of a URI reference to ensure that a resource
is indeed publicly accessible from that URI reference. The
member-only (private, password-protected) URI references created
by OASIS [Kavi] tools must not be cited in TC mailing list
messages, Wikis, JIRA tickets, specifications, or in any TC
"documents" that are or may may become public. Such password-protected
URIs frustrate, irritate, and bewilder users who expect OASIS
resources to be publicly available for viewing, but "discover"
(from a cited private URI reference) that the resources are
inaccessible. They may embarrass OASIS from the POV of users
who conclude that the consortium is not transparent/open.
How? While it is possible to manually edit/transform the bad
(private) URIs to create public-access URIs, the simplest way
for TC members to select the public-access URIs is to just
select/copy+paste the URI references from the public-access
indexes as presented on the TC public home page, "Related links"
For example, in the case of the DSS-X TC, here are the
index URIs; just use the "Related links" index information
for your TC or substitute yout TC's shortName for "dss-x"
1) DSS-X TC public home page
See there: "Related links" index URIs
2) DSS-X TC documents
Use the index here:
3) DSS-X TC archived email messages
Use the index here: https://lists.oasis-open.org/archives/dss-x/
4) DSS-X TC ballots
Use the index here:
5) DSS-X TC calender entries
Use the index here:
 Publicly Accessible URIs
 recent discussion on public-access URI references
OASIS, Director of Information Services
Editor, Cover Pages and XML Daily Newslink
Staff bio: http://www.oasis-open.org/who/staff.php#cover
Cover Pages: http://xml.coverpages.org/
Tel: +1 972-296-1783