© 2019 The Calendaring and Scheduling Consortium, Inc.
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on the internet or an intranet, without prior written permission. Permission can be requested from the address below.
The Calendaring and Scheduling Consortium, Inc.
4390 Chaffin Lane
McKinleyville
California 95519
United States of America
www.calconnect.org
The Calendaring and Scheduling Consortium (“CalConnect”) is a global non-profit organization with the aim to facilitate interoperability of collaborative technologies and tools through open standards.
CalConnect works closely with international and regional partners, of which the full list is available on our website ().
The procedures used to develop this document and those intended for its further maintenance are described in the CalConnect Directives.
In particular the different approval criteria needed for the different types of CalConnect documents should be noted. This document was drafted in accordance with the editorial rules of the CalConnect Directives.
Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. CalConnect shall not be held responsible for identifying any or all such patent rights. Details of any patent rights identified during the development of the document will be provided in the Introduction.
Any trade name used in this document is information given for the convenience of users and does not constitute an endorsement.
This document was prepared by Technical Committee PUBLISH.
This document, together with
I0701 CalConnect Document Public Review and Comment
I0702 CalConnect Document Classification and Numbering
I0703 CalConnect Document Processes and Management
CalConnect is committed in expanding the realm of standards in collaborative technologies with a focus on interoperability across the globe and communities of practice.
To facilitate its mission, the CalConnect Board of Directors has decided to align standardization and publication processes with international best practices, such as the ISO standardization process (
This document aims to achieve the said intention.
The document describes requirements for CalConnect standard documents.
This document provides requirements on document structure of the following types of CalConnect publication:
Directive
Standard
Guide
Specification
Amendment
Technical corrigendum
Report
These publication types are described in
This document does not apply to the following types of documents produced by CalConnect, although processes described in this document can be optionally used as guidance:
policy statements;
internal administrative documents; and
how-to guides.
For the purposes of this document, the terms and definitions given in
publishable work item that creates output that relates to standardization
organized process with one or more standardization work items (
entity with authority in charge of a standardization project (
written output of a standardization work item (
document (
document (
According to
internal committee of CalConnect tasked with a scope of work it is responsible for
stage of document (
output of a standardization project (
In this document, this explicitly means any documents and IP rights produced by the standardization project.
entity that publishes standardization work items (
proposal for a new work item (
act of developing a standardization work item (
act of publishing documents (
standarization work item (
publication that is co-published (
Both parties may jointly hold copyright of the joint publication.
advisory group with representatives from CalConnect and an external standardization body (
document register of a list of co-developed (
Intellectual Property Rights
Technical Coordination Committee
CalConnect implements a numbering system for projects/documents.
A project/document index shall be maintained on the CalConnect website with documents listed by number, name, and type.
The project code shall be of the form [n], where [n] is any selected positive integer of five (5) or less digits.
The numbering system applies across all project types. Different project types shall not share an identical project code.
The project code shall be assigned on proposal acceptance of the project.
Co-published documents shall attempt to use an identical project code in both CalConnect and at the collaborative publisher to prevent potential ambiguity, if possible.
The document identifier takes the form of [type][stage] [code][:][y], where:
[type] is the document identifier prefix;
[stage] is the document stage;
[code] is the project code of the project that created the document; and
[y] is the 4-digit edition year.
The edition year is the calendar year in which the document is published. On updates, a document will retain the same project code but may be assigned a different edition year in which the update is published.
Co-published documents shall incorporate codes from all collaborative publishing parties in the document identifier, joined together via a “solidus” sign (“`/`”).
CalConnect deliverables co-published with ISO are referenced as as “CC/ISO”, with IETF as “CC/IETF”.
Document types shall be represented in the “type” as follows:
Standard, “CC”
Directive, “CC/DIR”
Guide, “CC/Guide”
Specification, “CC/S”
Report, “CC/R”
Amendment, “CC/Amd”
Technical corrigendum, “CC/Cor”
Administrative, “CC/A”
“CC/Guide/DS 38002:2018” is a CalConnect Guide at DS stage with project number 38002, published in 2018.
Document stages shall be represented in the “stage” as follows:
Published, “` `” (blank)
Final draft standard, “`/FDS`”
Draft standard, “`/DS`”
Technical committee draft, “`/CD`”
Project group draft / Working draft, “`/WD`”
“CC/FDS 10668:2018” is a CalConnect standard document at FDS stage with project number 10668, published in 2018.
“CC/Guide/DS 20080:2018” is a CalConnect guide at DS stage with project number 20080, published in 2018.
Existing documents can be retrofitted to the scheme as practical.
This section describes the document structure and element requirements of a CalConnect standard document.
The cover page will contain:
CalConnect logo
Document number (
Document type (
Document title
Document status (
Date of publication
Responsible technical committee
Document authors and their affiliations, if any (
Incorporation by reference and hyperlink of the appropriate statements of Intellectual Property Rights, Appropriate Usage, Trademarks, and Disclaimer of Warranty
In co-published deliverables, as well as any further adoptions, the document shall retain the logographic marks of the publishing organizations.
This warning must be shown on the cover page for all draft documents.
WARNING FOR DRAFTS
This document is not a CalConnect Standard. It is distributed for review and comment, and is subject to change without notice and may not be referred to as a Standard. Recipients of this draft are invited to submit, with their comments, notification of any relevant patent rights of which they are aware and to provide supporting documentation.
Certain CalConnect documents are intended for public review, as specified in
The following note must be shown on the cover page for all documents intended for public review.
INSTRUCTIONS FOR REVIEW
This draft is intended for public review. Comments shall be submitted to …
The responsible technical committee shall be shown on the cover page.
Authors and editors of CalConnect published documents shall be shown on the cover page.
Each individual author or editor shall be shown on the cover page with:
their role (author or editor) in the creation of the document;
an affiliation, if the author participated through a CalConnect organizational membership, where the affiliation must be a current CalConnect member at the time of participation as an author or editor. Otherwise, in the case an author is an individual member, it should be clearly marked as so.
When a document is attributable to a TC in its entirety, or to CalConnect as an organization, no individual authorship shall be shown on the cover page.
Contributors other than authors and editors of the document as well as other contributing parties, shall be provided if appropriate within the Foreword.
A table of contents shall be provided in any user consumable format, including HTML, PDF and Word.
This does not apply to standard definition files (CSD XML) intended for machine consumption.
The table of contents may be omitted if the document is to be provided on paper medium with less than five (5) pages.
The body of the document shall have section and subsection identifiers to make it easy to refer clearly to specific items in the document.
Document elements including numbered list items, examples, and notes shall be numbered uniquely within a clause. Such elements shall be cited within the document by their number and containing clause.
“Clause 3 a)”
“6.3.3 a)”
“8.2 Note 3”
“2.6 Example 9”
Tables, figures, formulas shall be numbered uniquely within the document. Such elements shall be cited within the document by their type and number.
“Table 2”
“Figure 5”
“Formula 12”
The foreword shall be the first section of the document, unnumbered. It is a mandatory section.
The foreword shall contain a description of the CalConnect organization and provide the necessary copyright and trademark statements.
It is also the place to provide acknowledgements to contributors.
In a revised CalConnect standard, the foreword shall also describe a summary of changes from the previous edition.
The introduction shall be the second section of the document, unnumbered. It is a mandatory section.
It shall describe the purpose and intent of the document, as well as potential use cases. The document’s relationship with existing CalConnect or external standards, if appropriate to be explained, shall also be described here.
The scope shall always be provided as Section 1.
The section for normative references should be placed at Section 2 of the document.
Informative references shall be placed at the Bibliography section at the end of the document, unnumbered.
References in these sections shall be fully cited.
The terms and definitions sections shall be placed beginning at Section 3.
Annexes are numbered sections provided after the main body text. An annex may be considered informative or normative.
Each annex is given a clause identifier of capital Latin letters starting from the A to Z (English order). The first annex shall be stated as (and referred to) “Annex A”, the second “Annex B”, and so forth.
Clauses within annexes shall start with the annex identifier, for example, the first subclause in Annex A is “A.1”.
Appendixes are “annexes of annexes”, and are given a clause identifier that incorporate the annex it belongs to, followed by a capital Latin letter starting from A to Z (English order).
For example, the first appendix of Annex A will be “Appendix AA”, the second appendix of Annex C will be “Annex CB”.
Clauses within appendix shall start with the appendix identifier, for example, the first subclause in Annex SA is “SA.1”.
Changes to a document from a previous edition shall be described in summarized, bullet-point form at the end of the Foreword (
For documents rendered on paper medium for user consumption, page numbers shall be provided on all pages.
Page numbers shall use Roman numbers of unnumbered initial sections, and Arabic numerals for the main body of text (including appendices).
A trademark and copyright statement of the form shown below must appear on the cover page and the foreword.
Note that “`yyyy" is the 4-digit year, such as "2009`”.
© yyyy The Calendaring and Scheduling Consortium, Inc.
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on the internet or an intranet, without prior written permission. Permission can be requested from the address below.
Draft documents should clearly indicate on the title page and every page of the document that they are a draft document.
A CalConnect document shall be digitally represented in canonical form using the CSD XML (CalConnect Standard Document XML) syntax, in accordance with its defined grammar. This allows the CalConnect document to be digitally rendered into any kind of supported format, including HTML, PDF and Word.
CSD XML is an adopted form of Metanorma XML of the Metanorma standard document model.
The following documents are referred to in the text in such a way that some or all of their content constitutes requirements of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies.