[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [ws-calendar] Initial Working Draft level starter document forApplication Note on the use of WS-Calendar v1.0
I missed this when it came out earlier. Thanks to Chet for pointing this out. With this template, we transition from the not completed white paper begun under the old process to the committee note. The White Paper has several revisions (already) and one public review. Under the current process, however, TCs do not issue white papers. I propose starting with the PR, and moving ahead with the WD numbering within the same series, as the approach least likely to cause confusion later. We had WD01, WD02 and CSDPR01. This means we are now at app-note-v1.0-cnd01-wd03 Any objections? Thanks tc "It is the theory that decides what can be observed." - Albert Einstein
From: Paul Knight [mailto:paul.knight@oasis-open.org] Hi Toby and all, (please consider NOTEs shortly below) Per the TC's submission request [1], please find the
The expected URI pattern: NOTE NOTE NOTE NOTE (1) Please understand how the TC's choice of "Work Product Abbreviation" (WP-abbrev) will affect the directory structure and individual file name of your Work Product (White Paper) [4]. A file which is simply named "app-note" (with version info) may be hard to identify outside of its directory structure. (Imagine an individual who downloads application notes from several different TCs, all named "app-note"). In addition, since the WP-abbrev is used in the directory structure, the simple name "app-note" may become confusing if the TC, in its long and productive lifetime, produces several application notes on various future specifications within its charter. The TC may wish to consider other forms, like cal-app-note, ws-cal-app-note, wscal-v1-appnote, etc. Also keep in mind the possibility of multiple "app-note" versions related to the WS-Calendar specification version... they do not necessarily move in lock-step. (This concept is embedded in the title of the attached template, "Application Note on the use of WS-Calendar v1.0 Version 1.0". - It is Version 1.0 of the Application Note for WS-Calendar v1.0.) Although the WP-abbrev is embedded in the attached template in its name, footer, and custom properties, it is not really "set in concrete" until the TC votes to produce a Committee Note Draft for publication in the OASIS Library (docs.oasis-open.org) and eventual Public Review. At that time, the directory structures will be created, etc. So there is a significant amount of time to consider the long-term implications of the choice of WP-abbrev. I urge you all as TC members to discuss this among yourselves. 2) The OASIS Committee Note designation was established by the Board of Directors just last year (2010), and to date there have not been many different Committee Note template formats developed. If this format does not suit your purposes, please feel free to contact any of us on the TC Administration team to discuss your needs. The Committee Note process is intended to provide a means for a TC to communicate its messages in a variety of formats, while ensuring that OASIS' reputation for technical rigor and clarity of IPR implications is not compromised. We'll be happy to work with you to ensure your Committee Note format meets the needs of the TC and your audience.
http://tools.oasis-open.org/issues/browse/TCADMIN-531 [2] Working Drafts [4] OASIS Naming Directives |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]