[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [chairs] How to select and cite public-access URIs versus password-protected URI references
Thanks, Bill. I'll review your comments on strategy for "calling agendae out separately". Indeed, there are several anomalies and edge cases that I deliberately overlooked: I wanted to document a simple, general approach that will work for all four common types of resources and their URI references (not just documents): - Kavi documents - archived TC general discussion list email messages - TC ballots - TC calendar entries Note that the same general approach ("Related links" indexes from the TC public page) also works for locating the indes for TC comment list postings sub Comments Archive Unfortunately, in some cases, it appears impossible to locate/craft a public-access URI, given current Kavi implementation + configuration. It is possible for the four most common use cases. Bill, thanks for your diligence and attentiveness to the issue in TCs where you participate. Cheers, all. - Robin Robin Cover OASIS, Director of Information Services Editor, Cover Pages and XML Daily Newslink Email: robin@oasis-open.org Staff bio: http://www.oasis-open.org/who/staff.php#cover Cover Pages: http://xml.coverpages.org/ Newsletter: http://xml.coverpages.org/newsletterArchive.html Tel: +1 972-296-1783 On Mon, 19 Nov 2012, William Cox wrote:
Robin - 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: 1. Hand-edit a members link 2. Go to related links>documents on the TC public page 3. Use the public URI in the document posting notice (unless you've chosen not to post) 4. 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. bill -- William Cox Email: wtcox@CoxSoftwareArchitects.com Web: http://www.CoxSoftwareArchitects.com +1 862 485 3696 mobile +1 908 277 3460 fax 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 [1] 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 Use: http://www.oasis-open.org/committees/dss-x/ See there: "Related links" index URIs 2) DSS-X TC documents Use the index here: https://www.oasis-open.org/committees/documents.php?wg_abbrev=dss-x E.g., https://www.oasis-open.org/committees/download.php/47439/localsig-v1.0-wd01-8Nov2012.pdf 3) DSS-X TC archived email messages Use the index here: https://lists.oasis-open.org/archives/dss-x/ E.g., https://lists.oasis-open.org/archives/dss-x/201211/msg00026.html 4) DSS-X TC ballots Use the index here: https://www.oasis-open.org/committees/ballots.php?wg_abbrev=dss-x E.g., https://www.oasis-open.org/committees/ballot.php?id=1965 5) DSS-X TC calender entries Use the index here: https://www.oasis-open.org/committees/calendar.php?wg_abbrev=dss-x E.g., https://www.oasis-open.org/committees/event.php?event_id=33788 Thanks! [1] Publicly Accessible URIs http://docs.oasis-open.org/specGuidelines/ndr/namingDirectives.html#accessibleURIs [2] recent discussion on public-access URI references https://lists.oasis-open.org/archives/dss-x/201211/msg00026.html https://lists.oasis-open.org/archives/dss-x/201211/msg00030.html Robin Cover OASIS, Director of Information Services Editor, Cover Pages and XML Daily Newslink Email: robin@oasis-open.org Staff bio: http://www.oasis-open.org/who/staff.php#cover Cover Pages: http://xml.coverpages.org/ Newsletter: http://xml.coverpages.org/newsletterArchive.html Tel: +1 972-296-1783
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]