OASIS Web Services Calendar (WS-Calendar) TC

Hi Toby and all,  (please consider NOTEs shortly below) Per the TC's submission request [1], please find the attached starter document for: Application Note on the use of WS-Calendar v1.0 WP-abbrev: app-note The expected URI pattern: http://docs.oasis-open.org/ws-calendar/app-note/v1.0/cnd01/app-note-v1.0-cnd01.doc 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. end of  NOTE  NOTE  NOTE NOTE Please let me know if anything here fails to meet your expectations. Further revisions to this Work Product must be maintained in Working Drafts, following procedures detailed in the TC Handbook [2]. Working Drafts should be made available by uploading the document(s) to the TC's Kavi document repository, or (provisionally/temporarily) to the TC's Subversion (SVN) repository, if SVN has been activated for your TC [3].  TCs are encouraged to use ZIP packaging when the WD releases contain multiple files (and directories). For each WD revision, you will need to: 1) increment the Working Draft revision (number) from 01 to 02, 03, 04 etc., as successive Working Drafts are produced; the revision number needs to be updated at the top of the document in the stage identifier (Working Draft ##) and in the document identifier within the page footer. 2) supply the relevant publication/release/upload date for each successive Working Draft instance, using the  prescribed date format: DD Month YYYY; the date needs to be updated at the top of the document (just below the stage identifier, Working Draft ##) and in the page footer. 3) provide suitable text for a document Abstract, updating this summary with successive revisions to provide an accurate description of the subject matter, goals, scope, etc. 4) keep the Acknowledgments (Appendix A) and Revision History (Appendix C) up-to-date with each WD revision. 5) consult the OASIS Naming Directives document when creating new artifacts that may be part of the Work Product (e.g., image files, XML schemas), observing the rules for name characters in files and proposed directories, and for proposed URIs/namespaces [4]. When the TC votes [5] to approve a Working Draft as a Committee Draft (CSD or CND), the Chair or other designated person must submit a "Committee Specification Draft Creation and Upload Request" accessible on the TC Administration Requests Page [6].  Upon receipt of this form, the TC Administrator will QC and process the Work Product for official publication in the OASIS Library as a Committee Draft ( http://docs.oasis-open.org/ ), including addition of the requisite cover page metadata and other boilerplate information, as described in the TC Handbook. [7] =========== References: [1]  http://lists.oasis-open.org/archives/ws-calendar/201106/msg00004.html      http://tools.oasis-open.org/issues/browse/TCADMIN-531 [2] Working Drafts      http://docs.oasis-open.org/TChandbook/Reference/WorkingDrafts.html [3] SVN Version control, via Tools      http://tools.oasis-open.org/ [4] OASIS Naming Directives      http://docs.oasis-open.org/specGuidelines/ndr/namingDirectives.html [5] Approval of a WD as a CD (CSD or CND)      http://www.oasis-open.org/committees/process-2010-07-28.php#committeeDraft [6] TC Administration Requests Page, see     Committee Specification Draft Creation / Upload Request      http://www.oasis-open.org/resources/tc-admin-requests [7] Committee Specification Drafts and Committee Note Drafts      http://docs.oasis-open.org/TChandbook/Reference/CommitteeSpecDrafts.html      http://docs.oasis-open.org/TChandbook/Reference/CommitteeNoteDrafts.html -- Paul Knight   - Tel: +1 781-861-1013 OASIS - Advancing open standards for the information society Document Process Analyst app-note-v1.0-wd01.doc

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 Toby Considine Chair, OASIS oBIX Technical Committee U.S. National Inst. of Standards and Tech. Smart Grid Architecture Committee Facilities Technology Office University of North Carolina Chapel Hill, NC    Email: Toby.Considine@ unc.edu Phone: (919)962-9073 http://www.oasis-open.org blog: www.NewDaedalus.com     From: Paul Knight [mailto:paul.knight@oasis-open.org] Sent: Tuesday, June 07, 2011 3:15 PM To: ws-calendar@lists.oasis-open.org Subject: [ws-calendar] Initial Working Draft level starter document for Application Note on the use of WS-Calendar v1.0   Hi Toby and all,  (please consider NOTEs shortly below)   Per the TC's submission request [1], please find the attached starter document for: Application Note on the use of WS-Calendar v1.0 WP-abbrev: app-note The expected URI pattern: http://docs.oasis-open.org/ws-calendar/app-note/v1.0/cnd01/app-note-v1.0-cnd01.doc   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. end of  NOTE  NOTE  NOTE NOTE Please let me know if anything here fails to meet your expectations. Further revisions to this Work Product must be maintained in Working Drafts, following procedures detailed in the TC Handbook [2]. Working Drafts should be made available by uploading the document(s) to the TC's Kavi document repository, or (provisionally/temporarily) to the TC's Subversion (SVN) repository, if SVN has been activated for your TC [3].  TCs are encouraged to use ZIP packaging when the WD releases contain multiple files (and directories). For each WD revision, you will need to: 1) increment the Working Draft revision (number) from 01 to 02, 03, 04 etc., as successive Working Drafts are produced; the revision number needs to be updated at the top of the document in the stage identifier (Working Draft ##) and in the document identifier within the page footer. 2) supply the relevant publication/release/upload date for each successive Working Draft instance, using the  prescribed date format: DD Month YYYY; the date needs to be updated at the top of the document (just below the stage identifier, Working Draft ##) and in the page footer. 3) provide suitable text for a document Abstract, updating this summary with successive revisions to provide an accurate description of the subject matter, goals, scope, etc. 4) keep the Acknowledgments (Appendix A) and Revision History (Appendix C) up-to-date with each WD revision. 5) consult the OASIS Naming Directives document when creating new artifacts that may be part of the Work Product (e.g., image files, XML schemas), observing the rules for name characters in files and proposed directories, and for proposed URIs/namespaces [4]. When the TC votes [5] to approve a Working Draft as a Committee Draft (CSD or CND), the Chair or other designated person must submit a "Committee Specification Draft Creation and Upload Request" accessible on the TC Administration Requests Page [6].  Upon receipt of this form, the TC Administrator will QC and process the Work Product for official publication in the OASIS Library as a Committee Draft ( http://docs.oasis-open.org/ ), including addition of the requisite cover page metadata and other boilerplate information, as described in the TC Handbook. [7] =========== References: [1]  http://lists.oasis-open.org/archives/ws-calendar/201106/msg00004.html      http://tools.oasis-open.org/issues/browse/TCADMIN-531 [2] Working Drafts      http://docs.oasis-open.org/TChandbook/Reference/WorkingDrafts.html [3] SVN Version control, via Tools      http://tools.oasis-open.org/ [4] OASIS Naming Directives      http://docs.oasis-open.org/specGuidelines/ndr/namingDirectives.html [5] Approval of a WD as a CD (CSD or CND)      http://www.oasis-open.org/committees/process-2010-07-28.php#committeeDraft [6] TC Administration Requests Page, see     Committee Specification Draft Creation / Upload Request      http://www.oasis-open.org/resources/tc-admin-requests [7] Committee Specification Drafts and Committee Note Drafts      http://docs.oasis-open.org/TChandbook/Reference/CommitteeSpecDrafts.html      http://docs.oasis-open.org/TChandbook/Reference/CommitteeNoteDrafts.html -- Paul Knight   - Tel: +1 781-861-1013 OASIS - Advancing open standards for the information society Document Process Analyst

Hi Toby and WS-Calendar TC, For the TC-managed working drafts, you may use any numbering system which you find most manageable.  It is fine if you start with -03. Regarding the document naming, when documents are approved by the TC for publication in the OASIS Library ( docs.oasis-open.org ), we'll be consistent with the Naming Directives ([4] in the original message).  Thus, when the TC approves the working draft (whatever number it happens to be at that time) we'll start with: http://docs.oasis-open.org/ws-calendar/app-note/v1.0/cnd01/app-note-v1.0-cnd01.doc , and the first version for Public Review will be: http://docs.oasis-open.org/ws-calendar/app-note/v1.0/cnprd01/app-note-v1.0-cnprd01.doc . Regards, Paul On Fri, Aug 5, 2011 at 3:46 PM, Considine, Toby (Campus Services IT) < Toby.Considine@unc.edu > wrote: 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 Toby Considine Chair, OASIS oBIX Technical Committee U.S. National Inst. of Standards and Tech. Smart Grid Architecture Committee Facilities Technology Office University of North Carolina Chapel Hill, NC    Email: Toby.Considine@ unc.edu Phone: (919)962-9073 http://www.oasis-open.org blog: www.NewDaedalus.com     From: Paul Knight [mailto: paul.knight@oasis-open.org ] Sent: Tuesday, June 07, 2011 3:15 PM To: ws-calendar@lists.oasis-open.org Subject: [ws-calendar] Initial Working Draft level starter document for Application Note on the use of WS-Calendar v1.0   Hi Toby and all,  (please consider NOTEs shortly below)   Per the TC's submission request [1], please find the attached starter document for: Application Note on the use of WS-Calendar v1.0 WP-abbrev: app-note The expected URI pattern: http://docs.oasis-open.org/ws-calendar/app-note/v1.0/cnd01/app-note-v1.0-cnd01.doc   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. end of  NOTE  NOTE  NOTE NOTE Please let me know if anything here fails to meet your expectations. Further revisions to this Work Product must be maintained in Working Drafts, following procedures detailed in the TC Handbook [2]. Working Drafts should be made available by uploading the document(s) to the TC's Kavi document repository, or (provisionally/temporarily) to the TC's Subversion (SVN) repository, if SVN has been activated for your TC [3].  TCs are encouraged to use ZIP packaging when the WD releases contain multiple files (and directories). For each WD revision, you will need to: 1) increment the Working Draft revision (number) from 01 to 02, 03, 04 etc., as successive Working Drafts are produced; the revision number needs to be updated at the top of the document in the stage identifier (Working Draft ##) and in the document identifier within the page footer. 2) supply the relevant publication/release/upload date for each successive Working Draft instance, using the  prescribed date format: DD Month YYYY; the date needs to be updated at the top of the document (just below the stage identifier, Working Draft ##) and in the page footer. 3) provide suitable text for a document Abstract, updating this summary with successive revisions to provide an accurate description of the subject matter, goals, scope, etc. 4) keep the Acknowledgments (Appendix A) and Revision History (Appendix C) up-to-date with each WD revision. 5) consult the OASIS Naming Directives document when creating new artifacts that may be part of the Work Product (e.g., image files, XML schemas), observing the rules for name characters in files and proposed directories, and for proposed URIs/namespaces [4]. When the TC votes [5] to approve a Working Draft as a Committee Draft (CSD or CND), the Chair or other designated person must submit a "Committee Specification Draft Creation and Upload Request" accessible on the TC Administration Requests Page [6].  Upon receipt of this form, the TC Administrator will QC and process the Work Product for official publication in the OASIS Library as a Committee Draft ( http://docs.oasis-open.org/ ), including addition of the requisite cover page metadata and other boilerplate information, as described in the TC Handbook. [7] =========== References: [1]  http://lists.oasis-open.org/archives/ws-calendar/201106/msg00004.html      http://tools.oasis-open.org/issues/browse/TCADMIN-531 [2] Working Drafts      http://docs.oasis-open.org/TChandbook/Reference/WorkingDrafts.html [3] SVN Version control, via Tools      http://tools.oasis-open.org/ [4] OASIS Naming Directives      http://docs.oasis-open.org/specGuidelines/ndr/namingDirectives.html [5] Approval of a WD as a CD (CSD or CND)      http://www.oasis-open.org/committees/process-2010-07-28.php#committeeDraft [6] TC Administration Requests Page, see     Committee Specification Draft Creation / Upload Request      http://www.oasis-open.org/resources/tc-admin-requests [7] Committee Specification Drafts and Committee Note Drafts      http://docs.oasis-open.org/TChandbook/Reference/CommitteeSpecDrafts.html      http://docs.oasis-open.org/TChandbook/Reference/CommitteeNoteDrafts.html -- Paul Knight   - Tel: +1 781-861-1013 OASIS - Advancing open standards for the information society Document Process Analyst -- Paul Knight   - Tel: +1 781-861-1013 OASIS - Advancing open standards for the information society Document Process Analyst