diff --git a/.github/workflows/docker.yml b/.github/workflows/docker.yml deleted file mode 100644 index d5e719f..0000000 --- a/.github/workflows/docker.yml +++ /dev/null @@ -1,77 +0,0 @@ -# Auto-generated by Cimas: Do not edit it manually! -# See https://github.com/metanorma/cimas -name: docker - -on: - push: - branches: [ master ] - pull_request: - paths-ignore: - - .github/workflows/macos.yml - - .github/workflows/ubuntu.yml - - .github/workflows/windows.yml - -jobs: - test-docker: - runs-on: ubuntu-latest - container: docker://metanorma/mn - steps: - - uses: actions/checkout@master - - name: Checkout submodules - shell: bash - run: | - auth_header="$(git config --local --get http.https://github.com/.extraheader)" - git submodule sync --recursive - git -c "http.extraheader=$auth_header" -c protocol.version=2 submodule update --init --force --recursive --depth=1 - - name: Setup fonts - run: | - # We need to do this to install mscorefonts - apt-add-repository -y contrib - apt-get update - echo ttf-mscorefonts-installer msttcorefonts/accepted-mscorefonts-eula select true | debconf-set-selections - apt-get install -y ttf-mscorefonts-installer - curl -Ls https://raw.githubusercontent.com/metanorma/vista-fonts-installer/master/vista-fonts-installer.sh | bash - - uses: actions/setup-go@v2-beta - with: - go-version: '^1.13.1' - - name: Install yq - run: | - GO111MODULE=on go get github.com/mikefarah/yq/v3 - ln -s $GOPATH/bin/yq /usr/local/bin/yq - - name: Instal gems from local Gemfile - run: | - curl -LO --retry 3 https://raw.githubusercontent.com/metanorma/metanorma-build-scripts/master/gemfile-to-bundle-add.sh | bash - - name: Build document in the Metanorma container - env: - LC_ALL: C.UTF-8 - LANG: C.UTF-8 - LANGUAGE: C.UTF-8 - run: | - make clean all publish - - uses: actions/upload-artifact@master - with: - name: published - path: published - - deploy-gh-pages: - if: github.ref == 'refs/heads/master' - runs-on: ubuntu-latest - needs: test-docker - steps: - - uses: actions/checkout@master - - uses: actions/download-artifact@v1 - with: - name: published - - name: Deploy to GH Pages - uses: peaceiris/actions-gh-pages@v3 - with: - deploy_key: ${{ secrets.GH_DEPLOY_KEY }} - publish_dir: ./published - force_orphan: true - user_name: ${{ github.actor }} - user_email: ${{ format('{0}@users.noreply.github.com', github.actor) }} - commit_message: "${{ format('Deploy to GitHub Pages: {0}', github.sha) }}" - - uses: kolpav/purge-artifacts-action@v1 - with: - token: ${{ secrets.GITHUB_TOKEN }} - expire-in: 0 diff --git a/.github/workflows/generate.yml b/.github/workflows/generate.yml new file mode 100644 index 0000000..8a94620 --- /dev/null +++ b/.github/workflows/generate.yml @@ -0,0 +1,21 @@ +name: generate + +on: + push: + branches: [main] + pull_request: + workflow_dispatch: + +permissions: + contents: read + pages: write + id-token: write + +concurrency: + group: pages + cancel-in-progress: true + +jobs: + site: + uses: actions-mn/.github/.github/workflows/metanorma-generate.yml@v1 + secrets: inherit diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml new file mode 100644 index 0000000..34f525e --- /dev/null +++ b/.github/workflows/release.yml @@ -0,0 +1,17 @@ +name: Release + +on: + push: + branches: [main] + paths: ['sources/**', 'metanorma.yml', 'metanorma.release.yml'] + workflow_dispatch: + +permissions: + contents: write + +jobs: + release: + uses: actions-mn/.github/.github/workflows/metanorma-release.yml@v1 + with: + default-visibility: private + secrets: inherit diff --git a/.tmp.xml b/.tmp.xml new file mode 100644 index 0000000..afae276 --- /dev/null +++ b/.tmp.xml @@ -0,0 +1,1061 @@ + + + + ISO/CalConnect Partner Standards Development Organization (PSDO) Cooperation Agreement + CC/DS 10010:2018 + 10010 + + 2018-11-14T00:00:00Z + + + + + CalConnect + + + + + + CalConnect + + + en + + draft-standard + + 2018 + + + CalConnect + + + + + PUBLISH + + + 1 + 2018-11-14T00:00:00Z + +Foreword

The Calendaring and Scheduling Consortium ("CalConnect") is a global +non-profit organization that pursues the wide availability of truly +interoperable collaboration systems and applications through the use of +open standards. +CalConnect works closely with liaison partners and international +standard organizations including ISO, OASIS and M3AAWG.

+

ISO (the International Organization for Standardization) +is a worldwide federation of national standards bodies (ISO member +bodies). The work of preparing International Standards is normally +carried out through ISO technical committees. Each member body +interested in a subject for which a technical committee has been +established has the right to be represented on that committee. +International organizations, governmental and non-governmental, in +liaison with ISO, also take part in the work. ISO collaborates closely +with the International Electrotechnical Commission (IEC) on all matters +of electrotechnical standardization.

+

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 the Joint Coordination Group of +ISO and CalConnect.

+

This is the first edition of this document.

IntroductionPurpose

The purpose of this document is to establish an understanding between +ISO and CalConnect on cooperation on standards +development.

+

This document formalizes the process of collaboration of +ISO and CalConnect to cooperate and to +enable the collaborative development of standards.

+

The resulting standards are to be jointly published by +ISO and CalConnect as "ISO/CalConnect Standards", +according to processes described in this document.

+Background

One of the objectives of ISO is to facilitate the international +exchange of goods and services through the development of International +Standards.

+

The ISO Council has adopted a policy of inclusiveness +and encourages cooperation between ISO and other standardizing bodies, +where such cooperation would serve to ensure effective and efficient +use of resources available for standardization activities.

+

CalConnect aims to facilitate interoperability of collaborative +technologies with open standards, in particular on calendar, scheduling, +and contacts; its standards are globally recognized and widely applied.

+ + Intention +

ISO and CalConnect agree to the principles of cooperation described in +this document, in all fields subject to approval by the ISO TMB and the +CalConnect TC PUBLISH and TCC.

+
+Process cooperation

ISO and CalConnect wish to avoid duplication of efforts by their +respective committees.

+

ISO produces International Standards in accordance with processes +described in and , with the standard documents +drafted in accordance with the editorial rules of .

+

CalConnect creates publicly available CalConnect Standards through +a consensus-based standardization process described in , and +standard documents created in accordance with .

+

Both ISO and CalConnect believe that cooperation at +the standards development process level provides the following benefits:

+
    +
  • +

    maximizes the deliverable expertise of their experts; and

    +
  • +
  • +

    maximizes the quality of the resulting International Standard.

    +
  • +
+

This agreement facilitates a collaborative development process +for the creation of joint publications (ISO/CalConnect Standards) +between ISO and CalConnect.

+ +Scope

This document describes the agreement between CalConnect and ISO for +the cooperation of standards development and publication.

+

Specifically, it provides the principles and necessary processes for these +collaborative cases between ISO and CalConnect ("Parties"):

+
    +
  • +

    co-development of a standardization work item, proposed by either party

    +
  • +
  • +

    submission of a CalConnect document to ISO for its +standardization process

    +
  • +
+

Standardization processes in this document is intended to align +with , , and .

+ +Terms and definitionsTerms and definitions + ISO members +

ISO member bodies and correspondent members

+
+ + CalConnect members +

CalConnect member bodies

+
+ISO committee + ISO TC + +

ISO Technical Committee (including ISO/IEC JTC1) or Subcommittee

+CalConnect technical committee + CalConnect TC + +

internal committee of CalConnect tasked with a scope of work it +is responsible for

+ + standardization project +

an organized process with one or more standardization work items that +contributes towards a defined scope of work

+
+ + standardization work item +

publishable work item that creates output that relates +to standardization within a standardization project ()

+
+ + project owner +

entity with authority in charge of a standardization project +()

+
+ + document +

written output of a work item

+
+CalConnect deliverable

document () produced by a CalConnect TC +() as described in

+ +

According to , CalConnect deliverables include the +following types: CalConnect Standard, Guide, Specification, Report and +Directives. Directives are not considered a standardization work item.

+
+ISO TC deliverable

document () produced by an ISO TC +() as described in

+ +

According to , ISO TC deliverables include the +following types: International Standards, Technical Specifications, +Publicly Available Specifications and Technical Reports.

+
+ + document stage +

stage of document as specified in the ISO harmonized stages (as defined +in )

+
+standardization project output

output of a standardization project ()

+ +

In this document, it explicitly means any documents and IP rights +produced by the standardization project.

+
+ + proposal for standardization +

proposal for a new work item for standardization

+
+ + co-develop +

act of developing a work item by multiple parties from the proposal stage

+
+ + co-publish +

act of publishing documents () of identical content +by multiple parties

+
+ + joint work item +

work item co-developed () by both parties

+
+ + joint deliverable +

completed form of a joint work item that is designated to be +co-published () by ISO +and CalConnect

+
+joint publication

publication that is co-published () by +ISO and CalConnect

+ +

Different publishers of a joint publication may utilize a +different document layout.

+
+Joint Coordination Group + JCG + +

advisory group with representatives from ISO and CalConnect on +the execution and maintenance of this agreement

+joint project group + JPG + +

group created to be project owner () of a joint work item (), +composed of participants from ISO committees () and CalConnect TCs ()

+joint maintenance group + JMG + +

joint project group () for the sole +purpose of maintaining a +joint publication ()

+ + co-development document register +

document register of a list of co-developed () +documents () developed under this agreement, +held by the Joint Coordination Group ()

+
+ +
+
IPR
+
+

Intellectual Property Rights

+
+
TCC
+
+

CalConnect Technical Coordination Committee

+
+
TMB
+
+

ISO Technical Management Board

+
+
+
+Principles of cooperationCollaborative development process

A collaborative development process is crucial to effective development +of work items between ISO and CalConnect.

+

Both organizations agree to align appropriate internal processes +and procedures in order to facilitate joint development of work items.

+

Three mechanisms are provided below for cooperative development of +joint publications between ISO and CalConnect, namely:

+
    +
  1. +

    CalConnect contributes content to ISO;

    +
  2. +
  3. +

    ISO and CalConnect co-develop a joint deliverable;

    +
  4. +
  5. +

    Adoption of an existing standard from either party.

    +
  6. +
+ + Central coordination group +

ISO and CalConnect agree to the establishment of a joint coordination group +(JCG) to coordinate matters relevant to the execution and maintenance +of this agreement.

+
+Across subject fields

ISO and CalConnect agree that this agreement applies to all subject fields +subject to approval by both parties.

+

Details of implementation are provided in .

+Normative referencing

ISO and CalConnect agree to the normative referencing of their +standards as appropriate in publications of the other organization in +compliance with each organization’s policies and directives relative to +normative references.

+

Implementation details are provided in .

+Patent policy

ISO and CalConnect agree that content of joint deliverables, +including the ISO published form of joint publications, +will remain free of IPR restrictions that would limit their application.

+

Patented content in a joint deliverable is governed by the +ISO patent policy and the CalConnect IPR policy.

+

Any patents involved knowingly in the document shall be made +transparent prior to the DIS stage of the joint deliverable.

+Contributions to ISO standards

ISO International Standards are normally developed within ISO +Committees. As part of this normal development process, an ISO +committee may determine that specific elements of an CalConnect +standard (e.g. figures, data, definitions), along with information from +other sources, would contribute to the development of an ISO Standard.

+

As specified in the , original material contributed to +become part of an ISO publication is normally copied and distributed +within the ISO system as part of the consensus-building process, this +being without prejudice to the rights of the original copyright owner +to exploit the original text.

+

It is also recognized that, where such material is already subject to +copyright, rights have to be granted to ISO to reproduce and circulate +the material.

+

As part of this agreement, CalConnect grants a licence to ISO described +in +for using elements of a CalConnect standard in the development of joint +publications.

+Co-development of standards

In cases where CalConnect has developed a standard, or where CalConnect +is proposing or developing a standard (yet unpublished), which +corresponds to a stated ISO TC need covered by this agreement.

+

In these instances, the relevant ISO TC and CalConnect TC +may agree that it would be mutually beneficial to develop work jointly.

+

ISO and CalConnect agree to a coordinated and specified process for the +co-development of joint publications.

+

The detailed process and procedures are provided in ; copyright of the +resulting deliverables is explained in .

+Adoption of existing standardsGeneral

ISO and CalConnect agree to a coordinated and specified process for the +adoption of either party’s standardization work items, where:

+
    +
  • +

    CalConnect may wish to formally adopt a published ISO +International Standard;

    +
  • +
  • +

    CalConnect may propose that an existing CalConnect standard be +submitted as a final draft International Standard (FDIS) at ISO.

    +
  • +
+

Copyright of joint publications created through adoption is +explained in .

+Adoption of an ISO Standard by CalConnect

CalConnect may wish to formally adopt a published ISO International +Standard.

+

In this case, the source party is ISO and the adopting party +is CalConnect.

+

The method of adoption is specified in .

+Adoption of a CalConnect Standard by ISO

A published CalConnect standard with global use and acceptance may be +proposed for adoption as an ISO International Standard, through the +FDIS fast-track procedure of submitting a CalConnect standard to ISO.

+

In this case, the source party is CalConnect and the adopting party +is ISO.

+

The method of adoption is detailed in .

+Maintenance of joint publications

Maintenance of joint publications shall be a joint responsibility under +a joint process.

+

Details of the implementation of this clause is described in .

+

In joint publications where a maintenance agency or registration authority +is necessary, CalConnect agrees to serve as the default volunteer, as +described in .

+Mutual recognition and joint deliverables requirements

ISO and CalConnect shall establish rules to ensure +the collaborative effort by both parties are mutually +recognized within joint deliverables.

+

The associated requirements are provided in .

+ + Promotional activities +

ISO and CalConnect agree to share and coordinate promotional activities +for the joint publication via the JCG.

+
+Joint Coordination GroupGeneral

ISO and CalConnect agrees to establish a standing body, +the Joint Coordination Group ("JCG"), for:

+
    +
  • +

    maintenance and execution of this agreement; and

    +
  • +
  • +

    coordination and maintenance of procedures between two organizations.

    +
  • +
+ + Mediator for coordination issues +

This group meets as necessary and serves as the forum for discussing +and resolving issues relating to coordination that may arise from time to time.

+
+Coordination role

The JCG will support the individual liaisons between +ISO Technical Committee working groups and project teams, +with CalConnect technical committees.

+

The presence of the JCG is not intended to affect +responsibilities of existing organizational structures +in ISO and CalConnect.

+ + Fields of collaboration +

The JCG is responsible with the determination of the subject fields +of which this agreement applies to, subject to approval by +the ISO Technical Management Board and the CalConnect TC PUBLISH and TCC.

+
+Members

The JCG is composed of an equal number of representatives from both parties:

+
    +
  • +

    Two representatives from ISO

    +
  • +
  • +

    Two representatives from CalConnect

    +
  • +
+ + Amendments to this agreement +

ISO and CalConnect agree that changes to this agreement shall be +first proposed through the JCG, and formalized by a resolution from one +party to the other.

+
+ + + + + + +
Publication, copyright and commercial arrangementsNormative referencing of standards

ISO and CalConnect acknowledge that all documents, +data or electronic files provided by each consisting of or relating to +joint publications are copyrighted property and data and will not be +supplied to any other party without the prior written consent of the +copyright owner, and will not be used, in whole or in part, as a basis +for a joint publication without following specific procedures established by the +respective copyright owner.

+

Each organization will promptly notify the +other if it becomes aware of infringements or imitations by others of +a joint publication.

+CalConnect content license for joint development

In the development, review and adoption process, ISO members are free to copy and +distribute the relevant CalConnect documents for standards development +purposes and in accordance with ISO policies for the circulation of +draft standards and working documents.

+

CalConnect grants ISO a world-wide, non-exclusive, non-sub-licensable +license (except for national body adoption), +to use contents of CalConnect submitted documents to ISO, +within the development, review and adoption process of the +deliverables under this agreement.

+Copyright and exploitation rightsOf adopted standards

The copyright in any resulting ISO/CalConnect International Standard(s) published according to +, including any future versions of such Standard(s), remain with +the source party.

+

The adopting party will neither acquire nor assert copyright ownership or any +other proprietary rights in these ISO/CalConnect International Standard(s).

+

The source party retains all copyrights in the CalConnect Product(s) and +ISO/CalConnect International Standard(s) not specifically granted +hereunder.

+

Subject to the exploitation rights granted above, development by the adopting party (or its members) +of any other work affecting the integrity of the source standard or the ISO/CalConnect International +Standard(s) would need a separate agreement with the source party.

+Of jointly developed standards

Joint deliverables developed through the joint development process according to +, +copyright ownership will be held jointly by ISO +and CalConnect with normal exploitation rights for CalConnect and for +ISO and its members, including for national adoption purposes.

+

ISO and CalConnect may each sell and distribute the jointly developed standard, +in accordance with their own rules, without any royalties to the other.

+

The resulting joint publication is common to both organizations.

+Re-publishing

ISO and CalConnect agree that any re-publishing of content +developed under this agreement, such as the national adoption +of a joint publication by an ISO member body, or the re-publishing +of a joint publication by another organization, +will adhere to this agreement.

+

Publishing arrangements between ISO and ISO member countries are +unchanged by this agreement.

+ + Statement indicating source +

ISO and CalConnect agree that the resulting publication created with +the joint deliverable will contain a suitable statement that describes +the base standard the joint deliverable was derived from.

+
+Notification of right infringement

Each party shall promptly inform the other party if it becomes aware of +any copyright infringement or potential infringement of a joint publication.

+

CalConnect and ISO shall consult with each other to decide the best +way to respond to such infringement.

Alignment of project timelineProject stage mapping

The following table provides a mapping between ISO project stages and +CalConnect project stages. This document identifies stages +according to the ISO project stage names.

+ + Alignment between ISO and CalConnect project stages + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Identification in this documentISO harmonized stage ()CalConnect stage
+ Preliminary + 00 Preliminary00 Preliminary
+ Proposal + 10 Proposal10 Proposal
+ Preparatory + 20 Preparatory20 Preparatory
+ Committee + 30 Committee30 Committee
+ Enquiry + 40 Enquiry40 Enquiry
+ Approval + 50 Approval50 Approval
+ Publication + 60 Publication60 Publication
+ Review + 90 Review90 Review
+ Withdrawal + 95 Withdrawal95 Withdrawal
+Track synchronization

ISO deliverables can be developed according to different tracks +and timelines detailed in and .

+

CalConnect deliverables are developed according to the +timelines detailed in .

+

For a project under this agreement, CalConnect agrees to adopt +a developmental track not slower than the track selected in +ISO to ensure the synchronicity between +development outcome and publication.

Co-development processGeneral

In joint development, technical level support for the development of +these standards is provided through the associated CalConnect TC as +well as the ISO member bodies and their duly appointed technical +experts through the relevant ISO TC.

+

Experts in ISO are encouraged to participate in the +technical work on CalConnect technologies by participating in +CalConnect technical committees.

+First draft

A first draft of the standardization deliverable may be created +for proposal submission, or may be created in the Committee stage. +The draft shall be created through a collaboration process between +experts from both organizations, or at least, the proposing +organization should have received input from the other organization.

+

CalConnect agrees that any draft submitted to ISO +shall adhere to the requirements detailed in , and +applicable internal guidelines of ISO.

+Disapproval and continuance

If the project proposal is rejected by the JCG, its output may still be +developed by the project proposer if appropriate, and its output may +still be proposed to the JCG for co-development in later stages.

+

At any time, if a ballot to approve the development of a joint work item +is disapproved by ISO or CalConnect, each organization may proceed +to develop the joint work item independently of each other.

+Proposal development: Preliminary stageGeneral

At the first instance where either party wishes to co-develop +a project with the other party, it should be raised to the JCG.

+

The JCG shall consult the stakeholders to determine appropriateness +of the project and advise the proposer.

+ + Initiation by CalConnect +

CalConnect may propose to the appropriate ISO TC(s) to +jointly develop a new or existing CalConnect standard +to gain recognition as an ISO/CalConnect Standard.

+
+ + Initiation by ISO TC +

If an ISO TC wishes to initiate the joint development of a +standard, the ISO TC secretariat shall contact the appropriate +CalConnect TC to gauge mutual interest.

+
+Proposal submission: Proposal stage + General +

When the JCG determines interest within ISO to co-develop the +proposed project, the project proposer should submit a proposal +indicating its wish to co-develop the proposed project, +to be approved by the relevant ISO and CalConnect TCs via ballot.

+
+Initiation by CalConnect

CalConnect shall provide a NWIP in accordance with for the +proposal of new work items.

+

In addition, the NWIP shall include:

+
    +
  • +

    rationale for using this process; and

    +
  • +
  • +

    justification of the need for an ISO/CalConnect International +Standard.

    +
  • +
+Initiation by ISO TC

An ISO member shall submit a NWIP to the ISO TC for approval +in accordance with .

+

Concurrently, the corresponding CalConnect TC will submit a +project proposal to the CalConnect TCC, providing the relevant +information for the project and a statement that the project +is to be developed jointly with the relevant ISO TC.

+Fast-track proposal at ISO

When the ISO NWIP is accompanied by an existing CalConnect standard, +members of the ISO TC will be invited to approve its submission as a DIS.

+ +

A two-thirds (2/3) majority vote of participating ISO P-members +is required for approval ().

+
+Approval of co-development

If both organizations approve the proposal for joint development, +the project shall be adopted on both sides by a CalConnect +TC and an ISO TC.

+

The JCG shall then create a joint project group to be the project +owner of the proposed joint work item through the CalConnect TCC and the +secretariat of the ISO TC, consisting of nominated experts from the +relevant CalConnect and ISO TCs.

+

ISO and CalConnect will mutually agree on a Convener for the JPG.

+

This approved project shall be listed in the JCG register of +co-developed projects.

+Content development: Preparatory, Committee, Enquiry stagesGeneral

The goal of these stages are to create an approved, balloted +draft of the joint deliverable by both parties.

+

In these stages, members of the joint project group shall +collaborate closely to ensure efficient and effective +development of the deliverable of the respective stages. +The deliverable shall be developed jointly by experts of +both organizations.

+Stage synchronization

The approval process at CalConnect and ISO shall be adhered to. +CalConnect agrees to synchronize its project stage with +the corresponding ISO project stage.

+

Specifically:

+
    +
  • +

    If a deliverable is approved by ballot at both ISO and CalConnect, +CalConnect will advance the project stage at its +project group accordingly.

    +
  • +
  • +

    If a deliverable is rejected by ballot at either party, +CalConnect will not advance project stage at its +project group, unless a re-ballot at ISO approves +advancement of the deliverable.

    +
  • +
  • +

    In cases where a development stage is optional and skipped +in accordance with and , CalConnect +shall set the stage of its project at the corresponding +stage.

    +
  • +
+Approval of a committee draft

Once consensus is reached within the JPG, the draft is circulated to +the relevant ISO and CalConnect TCs for three-month comment.

+

The JPG prepares a compilation of comments received from both +organizations and develops a revised draft.

+Approval of a draft standard

Once consensus within the JPG is achieved, the draft is provided to ISO +for DIS ballot and CalConnect for DS ballot.

+

Once balloting and approval at that stage, from both organizations, is +completed, the JPG prepares the document for circulation by ISO for a +two-month FDIS vote (according to , unanimous approval in +ISO during DIS ballot implies that a further FDIS ballot is not +necessary).

+

In parallel, CalConnect submits the draft to the CalConnect TCC for FS +ballot.

+Approval for publication

The document is considered approved when:

+
    +
  • +

    ISO achieves the requisite FDIS approval (or unanimous DIS approval), +in accordance with , and;

    +
  • +
  • +

    CalConnect TCC has provided its requisite approval, in accordance +with .

    +
  • +
+

Once the document has been approved by both ISO and CalConnect, the +document is published as a joint ISO/CalConnect standard.

+Pre-publication: Public review

A public review period of 60 days is required for the compliance +to rules, for which both ISO and CalConnect adhere to.

+

A 60-day public review shall be held in the DIS stage of the ISO deliverable.

+

Comments to ISO shall be performed according to and ; +comments to CalConnect shall be performed through CalConnect’s public review procedure.

+

The parties agree to synchronize the dates of review periods for the +maximum benefit to the joint work item.

+Publication + As a CalConnect Standard +

After an ISO ballot on the acceptance of a joint work item as +DIS, FDIS or IS, the joint work item will be published +as a CalConnect Standard.

+
+ + As an ISO/CalConnect Standard +

After an ISO ballot on the acceptance of a joint work item’s status +to proceed to IS from FDIS, the joint work item will be published by +ISO and CalConnect as an ISO/CalConnect Standard.

+
+Abandonment

A joint work item may be abandoned by one of the two parties if it sees +it being inappropriate or is no longer interested or able to contribute +to the joint work item. Each party is allowed to abandon the joint +work, which at that point will become sole work of the other party.

+

A notice of such must be sent by the abandoning party to the JCG and +distributed by both parties to its members.

+

The abandoning party, if the abandoned work is carried on by the other +party, is required to explicitly agree that the copyright of such work +is to be waived to the continuing party to allow publication of the document.

+

The rejoining an abandoned work item prior to publication, by the abandoning party, +is explicitly allowed by this agreement, given a notice is filed at +the JCG, unless in exceptional circumstances.

+ + Additional collaborators +

Parties may bring in additional collaborators under this agreement, +given it is approved by the JCG, that the provisions of this agreement +are fully satisfied by agreements present between all collaborators.

+
+ + Notification +

Notification of availability of new documents within CalConnect +will be announced to the appropriate ISO TCs and CalConnect TCs.

+
+ + Availability of working documents +

Drafts and working documents are available according to +each party’s normal practices.

+
Adoption processGeneral

ISO and CalConnect agree to a coordinated and specified process for the +adoption of either party’s standardization work items, where:

+
    +
  • +

    CalConnect may wish to formally adopt a published ISO International Standard;

    +
  • +
  • +

    CalConnect may propose that an existing CalConnect standard be +submitted as a final draft International Standard (FDIS) at ISO.

    +
  • +
+Adoption of an ISO Standard by CalConnect

CalConnect may wish to formally adopt a published ISO International +Standard as described in ,

+

Such adoption shall be subject to an agreement between CalConnect and +the ISO member body in the country where CalConnect has its legal seat +(ANSI).

+Adoption of a CalConnect Standard by ISOGeneral

As described in , a CalConnect +standard may be adopted by ISO.

+

The adoption of a CalConnect standard at ISO is through FDIS fast-track +as described in this clause.

+

Adoption by ISO FDIS approval is intended to validate an existing +CalConnect standard through ISO’s established member body approval +mechanism.

+Initiation by CalConnect

CalConnect may propose an existing CalConnect standard to be submitted +as a final draft International Standard (FDIS) at ISO.

+

Such requests shall be submitted to the Secretary-General of ISO for +acceptance.

+

The ISO Secretary-General shall then submit a proposal to the relevant +ISO committee for a 30-day ballot which shall decide, by simple majority +vote, on:

+
    +
  1. +

    the need for an ISO International Standard on the subject; and

    +
  2. +
  3. +

    submission of the proposal for FDIS ballot.

    +
  4. +
+Initiation by ISO

Any ISO TC may decide to invite, by simple majority vote, CalConnect to +offer a particular CalConnect standard for adoption under this +agreement, provided agreement has been obtained from CalConnect.

+

Where an ISO TC confirms the need for an ISO International Standard, +but determines that the proposed CalConnect standard should not be +submitted for FDIS ballot, CalConnect shall be consulted on its +interest to proceed with the project jointly.

+Approval

Requirements for acceptance shall be those pertaining to the FDIS +approval stage in .

+

Upon acceptance by CalConnect and the relevant ISO TC, the CalConnect +standard shall be circulated to ISO members for a five-month approval +vote (to also allow for national public review and, where necessary, +translation).

+

The adoption is considered approved once the FDIS ballot is approved.

+

The process described in also applies.

Maintenance of joint deliverablesGeneral

The project groups in both organizations responsible for +the published deliverable shall work in collaboration to +address any corrections or necessary amendments.

+

The intention is to coordinate the initiation of revisions and to +maintain, to the greatest extent possible, one common ISO/CalConnect +Standard on a given subject.

+

When a joint deliverable is deemed to be updated, both parties agree that each +other has the first right of refusal.

+

The revisions shall be published jointly as described +in .

+Systematic review and outcome

Joint publications that have been published for four (4) years since +their last approval date shall be reviewed in their entirety by the +responsible JMG, as determined by the JCG.

+

A decision shall be made by both parties at the end of the review +period, on whether to:

+
    +
  1. +

    confirm the standard, for which no change is necessary;

    +
  2. +
  3. +

    revise, as a new joint work item; or

    +
  4. +
  5. +

    withdraw the standard.

    +
  6. +
+

The decided action shall be initiated within five (5) years of the last +approval date.

+ +

The four (4) years review period provides a one (1) year +timeframe for which a review decision can be made, in accordance with + and where a maximum of five (5) years is +allowed between reviews.

+
+ParticipationAgree to jointly maintain

When both the ISO TC and CalConnect agree to jointly revise the +standard, a joint maintenance group (JMG) is established consisting of +nominated experts from the relevant CalConnect and ISO TCs.

+

ISO and CalConnect mutually agree on a Convener for the MG.

+Non-participation of ISO TC

If CalConnect initiates revision to the document and the relevant ISO +TC decides not to participate in the revision process, ISO shall ensure +that the ISO/CalConnect Standard is not revised until CalConnect has +completed its revision.

+

Once the document has been revised, CalConnect may submit the document +to ISO as a potential new Standard for FDIS fast-track approval to +supercede the earlier ISO/CalConnect Standard.

+

Should the revised document not be submitted by CalConnect, or accepted +by the relevant ISO Committee, the original ISO FDIS fast track +Standard shall be withdrawn, unless otherwise agreed by both +organizations.

+Non-participation of CalConnect

If ISO initiates the revision and CalConnect decides not to participate +in the process, then ISO may continue to revise the Standard.

+

However, any material used from the original ISO/CalConnect Standard +will require a separate agreement with CalConnect.

+ + Comment distribution +

When a party receives formal comments on the joint work item, it shall +share it with the other party within 2 weeks of receiving them, +documented and distributed through the JCG.

+
+ + Withdrawal +

When a review determines that a joint published item should be +withdrawn, both parties agree that the item to be indicated as +withdrawn.

+
+Revision of deliverables + Initiation of revision process +

Revisions to joint publications can be proposed to the relevant +CalConnect or ISO TC at any time by members of CalConnect or the +ISO TC.

+
+ + Amendments and full revisions +

Amendments and full revisions of a joint deliverable +are considered joint new work items, and shall be developed in +accordance with the procedures in .

+
+ + Corrections +

Corrections, such as technical corrigenda, of an ISO/CalConnect +standard, shall be jointly developed by the appropriate ISO TC +and CalConnect TC in accordance with each organizations' internal +procedures.

+
+ + Maintenance agency and registration authority + + + General +

Both organizations recognize that a maintenance agency or +registration authority is required for the successful implementation of +certain standardization deliverables resulting from this agreement.

+
+Default volunteer role

For standards developed under this agreement, CalConnect volunteers +to serve as their maintenance agency or registration authority as +necessary.

+

CalConnect shall submit a suitable application to ISO once a NWIP +requiring establishment of a maintenance agency or registration +authority for a joint work item is approved.

Deliverable requirements + Document layout +

CalConnect and ISO will establish a consistent layout, including +associated supporting information (e.g. foreword, introduction), for +joint publications.

+
+ + Trademark and copyright statements +

Similar to the process applied on national adoption +of an ISO deliverable, trademarks and copyright statements +of both organizations shall appear on the document cover page as +well as in the foreword.

+
+ + Patent statement +

A suitable patent statement in accordance with the ISO patent policy +and the CalConnect patent policy shall be stated in the foreword +of the document.

+
+ + Publication dates +

The edition year and the year of publishing of a joint deliverable +shall be identical in the ISO and CalConnect deliverables.

+
+Cover page

In ISO and CalConnect publications of the joint publication, +as well as any further adoptions, shall retain the logographic marks +of both organizations.

+

The joint publication shall also provide a single document identifier +on the cover page.

+ + Introduction part +

The introduction shall state that it is a joint work product +between ISO and CalConnect.

+
+Document identifier and references

ISO publications published through joint publication under this +agreement will be referenced with the following prefixes:

+
    +
  • +

    "ISO/CC" in ISO documents

    +
  • +
  • +

    "CC/ISO" in CalConnect documents

    +
  • +
+

In case that a joint publication is performed under ISO/IEC JTC 1, +the resulting prefixes are:

+
    +
  • +

    "ISO/IEC/CC" in ISO and IEC documents;

    +
  • +
  • +

    "CC/ISO/IEC" in CalConnect documents

    +
  • +
+

References shall contain sufficient information for those wishing +to obtain the equivalent documents of the other party to be +able to do so.

+ +

In the document identifier "ISO/CC 18001:2018", "ISO/CC" is the prefix, +"18001" the project code, and "2018" the edition date.

+
+ +

In the document identifier "ISO/IEC/CC 28001:2018", "ISO/IEC/CC" is the +prefix, "28001" the project code, and "2018" the edition date.

+
+Project code

A mutually acceptable number will be used for the project code, with +the goal of achieving identical deliverable numbers in ISO and +CalConnect to prevent potential ambiguity.

+

ISO and CalConnect shall also give consideration to any previous numbering +used by ISO or CalConnect to determine the number designation for the +Standards developed in accordance with this agreement.

+Editorial work

ISO and CalConnect will perform final editorial/production work on the +joint work item with approval of the final proof by both parties prior +to ISO publication.

+

CalConnect and ISO will not charge each other for any editing or +production work undertaken in development of the final +ISO/CalConnect Standard.

Normative References + + CalConnect Directive: Standardization and publication + + CC/DIR 10001 + + + CalConnect Directive: Standard document requirements + + CC/DIR 10002 + + + Procedures specific to ISO + + ISO/IEC Directives, Part 1, Consolidated ISO Supplement + + Procedures for the technical work + ISO/IEC Directives, Part 1 + + + + ISO + + + + + + IEC + + + + Principles and rules for the structure and drafting of ISO and IEC documents + ISO/IEC Directives, Part 2 + + + + ISO + + + + + + IEC + + + + + 2018-12-10 + Standardization and related activities — General vocabulary + Normalisation et activités connexes — Vocabulaire général + https://www.iso.org/standard/39976.html + https://www.iso.org/obp/ui/#!iso:std:39976:en + https://www.iso.org/contents/data/standard/03/99/39976.detail.rss + ISO/IEC Guide 2:2004 + + 2004 + + + + + International Organization for Standardization + ISO + www.iso.org + + + + + + International Electrotechnical Commission + IEC + www.iec.ch + + + 8 + en + fr + + ISO/IEC Guide 2:2004 provides general terms and definitions concerning standardization and related activities. It is intended to contribute fundamentally towards mutual understanding amongst the members of ISO and IEC and the various governmental and non-governmental agencies involved in standardization at international, regional and national levels. It is intended also to provide a suitable source for teaching and for reference, briefly covering basic theoretical and practical principles of standardization, certification and laboratory accreditation.It is not the aim of ISO/IEC Guide 2:2004 to duplicate definitions of terms adequately defined for general purposes in other authoritative international vocabularies.NOTE 1 From this point of view, particular attention is drawn to the International vocabulary of basic and general terms in metrology (VIM) jointly prepared by ISO, IEC, BIPM, IFCC, IUPAC, IUPAP and OIML, and published in 1993 (second edition).NOTE 2 In addition to the terms given in the official languages of ISO and IEC (English, French and Russian), equivalent terms provided by the relevant member bodies are given in the following languages: + Le Guide ISO/CEI 2 fournit des termes généraux et leurs définitions concernant la normalisation et les activités connexes. Il est prévu pour contribuer, de manière fondamentale, à la compréhension mutuelle entre les membres de l’ISO, de la CEI et des diverses institutions gouvernementales et non gouvernementales engagées dans la normalisation aux niveaux international, régional et national. Il est prévu également pour constituer un instrument de formation ou de référence couvrant brièvement les principes de base, théoriques et pratiques, de la normalisation, de la certification et de l’accréditation des laboratoires d’essais.L’objet du Guide ISO/CEI 2 n’est pas de redonner les définitions de termes déjà définis de façon satisfaisante dans leur sens général par d’autres vocabulaires internationaux faisant autorité.NOTE 1 Une attention particulière doit être portée, à cet égard, au Vocabulaire international des termes fondamentaux et généraux de métrologie (VIM) préparé conjointement par l’ISO, la CEI, le BIPM, la FICC, l’OIML, l’UICPA et l’UIPPA et qui a été publié en 1993 (deuxième édition).NOTE 2 En plus des termes donnés dans les langues officielles de l’ISO et de la CEI (anglais, français et russe), les termes équivalents fournis par les comités membres responsables sont donnés dans les langues suivantes : + + 90 + 93 + + + 2004 + + + ISO/IEC + + + + + + ISO/IEC Guide 2:1996 + + + + ISO/TMBGTechnical Management Board - groups + + + 01.120 + Standardization. General rules + + + 01.040.01 + Generalities. Terminology. Standardization. Documentation (Vocabularies) + + + Bibliography + + World Trade Organization, The WTO Agreements Series Technical Barriers to Trade + WTO TBT Agreements + + +
diff --git a/Gemfile.lock b/Gemfile.lock new file mode 100644 index 0000000..b18dfdb --- /dev/null +++ b/Gemfile.lock @@ -0,0 +1,293 @@ +GEM + remote: https://rubygems.org/ + specs: + addressable (2.7.0) + public_suffix (>= 2.0.2, < 5.0) + asciidoctor (2.0.10) + asciimath (1.0.9) + bibtex-ruby (5.1.4) + latex-decode (~> 0.0) + camertron-eprun (1.1.1) + cldr-plurals-runtime-rb (1.0.1) + cnccs (0.1.6) + concurrent-ruby (1.1.6) + domain_name (0.5.20190701) + unf (>= 0.0.5, < 1.0.0) + down (5.1.1) + addressable (~> 2.5) + faraday (1.0.1) + multipart-post (>= 1.2, < 3) + ffi (1.13.1) + ffi-compiler2 (2.0.0) + ffi (>= 1.0.0) + rake + fontist (0.2.0) + down (~> 5.0) + libmspack (~> 0.1.0) + gb-agencies (0.0.6) + git (1.7.0) + rchardet (~> 1.8) + html2doc (1.0.1) + asciimath (~> 1.0.9) + htmlentities (~> 4.3.4) + image_size + mime-types + nokogiri (>= 1.10.4) + thread_safe + uuidtools + htmlentities (4.3.4) + http-cookie (1.0.3) + domain_name (~> 0.5) + iev (0.2.3) + nokogiri (>= 1.10.4) + image_size (2.0.2) + iso-639 (0.3.5) + iso639 (1.3.2) + isodoc (1.0.28) + asciimath + html2doc (~> 1.0.0) + htmlentities (~> 4.3.4) + liquid + metanorma (~> 1.0.0) + nokogiri (>= 1.10.4) + rake (~> 12.0) + roman-numerals + sassc (~> 2.4.0) + thread_safe + uuidtools + isoics (0.1.8) + latex-decode (0.3.1) + libmspack (0.1.0) + ffi + ffi-compiler2 (>= 2.0.0) + liquid (4.0.3) + mathml2asciimath (0.0.10) + htmlentities (~> 4.3.4) + nokogiri (>= 1.10.4) + metanorma (1.0.5) + asciidoctor + htmlentities + mn2pdf (~> 1.13) + nokogiri + metanorma-cli (1.2.13.1) + fontist (~> 0.2.0) + git (~> 1.5) + isodoc (~> 1.0.0) + metanorma (~> 1.0.0) + metanorma-csa (~> 1.4.0) + metanorma-csd (~> 1.3.0) + metanorma-gb (~> 1.3.0) + metanorma-generic (~> 1.4.0) + metanorma-iec (~> 1.0.0) + metanorma-ietf (~> 2.0.0) + metanorma-iho (~> 0.0.1) + metanorma-iso (~> 1.3.0) + metanorma-itu (~> 1.0.0) + metanorma-m3d (~> 1.3.0) + metanorma-nist (~> 1.0.0) + metanorma-ogc (~> 1.0.0) + metanorma-standoc (~> 1.4.0) + metanorma-un (~> 0.3.1) + relaton-cli (>= 0.8.2) + thor (~> 0.20.3) + metanorma-csa (1.4.12) + htmlentities (~> 4.3.4) + image_size + isodoc (~> 1.0.0) + metanorma-standoc (~> 1.4.0) + mime-types + ruby-jing + thread_safe + uuidtools + metanorma-csd (1.3.23) + isodoc (~> 1.0.0) + metanorma-standoc (~> 1.4.0) + metanorma-gb (1.3.26) + gb-agencies (~> 0.0.4) + htmlentities (~> 4.3.4) + isodoc (~> 1.0.0) + metanorma-iso (~> 1.3.0) + twitter_cldr (~> 4.4.4) + metanorma-generic (1.4.10) + htmlentities (~> 4.3.4) + isodoc (~> 1.0.0) + metanorma-standoc (~> 1.4.0) + ruby-jing + metanorma-iec (1.0.8) + isodoc (~> 1.0.0) + metanorma-iso (~> 1.3.0) + ruby-jing + metanorma-ietf (2.0.12) + isodoc (~> 1.0.0) + mathml2asciimath + metanorma-standoc (~> 1.4.0) + metanorma-iho (0.0.3) + htmlentities (~> 4.3.4) + isodoc (~> 1.0.0) + metanorma-generic (~> 1.4.0) + metanorma-standoc (~> 1.4.0) + metanorma-iso (1.3.26) + isodoc (~> 1.0.0) + metanorma-standoc (~> 1.4.0) + mn2sts (~> 1.2.0) + ruby-jing + tokenizer (~> 0.3.0) + twitter_cldr + metanorma-itu (1.0.17) + htmlentities (~> 4.3.4) + isodoc (~> 1.0.0) + metanorma-standoc (~> 1.4.0) + ruby-jing + metanorma-m3d (1.3.21) + asciimath + htmlentities (~> 4.3.4) + image_size + isodoc (~> 1.0.0) + metanorma-standoc (~> 1.4.0) + mime-types + ruby-jing + thread_safe + uuidtools + metanorma-nist (1.0.9) + htmlentities (~> 4.3.4) + iso-639 + isodoc (~> 1.0.0) + metanorma-standoc (~> 1.4.0) + ruby-jing + twitter_cldr + tzinfo-data + metanorma-ogc (1.0.8) + htmlentities (~> 4.3.4) + iso-639 + isodoc (~> 1.0.20) + metanorma-standoc (~> 1.4.0) + ruby-jing + metanorma-standoc (1.4.0) + asciidoctor (~> 2.0.0) + concurrent-ruby + iev (~> 0.2.1) + isodoc (~> 1.0.20) + mathml2asciimath + mimemagic + relaton (~> 1.1.0) + relaton-iev (~> 1.0.0) + ruby-jing + sterile (~> 1.0.14) + unicode2latex (~> 0.0.1) + metanorma-un (0.3.10) + htmlentities (~> 4.3.4) + iso-639 + isodoc (~> 1.0.0) + metanorma-standoc (~> 1.4.0) + roman-numerals + ruby-jing + twitter_cldr + mime-types (3.3.1) + mime-types-data (~> 3.2015) + mime-types-data (3.2020.0512) + mimemagic (0.3.5) + mini_portile2 (2.4.0) + mn2pdf (1.14) + mn2sts (1.2.0) + multipart-post (2.1.1) + nokogiri (1.10.9) + mini_portile2 (~> 2.4.0) + optout (0.0.2) + public_suffix (4.0.5) + rake (12.3.3) + rchardet (1.8.0) + relaton (1.1.0) + relaton-calconnect (~> 1.1.0) + relaton-gb (~> 1.1.0) + relaton-iec (~> 1.1.0) + relaton-ieee (~> 1.1.0) + relaton-ietf (~> 1.1.0) + relaton-iso (~> 1.1.0) + relaton-itu (~> 1.1.0) + relaton-nist (~> 1.1.0) + relaton-ogc (~> 1.1.0) + relaton-omg (~> 1.1.0) + relaton-un (~> 1.1.0) + relaton-w3c (~> 1.1.0) + relaton-bib (1.1.0) + addressable + bibtex-ruby + iso639 + nokogiri + relaton-calconnect (1.1.0) + faraday + relaton-iso-bib (~> 1.1.0) + relaton-cli (1.1.2) + liquid + relaton (~> 1.1.0) + thor + relaton-gb (1.1.0) + cnccs (~> 0.1.1) + gb-agencies (~> 0.0.1) + relaton-iso-bib (>= 1.1.0) + relaton-iec (1.1.0) + addressable + relaton-iso-bib (~> 1.1.0) + relaton-ieee (1.1.0) + faraday (~> 1.0.0) + relaton-bib (~> 1.1.0) + relaton-ietf (1.1.3) + relaton-bib (~> 1.1.0) + relaton-iev (1.0.0) + relaton (~> 1) + relaton-iso (1.1.0) + relaton-iec (~> 1.1.0) + relaton-iso-bib (~> 1.1.0) + relaton-iso-bib (1.1.0) + isoics (~> 0.1.6) + relaton-bib (~> 1.1.0) + relaton-itu (1.1.0) + relaton-iso-bib (~> 1.1.0) + relaton-nist (1.1.0) + relaton-bib (~> 1.1.0) + rubyzip + relaton-ogc (1.1.0) + faraday (~> 1.0.0) + relaton-iso-bib (~> 1.1.0) + relaton-omg (1.1.0) + relaton-bib (~> 1.1.0) + relaton-un (1.1.0) + faraday + http-cookie + relaton-iso-bib (~> 1.1.0) + unf_ext (>= 0.0.7.7) + relaton-w3c (1.1.0) + relaton-bib (>= 1.1.0) + roman-numerals (0.3.0) + ruby-jing (0.0.1) + optout (>= 0.0.2) + rubyzip (2.3.0) + sassc (2.4.0) + ffi (~> 1.9) + sterile (1.0.16) + nokogiri (>= 1.10.8) + thor (0.20.3) + thread_safe (0.3.6) + tokenizer (0.3.0) + twitter_cldr (4.4.5) + camertron-eprun + cldr-plurals-runtime-rb (~> 1.0) + tzinfo + tzinfo (2.0.2) + concurrent-ruby (~> 1.0) + tzinfo-data (1.2020.1) + tzinfo (>= 1.0.0) + unf (0.1.4) + unf_ext + unf_ext (0.0.7.7) + unicode2latex (0.0.3) + uuidtools (2.1.5) + +PLATFORMS + ruby + +DEPENDENCIES + metanorma-cli + +BUNDLED WITH + 2.1.4 diff --git a/deploy_key.pub b/deploy_key.pub new file mode 100644 index 0000000..df547dd --- /dev/null +++ b/deploy_key.pub @@ -0,0 +1 @@ +ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQC+ndZfKRviI7/I64xEvIRhGpggAoXnOXyrLTpNwD3WuMvXkrt+hS9OQNoOrpISdzK/d4PVSOoScm6tOpZ/jFjwKfkpWKgHQWjkZj5ICz2jGO4QkwDKlBu/alwoRzF86P60vO417xTTNuzz3H/TQakp8KJgXdbGfK7wvYQzoaidYgGN4Gvz0hTUVuByNjItB/QWhi8nUX3+3tWqhkKcVLIzWc9wKC8HcFUqbgPQlalMuc7bPcM+1cOraHeeoJAhOVoKMnFLVefIAWPMr9Zt+qv97bZ3MJHou3aVh7boUyD66DLIsWoGJxgqq5jZs1kPd+GvBBMjc8jtljbeu5QoYwZp ci@metanorma.org diff --git a/documents.html b/documents.html new file mode 100644 index 0000000..615c4da --- /dev/null +++ b/documents.html @@ -0,0 +1,1138 @@ + + + + TC-PUBLISH + + + + + + + + + +
+
+
CalConnect
+
+
+
+
+
+
TC-PUBLISH
+
+
+
+
+
+
+
+
+

+ + CC/FDS 10010:2019 + +

+
+ +
+
+ standard +
+
+
+ + + +
+
+ + + final-draft + +
+
+ +
+ + 2019-01-18 +
+
+
+ +
+ +
+ +
+ + +
+ HTML +
+ + +
+ PDF +
+ + +
+ Word +
+ + +
+ XML +
+ +
+
+
+ + + + diff --git a/documents.rxl b/documents.rxl new file mode 100644 index 0000000..0346042 --- /dev/null +++ b/documents.rxl @@ -0,0 +1,43 @@ +TC-PUBLISHCalConnect + ISO/CalConnect Partner Standards Development Organization (PSDO) Cooperation Agreement + documents/cc-10010.xml + documents/cc-10010.pdf + documents/cc-10010.doc + documents/cc-10010.html + documents/cc-10010.rxl + CC/FDS 10010:2019 + 10010 + + 2019-01-18 + + + + + CalConnect + + + + + + CalConnect + + + 1 + + 2019-01-18 + + en + + + final-draft + + + 2019 + + + CalConnect + + + + + diff --git a/documents/cc-10010.doc b/documents/cc-10010.doc new file mode 100644 index 0000000..8e68bf4 --- /dev/null +++ b/documents/cc-10010.doc @@ -0,0 +1,4545 @@ +MIME-Version: 1.0 +Content-Type: multipart/related; boundary="----=_NextPart_86bf3968.c2a0.4313" + +------=_NextPart_86bf3968.c2a0.4313 +Content-Location: file:///C:/Doc/cc-10010.htm +Content-Type: text/html; charset="utf-8" + + + + + + + + + + + + +

+ + CC/FDS 10010:2019 + + + +

+ + +

+ +

+ CalConnect  + + PUBLISH + +

+ +

+ ISO/CalConnect Partner Standards Development Organization (PSDO) Cooperation Agreement + +
+ +

+ + + + + + + +

+ +

 

+ +

+ +
+ +

Final Draft Standard

+ + +
+ +

+ +

 

+ +

+ + +
+ +
+

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. +

+
+
+ +
+ + +
+ +
+ + + + + +

 

+
+

+
+

+
+ +

+ Contents +

+ +

 TOC + \o "1-2" \h \z \u + + +. + + + PAGEREF _Toc230414067 \h + 1 +

+ +

+ + +Warning for Drafts +. + + + PAGEREF _Toc732875354 \h + 1 + + +

+ +

+ + + +. + + + PAGEREF _Toc385853796 \h + 1 + + +

+ +

+ + + +. + + + PAGEREF _Toc915356927 \h + 1 + + +

+ +

+ + +Foreword +. + + + PAGEREF _Toc163817744 \h + 1 + + +

+ +

+ + +Introduction +. + + + PAGEREF _Toc885659155 \h + 1 + + +

+ +

+ + +Purpose +. + + + PAGEREF _Toc662284327 \h + 1 + + +

+ +

+ + +Background +. + + + PAGEREF _Toc313278745 \h + 1 + + +

+ +

+ + +Intention +. + + + PAGEREF _Toc696753281 \h + 1 + + +

+ +

+ + +Process cooperation +. + + + PAGEREF _Toc552721456 \h + 1 + + +

+ +

+ + +1. Scope +. + + + PAGEREF _Toc369478452 \h + 1 + + +

+ +

+ + +2. Normative references +. + + + PAGEREF _Toc662889700 \h + 1 + + +

+ +

+ + +3. Terms and definitions +. + + + PAGEREF _Toc669873431 \h + 1 + + +

+ +

+ + +3.1. Terms and definitions +. + + + PAGEREF _Toc311454650 \h + 1 + + +

+ +

+ + +3.2. Abbreviations +. + + + PAGEREF _Toc664206716 \h + 1 + + +

+ +

+ + +4. Principles of cooperation +. + + + PAGEREF _Toc388573314 \h + 1 + + +

+ +

+ + +4.1. Collaborative development process +. + + + PAGEREF _Toc144158776 \h + 1 + + +

+ +

+ + +4.2. Central coordination group +. + + + PAGEREF _Toc410172252 \h + 1 + + +

+ +

+ + +4.3. Across subject fields +. + + + PAGEREF _Toc550269071 \h + 1 + + +

+ +

+ + +4.4. Normative referencing +. + + + PAGEREF _Toc667815229 \h + 1 + + +

+ +

+ + +4.5. Patent policy +. + + + PAGEREF _Toc875224183 \h + 1 + + +

+ +

+ + +4.6. Contributions to ISO standards +. + + + PAGEREF _Toc884493122 \h + 1 + + +

+ +

+ + +4.7. Co-development of standards +. + + + PAGEREF _Toc544545998 \h + 1 + + +

+ +

+ + +4.8. Adoption of existing standards +. + + + PAGEREF _Toc047354330 \h + 1 + + +

+ +

+ + +4.9. Maintenance of joint publications +. + + + PAGEREF _Toc288601155 \h + 1 + + +

+ +

+ + +4.10. Mutual recognition and joint deliverables requirements +. + + + PAGEREF _Toc865030914 \h + 1 + + +

+ +

+ + +4.11. Promotional activities +. + + + PAGEREF _Toc368750936 \h + 1 + + +

+ +

+ + +5. Joint Coordination Group +. + + + PAGEREF _Toc010284605 \h + 1 + + +

+ +

+ + +5.1. General +. + + + PAGEREF _Toc214312853 \h + 1 + + +

+ +

+ + +5.2. Mediator for coordination issues +. + + + PAGEREF _Toc353673605 \h + 1 + + +

+ +

+ + +5.3. Coordination role +. + + + PAGEREF _Toc627079372 \h + 1 + + +

+ +

+ + +5.4. Fields of collaboration +. + + + PAGEREF _Toc014032753 \h + 1 + + +

+ +

+ + +5.5. Members +. + + + PAGEREF _Toc660649517 \h + 1 + + +

+ +

+ + +6. Amendments to this agreement +. + + + PAGEREF _Toc483557754 \h + 1 + + +

+ +

+ + +Appendix A (normative) Publication, copyright and commercial arrangements +. + + + PAGEREF _Toc669524762 \h + 1 + + +

+ +

+ + +A.1. Normative referencing of standards +. + + + PAGEREF _Toc909093452 \h + 1 + + +

+ +

+ + +A.2. CalConnect content license for joint development +. + + + PAGEREF _Toc718369549 \h + 1 + + +

+ +

+ + +A.3. Copyright and exploitation rights +. + + + PAGEREF _Toc565304938 \h + 1 + + +

+ +

+ + +A.4. Re-publishing +. + + + PAGEREF _Toc358633616 \h + 1 + + +

+ +

+ + +A.5. Statement indicating source +. + + + PAGEREF _Toc808155435 \h + 1 + + +

+ +

+ + +A.6. Notification of right infringement +. + + + PAGEREF _Toc306440971 \h + 1 + + +

+ +

+ + +Appendix B (normative) Alignment of project timeline +. + + + PAGEREF _Toc180670934 \h + 1 + + +

+ +

+ + +B.1. Project stage mapping +. + + + PAGEREF _Toc961873139 \h + 1 + + +

+ +

+ + +B.2. Track synchronization +. + + + PAGEREF _Toc187325597 \h + 1 + + +

+ +

+ + +Appendix C (normative) Co-development process +. + + + PAGEREF _Toc055396951 \h + 1 + + +

+ +

+ + +C.1. General +. + + + PAGEREF _Toc009177637 \h + 1 + + +

+ +

+ + +C.2. First draft +. + + + PAGEREF _Toc899900165 \h + 1 + + +

+ +

+ + +C.3. Disapproval and continuance +. + + + PAGEREF _Toc866407257 \h + 1 + + +

+ +

+ + +C.4. Proposal development: Preliminary stage +. + + + PAGEREF _Toc019977796 \h + 1 + + +

+ +

+ + +C.5. Proposal submission: Proposal stage +. + + + PAGEREF _Toc333430389 \h + 1 + + +

+ +

+ + +C.6. Content development: Preparatory, Committee, Enquiry stages +. + + + PAGEREF _Toc754434824 \h + 1 + + +

+ +

+ + +C.7. Pre-publication: Public review +. + + + PAGEREF _Toc114567658 \h + 1 + + +

+ +

+ + +C.8. Publication +. + + + PAGEREF _Toc870277351 \h + 1 + + +

+ +

+ + +C.9. Abandonment +. + + + PAGEREF _Toc862649077 \h + 1 + + +

+ +

+ + +C.10. Additional collaborators +. + + + PAGEREF _Toc629499720 \h + 1 + + +

+ +

+ + +C.11. Notification +. + + + PAGEREF _Toc894215624 \h + 1 + + +

+ +

+ + +C.12. Availability of working documents +. + + + PAGEREF _Toc400594164 \h + 1 + + +

+ +

+ + +Appendix D (normative) Adoption process +. + + + PAGEREF _Toc957199738 \h + 1 + + +

+ +

+ + +D.1. General +. + + + PAGEREF _Toc468463234 \h + 1 + + +

+ +

+ + +D.2. Adoption of an ISO Standard by CalConnect +. + + + PAGEREF _Toc910343673 \h + 1 + + +

+ +

+ + +D.3. Adoption of a CalConnect Standard by ISO +. + + + PAGEREF _Toc588298022 \h + 1 + + +

+ +

+ + +Appendix E (normative) Maintenance of joint deliverables +. + + + PAGEREF _Toc253874381 \h + 1 + + +

+ +

+ + +E.1. General +. + + + PAGEREF _Toc406143897 \h + 1 + + +

+ +

+ + +E.2. Systematic review and outcome +. + + + PAGEREF _Toc199317163 \h + 1 + + +

+ +

+ + +E.3. Participation +. + + + PAGEREF _Toc514643740 \h + 1 + + +

+ +

+ + +E.4. Comment distribution +. + + + PAGEREF _Toc495006217 \h + 1 + + +

+ +

+ + +E.5. Withdrawal +. + + + PAGEREF _Toc700628584 \h + 1 + + +

+ +

+ + +E.6. Revision of deliverables +. + + + PAGEREF _Toc763665349 \h + 1 + + +

+ +

+ + +E.7. Maintenance agency and registration authority +. + + + PAGEREF _Toc573840432 \h + 1 + + +

+ +

+ + +E.8. General +. + + + PAGEREF _Toc200430449 \h + 1 + + +

+ +

+ + +E.9. Default volunteer role +. + + + PAGEREF _Toc342699098 \h + 1 + + +

+ +

+ + +Appendix F (normative) Deliverable requirements +. + + + PAGEREF _Toc410272454 \h + 1 + + +

+ +

+ + +F.1. Document layout +. + + + PAGEREF _Toc739721323 \h + 1 + + +

+ +

+ + +F.2. Trademark and copyright statements +. + + + PAGEREF _Toc804235203 \h + 1 + + +

+ +

+ + +F.3. Patent statement +. + + + PAGEREF _Toc620644575 \h + 1 + + +

+ +

+ + +F.4. Publication dates +. + + + PAGEREF _Toc848778198 \h + 1 + + +

+ +

+ + +F.5. Cover page +. + + + PAGEREF _Toc824897987 \h + 1 + + +

+ +

+ + +F.6. Introduction part +. + + + PAGEREF _Toc265889836 \h + 1 + + +

+ +

+ + +F.7. Document identifier and references +. + + + PAGEREF _Toc458114612 \h + 1 + + +

+ +

+ + +F.8. Project code +. + + + PAGEREF _Toc593864273 \h + 1 + + +

+ +

+ + +F.9. Editorial work +. + + + PAGEREF _Toc112530461 \h + 1 + + +

+ +

+ + +Bibliography +. + + + PAGEREF _Toc303672340 \h + 1 + + +

+ +

+ + + + +

 

+ +

+ + +
+ + + + + + + + + +
+

+
+

+
+

Foreword

+

The Calendaring and Scheduling Consortium (“CalConnect”) is a global +non-profit organization that pursues the wide availability of truly +interoperable collaboration systems and applications through the use of +open standards. +CalConnect works closely with liaison partners and international +standard organizations including ISO, OASIS and M3AAWG.

+

ISO (the International Organization for Standardization) +is a worldwide federation of national standards bodies (ISO member +bodies). The work of preparing International Standards is normally +carried out through ISO technical committees. Each member body +interested in a subject for which a technical committee has been +established has the right to be represented on that committee. +International organizations, governmental and non-governmental, in +liaison with ISO, also take part in the work. ISO collaborates closely +with the International Electrotechnical Commission (IEC) on all matters +of electrotechnical standardization.

+

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 the Joint Coordination Group of +ISO and CalConnect.

+

This is the first edition of this document.

+
+

+
+

+
+

Introduction

+

Purpose

The purpose of this document is to establish an understanding between +ISO and CalConnect on cooperation on standards +development.

+

This document formalizes the process of collaboration of +ISO and CalConnect to cooperate and to +enable the collaborative development of standards.

+

The resulting standards are to be jointly published by +ISO and CalConnect as “ISO/CalConnect Standards”, +according to processes described in this document.

+

Background

One of the objectives of ISO is to facilitate the international +exchange of goods and services through the development of International +Standards.

+

The ISO Council has adopted a policy of inclusiveness +and encourages cooperation between ISO and other standardizing bodies, +where such cooperation would serve to ensure effective and efficient +use of resources available for standardization activities.

+

CalConnect aims to facilitate interoperability of collaborative +technologies with open standards, in particular on calendar, scheduling, +and contacts; its standards are globally recognized and widely applied.

+

Intention

+ +

ISO and CalConnect agree to the principles of cooperation described in +this document, in all fields subject to approval by the ISO TMB and the +CalConnect TC PUBLISH and TCC.

+
+

Process cooperation

ISO and CalConnect wish to avoid duplication of efforts by their +respective committees.

+

ISO produces International Standards in accordance with processes +described in ISO 1 (all parts) and ISO 1 (all parts), with the standard documents +drafted in accordance with the editorial rules of ISO/IEC Guide 2 (all parts).

+

CalConnect creates publicly available CalConnect Standards through +a consensus-based standardization process described in CC/DIR 10001, and +standard documents created in accordance with CC/DIR 10002.

+

Both ISO and CalConnect believe that cooperation at +the standards development process level provides the following benefits:

+ +

+maximizes the deliverable expertise of their experts; and +

+

+maximizes the quality of the resulting International Standard. +

+ +

This agreement facilitates a collaborative development process +for the creation of joint publications (ISO/CalConnect Standards) +between ISO and CalConnect.

+
+

 

+
+

+
+

+
+

ISO/CalConnect Partner Standards Development Organization (PSDO) Cooperation Agreement

+
+

1.  Scope

+

This document describes the agreement between CalConnect and ISO for +the cooperation of standards development and publication.

+

Specifically, it provides the principles and necessary processes for these +collaborative cases between ISO and CalConnect (“Parties”):

+ +

+co-development of a standardization work item, proposed by either party +

+

+submission of a CalConnect document to ISO for its +standardization process +

+ +

Standardization processes in this document is intended to align +with ISO 1 (all parts), ISO 1 (all parts), CC/DIR 10001 and CC/DIR 10002.

+
+

2.  Normative references

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.

CC CC/DIR 10001, CalConnect Directive: Standardization and publication

CC CC/DIR 10002, CalConnect Directive: Standard document requirements

ISO 1 (all parts), Geometrical product specifications (GPS) – Standard reference temperature for the specification of geometrical and dimensional properties

ISO 1 (all parts), Geometrical product specifications (GPS) – Standard reference temperature for the specification of geometrical and dimensional properties

ISO/IEC Guide 2 (all parts), Standardization and related activities – General vocabulary

ISO/IEC Guide 2:2004, Standardization and related activities – General vocabulary

+
+

3.  Terms and definitions

+

For the purposes of this document, the terms and definitions + given in ISO/IEC Guide 2:2004 and the following apply.

+

3.1.  Terms and definitions

3.1.1. 

ISO members

+ +

ISO member bodies and correspondent members

+ +

3.1.2. 

CalConnect members

+ +

CalConnect member bodies

+ +

3.1.3. 

ISO committee

+

ISO TC

+ +

ISO Technical Committee (including ISO/IEC JTC1) or Subcommittee

+

3.1.4. 

CalConnect technical committee

+

CalConnect TC

+ +

internal committee of CalConnect tasked with a scope of work it +is responsible for

+

3.1.5. 

standardization project

+ +

an organized process with one or more standardization work items that +contributes towards a defined scope of work

+ +

3.1.6. 

standardization work item

+ +

publishable work item that creates output that relates +to standardization within a standardization project (Clause 3.1.5)

+ +

3.1.7. 

project owner

+ +

entity with authority in charge of a standardization project +(Clause 3.1.5)

+ +

3.1.8. 

document

+ +

written output of a work item

+ +

3.1.9. 

CalConnect deliverable

document (Clause 3.1.8) produced by a CalConnect TC +(Clause 3.1.4) as described in CC/DIR 10001

+

Note 1 to entry: According to CC/DIR 10001, CalConnect deliverables include the +following types: CalConnect Standard, Guide, Specification, Report and +Directives. Directives are not considered a standardization work item.

+

3.1.10. 

ISO TC deliverable

document (Clause 3.1.8) produced by an ISO TC +(Clause 3.1.3) as described in ISO 1 (all parts)

+

Note 1 to entry: According to ISO 1 (all parts), ISO TC deliverables include the +following types: International Standards, Technical Specifications, +Publicly Available Specifications and Technical Reports.

+

3.1.11. 

document stage

+ +

stage of document as specified in the ISO harmonized stages (as defined +in ISO 1 (all parts))

+ +

3.1.12. 

standardization project output

output of a standardization project (Clause 3.1.5)

+

Note 1 to entry: In this document, it explicitly means any documents and IP rights +produced by the standardization project.

+

3.1.13. 

proposal for standardization

+ +

proposal for a new work item for standardization

+ +

3.1.14. 

co-develop

+ +

act of developing a work item by multiple parties from the proposal stage

+ +

3.1.15. 

co-publish

+ +

act of publishing documents (Clause 3.1.8) of identical content +by multiple parties

+ +

3.1.16. 

joint work item

+ +

work item co-developed (Clause 3.1.14) by both parties

+ +

3.1.17. 

joint deliverable

+ +

completed form of a joint work item that is designated to be +co-published (Clause 3.1.15) by ISO +and CalConnect

+ +

3.1.18. 

joint publication

publication that is co-published (Clause 3.1.15) by +ISO and CalConnect

+

Note 1 to entry: Different publishers of a joint publication may utilize a +different document layout.

+

3.1.19. 

Joint Coordination Group

+

JCG

+ +

advisory group with representatives from ISO and CalConnect on +the execution and maintenance of this agreement

+

3.1.20. 

joint project group

+

JPG

+ +

group created to be project owner (Clause 3.1.7) of a joint work item (Clause 3.1.16), +composed of participants from ISO committees (Clause 3.1.3) and CalConnect TCs (Clause 3.1.4)

+

3.1.21. 

joint maintenance group

+

JMG

+ +

joint project group (Clause 3.1.20) for the sole +purpose of maintaining a +joint publication (Clause 3.1.18)

+

3.1.22. 

co-development document register

+ +

document register of a list of co-developed (Clause 3.1.14) +documents (Clause 3.1.8) developed under this agreement, +held by the Joint Coordination Group (Clause 3.1.19)

+
+

3.2.  Abbreviations

+ +

IPR

+

Intellectual Property Rights

+

TCC

+

CalConnect Technical Coordination Committee

+

TMB

+

ISO Technical Management Board

+
+
+
+
+

4.  Principles of cooperation

+

4.1.  Collaborative development process

A collaborative development process is crucial to effective development +of work items between ISO and CalConnect.

+

Both organizations agree to align appropriate internal processes +and procedures in order to facilitate joint development of work items.

+

Three mechanisms are provided below for cooperative development of +joint publications between ISO and CalConnect, namely:

+ +

+CalConnect contributes content to ISO; +

+

+ISO and CalConnect co-develop a joint deliverable; +

+

+Adoption of an existing standard from either party. +

+
+

4.2.  Central coordination group

+ +

ISO and CalConnect agree to the establishment of a joint coordination group +(JCG) to coordinate matters relevant to the execution and maintenance +of this agreement.

+
+

4.3.  Across subject fields

ISO and CalConnect agree that this agreement applies to all subject fields +subject to approval by both parties.

+

Details of implementation are provided in Clause 5.4.

+

4.4.  Normative referencing

ISO and CalConnect agree to the normative referencing of their +standards as appropriate in publications of the other organization in +compliance with each organization’s policies and directives relative to +normative references.

+

Implementation details are provided in Appendix A.1.

+

4.5.  Patent policy

ISO and CalConnect agree that content of joint deliverables, +including the ISO published form of joint publications, +will remain free of IPR restrictions that would limit their application.

+

Patented content in a joint deliverable is governed by the +ISO patent policy and the CalConnect IPR policy.

+

Any patents involved knowingly in the document shall be made +transparent prior to the DIS stage of the joint deliverable.

+

4.6.  Contributions to ISO standards

ISO International Standards are normally developed within ISO +Committees. As part of this normal development process, an ISO +committee may determine that specific elements of an CalConnect +standard (e.g. figures, data, definitions), along with information from +other sources, would contribute to the development of an ISO Standard.

+

As specified in the ISO 1 (all parts), original material contributed to +become part of an ISO publication is normally copied and distributed +within the ISO system as part of the consensus-building process, this +being without prejudice to the rights of the original copyright owner +to exploit the original text.

+

It is also recognized that, where such material is already subject to +copyright, rights have to be granted to ISO to reproduce and circulate +the material.

+

As part of this agreement, CalConnect grants a licence to ISO described +in Appendix A.2 +for using elements of a CalConnect standard in the development of joint +publications.

+

4.7.  Co-development of standards

In cases where CalConnect has developed a standard, or where CalConnect +is proposing or developing a standard (yet unpublished), which +corresponds to a stated ISO TC need covered by this agreement.

+

In these instances, the relevant ISO TC and CalConnect TC +may agree that it would be mutually beneficial to develop work jointly.

+

ISO and CalConnect agree to a coordinated and specified process for the +co-development of joint publications.

+

The detailed process and procedures are provided in Appendix C; copyright of the +resulting deliverables is explained in Appendix A.3.2.

+

4.8.  Adoption of existing standards

4.8.1.  General

ISO and CalConnect agree to a coordinated and specified process for the +adoption of either party’s standardization work items, where:

+ +

+CalConnect may wish to formally adopt a published ISO +International Standard; +

+

+CalConnect may propose that an existing CalConnect standard be +submitted as a final draft International Standard (FDIS) at ISO. +

+ +

Copyright of joint publications created through adoption is +explained in Appendix A.3.1.

+

4.8.2.  Adoption of an ISO Standard by CalConnect

CalConnect may wish to formally adopt a published ISO International +Standard.

+

In this case, the source party is ISO and the adopting party +is CalConnect.

+

The method of adoption is specified in Appendix D.2.

+

4.8.3.  Adoption of a CalConnect Standard by ISO

A published CalConnect standard with global use and acceptance may be +proposed for adoption as an ISO International Standard, through the +FDIS fast-track procedure of submitting a CalConnect standard to ISO.

+

In this case, the source party is CalConnect and the adopting party +is ISO.

+

The method of adoption is detailed in Appendix D.3.

+

4.9.  Maintenance of joint publications

Maintenance of joint publications shall be a joint responsibility under +a joint process.

+

Details of the implementation of this clause is described in Appendix E.

+

In joint publications where a maintenance agency or registration authority +is necessary, CalConnect agrees to serve as the default volunteer, as +described in Appendix E.7.

+

4.10.  Mutual recognition and joint deliverables requirements

ISO and CalConnect shall establish rules to ensure +the collaborative effort by both parties are mutually +recognized within joint deliverables.

+

The associated requirements are provided in Appendix F.

+

4.11.  Promotional activities

+ +

ISO and CalConnect agree to share and coordinate promotional activities +for the joint publication via the JCG.

+
+
+
+

5.  Joint Coordination Group

+

5.1.  General

ISO and CalConnect agrees to establish a standing body, +the Joint Coordination Group (“JCG”), for:

+ +

+maintenance and execution of this agreement; and +

+

+coordination and maintenance of procedures between two organizations. +

+
+

5.2.  Mediator for coordination issues

+ +

This group meets as necessary and serves as the forum for discussing +and resolving issues relating to coordination that may arise from time to time.

+
+

5.3.  Coordination role

The JCG will support the individual liaisons between +ISO Technical Committee working groups and project teams, +with CalConnect technical committees.

+

The presence of the JCG is not intended to affect +responsibilities of existing organizational structures +in ISO and CalConnect.

+

5.4.  Fields of collaboration

+ +

The JCG is responsible with the determination of the subject fields +of which this agreement applies to, subject to approval by +the ISO Technical Management Board and the CalConnect TC PUBLISH and TCC.

+
+

5.5.  Members

The JCG is composed of an equal number of representatives from both parties:

+ +

+Two representatives from ISO +

+

+Two representatives from CalConnect +

+
+
+
+

6.  Amendments to this agreement

+

ISO and CalConnect agree that changes to this agreement shall be +first proposed through the JCG, and formalized by a resolution from one +party to the other.

+
+

+
+

+
+

Appendix A
(normative)
Publication, copyright and commercial arrangements

+

A.1.  Normative referencing of standards

ISO and CalConnect acknowledge that all documents, +data or electronic files provided by each consisting of or relating to +joint publications are copyrighted property and data and will not be +supplied to any other party without the prior written consent of the +copyright owner, and will not be used, in whole or in part, as a basis +for a joint publication without following specific procedures established by the +respective copyright owner.

+

Each organization will promptly notify the +other if it becomes aware of infringements or imitations by others of +a joint publication.

+

A.2.  CalConnect content license for joint development

In the development, review and adoption process, ISO members are free to copy and +distribute the relevant CalConnect documents for standards development +purposes and in accordance with ISO policies for the circulation of +draft standards and working documents.

+

CalConnect grants ISO a world-wide, non-exclusive, non-sub-licensable +license (except for national body adoption), +to use contents of CalConnect submitted documents to ISO, +within the development, review and adoption process of the +deliverables under this agreement.

+

A.3.  Copyright and exploitation rights

A.3.1.  Of adopted standards

The copyright in any resulting ISO/CalConnect International Standard(s) published according to +Clause 4.8, including any future versions of such Standard(s), remain with +the source party.

+

The adopting party will neither acquire nor assert copyright ownership or any +other proprietary rights in these ISO/CalConnect International Standard(s).

+

The source party retains all copyrights in the CalConnect Product(s) and +ISO/CalConnect International Standard(s) not specifically granted +hereunder.

+

Subject to the exploitation rights granted above, development by the adopting party (or its members) +of any other work affecting the integrity of the source standard or the ISO/CalConnect International +Standard(s) would need a separate agreement with the source party.

+

A.3.2.  Of jointly developed standards

Joint deliverables developed through the joint development process according to +Clause 4.7, +copyright ownership will be held jointly by ISO +and CalConnect with normal exploitation rights for CalConnect and for +ISO and its members, including for national adoption purposes.

+

ISO and CalConnect may each sell and distribute the jointly developed standard, +in accordance with their own rules, without any royalties to the other.

+

The resulting joint publication is common to both organizations.

+

A.4.  Re-publishing

ISO and CalConnect agree that any re-publishing of content +developed under this agreement, such as the national adoption +of a joint publication by an ISO member body, or the re-publishing +of a joint publication by another organization, +will adhere to this agreement.

+

Publishing arrangements between ISO and ISO member countries are +unchanged by this agreement.

+

A.5.  Statement indicating source

+ +

ISO and CalConnect agree that the resulting publication created with +the joint deliverable will contain a suitable statement that describes +the base standard the joint deliverable was derived from.

+
+

A.6.  Notification of right infringement

Each party shall promptly inform the other party if it becomes aware of +any copyright infringement or potential infringement of a joint publication.

+

CalConnect and ISO shall consult with each other to decide the best +way to respond to such infringement.

+
+

+
+

+
+

Appendix B
(normative)
Alignment of project timeline

+

B.1.  Project stage mapping

The following table provides a mapping between ISO project stages and +CalConnect project stages. This document identifies stages +according to the ISO project stage names.

+

Table B.1 — Alignment between ISO and CalConnect project stages

Identification in this documentISO harmonized stage (ISO 1 (all parts))CalConnect stage
+Preliminary +00 Preliminary00 Preliminary
+Proposal +10 Proposal10 Proposal
+Preparatory +20 Preparatory20 Preparatory
+Committee +30 Committee30 Committee
+Enquiry +40 Enquiry40 Enquiry
+Approval +50 Approval50 Approval
+Publication +60 Publication60 Publication
+Review +90 Review90 Review
+Withdrawal +95 Withdrawal95 Withdrawal
+

B.2.  Track synchronization

ISO deliverables can be developed according to different tracks +and timelines detailed in ISO 1 (all parts) and ISO 1 (all parts).

+

CalConnect deliverables are developed according to the +timelines detailed in CC/DIR 10001.

+

For a project under this agreement, CalConnect agrees to adopt +a developmental track not slower than the track selected in +ISO to ensure the synchronicity between +development outcome and publication.

+
+

+
+

+
+

Appendix C
(normative)
Co-development process

+

C.1.  General

In joint development, technical level support for the development of +these standards is provided through the associated CalConnect TC as +well as the ISO member bodies and their duly appointed technical +experts through the relevant ISO TC.

+

Experts in ISO are encouraged to participate in the +technical work on CalConnect technologies by participating in +CalConnect technical committees.

+

C.2.  First draft

A first draft of the standardization deliverable may be created +for proposal submission, or may be created in the Committee stage. +The draft shall be created through a collaboration process between +experts from both organizations, or at least, the proposing +organization should have received input from the other organization.

+

CalConnect agrees that any draft submitted to ISO +shall adhere to the requirements detailed in CC/DIR 10002, ISO/IEC Guide 2 (all parts) and +applicable internal guidelines of ISO.

+

C.3.  Disapproval and continuance

If the project proposal is rejected by the JCG, its output may still be +developed by the project proposer if appropriate, and its output may +still be proposed to the JCG for co-development in later stages.

+

At any time, if a ballot to approve the development of a joint work item +is disapproved by ISO or CalConnect, each organization may proceed +to develop the joint work item independently of each other.

+

C.4.  Proposal development: Preliminary stage

C.4.1.  General

At the first instance where either party wishes to co-develop +a project with the other party, it should be raised to the JCG.

+

The JCG shall consult the stakeholders to determine appropriateness +of the project and advise the proposer.

+

C.4.2.  Initiation by CalConnect

+ +

CalConnect may propose to the appropriate ISO TC(s) to +jointly develop a new or existing CalConnect standard +to gain recognition as an ISO/CalConnect Standard.

+
+

C.4.3.  Initiation by ISO TC

+ +

If an ISO TC wishes to initiate the joint development of a +standard, the ISO TC secretariat shall contact the appropriate +CalConnect TC to gauge mutual interest.

+
+

C.5.  Proposal submission: Proposal stage

C.5.1.  General

+ +

When the JCG determines interest within ISO to co-develop the +proposed project, the project proposer should submit a proposal +indicating its wish to co-develop the proposed project, +to be approved by the relevant ISO and CalConnect TCs via ballot.

+
+

C.5.2.  Initiation by CalConnect

CalConnect shall provide a NWIP in accordance with ISO 1 (all parts) for the +proposal of new work items.

+

In addition, the NWIP shall include:

+ +

+rationale for using this process; and +

+

+justification of the need for an ISO/CalConnect International +Standard. +

+
+

C.5.3.  Initiation by ISO TC

An ISO member shall submit a NWIP to the ISO TC for approval +in accordance with ISO 1 (all parts).

+

Concurrently, the corresponding CalConnect TC will submit a +project proposal to the CalConnect TCC, providing the relevant +information for the project and a statement that the project +is to be developed jointly with the relevant ISO TC.

+

C.5.4.  Fast-track proposal at ISO

When the ISO NWIP is accompanied by an existing CalConnect standard, +members of the ISO TC will be invited to approve its submission as a DIS.

+

NOTE  A two-thirds (2/3) majority vote of participating ISO P-members +is required for approval (ISO 1 (all parts)).

+

C.5.5.  Approval of co-development

If both organizations approve the proposal for joint development, +the project shall be adopted on both sides by a CalConnect +TC and an ISO TC.

+

The JCG shall then create a joint project group to be the project +owner of the proposed joint work item through the CalConnect TCC and the +secretariat of the ISO TC, consisting of nominated experts from the +relevant CalConnect and ISO TCs.

+

ISO and CalConnect will mutually agree on a Convener for the JPG.

+

This approved project shall be listed in the JCG register of +co-developed projects.

+

C.6.  Content development: Preparatory, Committee, Enquiry stages

C.6.1.  General

The goal of these stages are to create an approved, balloted +draft of the joint deliverable by both parties.

+

In these stages, members of the joint project group shall +collaborate closely to ensure efficient and effective +development of the deliverable of the respective stages. +The deliverable shall be developed jointly by experts of +both organizations.

+

C.6.2.  Stage synchronization

The approval process at CalConnect and ISO shall be adhered to. +CalConnect agrees to synchronize its project stage with +the corresponding ISO project stage.

+

Specifically:

+ +

+If a deliverable is approved by ballot at both ISO and CalConnect, +CalConnect will advance the project stage at its +project group accordingly. +

+

+If a deliverable is rejected by ballot at either party, +CalConnect will not advance project stage at its +project group, unless a re-ballot at ISO approves +advancement of the deliverable. +

+

+In cases where a development stage is optional and skipped +in accordance with ISO 1 (all parts) and ISO 1 (all parts), CalConnect +shall set the stage of its project at the corresponding +stage. +

+
+

C.6.3.  Approval of a committee draft

Once consensus is reached within the JPG, the draft is circulated to +the relevant ISO and CalConnect TCs for three-month comment.

+

The JPG prepares a compilation of comments received from both +organizations and develops a revised draft.

+

C.6.4.  Approval of a draft standard

Once consensus within the JPG is achieved, the draft is provided to ISO +for DIS ballot and CalConnect for DS ballot.

+

Once balloting and approval at that stage, from both organizations, is +completed, the JPG prepares the document for circulation by ISO for a +two-month FDIS vote (according to ISO 1 (all parts), unanimous approval in +ISO during DIS ballot implies that a further FDIS ballot is not +necessary).

+

In parallel, CalConnect submits the draft to the CalConnect TCC for FS +ballot.

+

C.6.5.  Approval for publication

The document is considered approved when:

+ +

+ISO achieves the requisite FDIS approval (or unanimous DIS approval), +in accordance with ISO 1 (all parts), and; +

+

+CalConnect TCC has provided its requisite approval, in accordance +with CC/DIR 10001. +

+ +

Once the document has been approved by both ISO and CalConnect, the +document is published as a joint ISO/CalConnect standard.

+

C.7.  Pre-publication: Public review

A public review period of 60 days is required for the compliance +to WTO TBT Agreements rules, for which both ISO and CalConnect adhere to.

+

A 60-day public review shall be held in the DIS stage of the ISO deliverable.

+

Comments to ISO shall be performed according to ISO 1 (all parts) and ISO 1 (all parts); +comments to CalConnect shall be performed through CalConnect’s public review procedure.

+

The parties agree to synchronize the dates of review periods for the +maximum benefit to the joint work item.

+

C.8.  Publication

C.8.1.  As a CalConnect Standard

+ +

After an ISO ballot on the acceptance of a joint work item as +DIS, FDIS or IS, the joint work item will be published +as a CalConnect Standard.

+
+

C.8.2.  As an ISO/CalConnect Standard

+ +

After an ISO ballot on the acceptance of a joint work item’s status +to proceed to IS from FDIS, the joint work item will be published by +ISO and CalConnect as an ISO/CalConnect Standard.

+
+

C.9.  Abandonment

A joint work item may be abandoned by one of the two parties if it sees +it being inappropriate or is no longer interested or able to contribute +to the joint work item. Each party is allowed to abandon the joint +work, which at that point will become sole work of the other party.

+

A notice of such must be sent by the abandoning party to the JCG and +distributed by both parties to its members.

+

The abandoning party, if the abandoned work is carried on by the other +party, is required to explicitly agree that the copyright of such work +is to be waived to the continuing party to allow publication of the document.

+

The rejoining an abandoned work item prior to publication, by the abandoning party, +is explicitly allowed by this agreement, given a notice is filed at +the JCG, unless in exceptional circumstances.

+

C.10.  Additional collaborators

+ +

Parties may bring in additional collaborators under this agreement, +given it is approved by the JCG, that the provisions of this agreement +are fully satisfied by agreements present between all collaborators.

+
+

C.11.  Notification

+ +

Notification of availability of new documents within CalConnect +will be announced to the appropriate ISO TCs and CalConnect TCs.

+
+

C.12.  Availability of working documents

+ +

Drafts and working documents are available according to +each party’s normal practices.

+
+
+

+
+

+
+

Appendix D
(normative)
Adoption process

+

D.1.  General

ISO and CalConnect agree to a coordinated and specified process for the +adoption of either party’s standardization work items, where:

+ +

+CalConnect may wish to formally adopt a published ISO International Standard; +

+

+CalConnect may propose that an existing CalConnect standard be +submitted as a final draft International Standard (FDIS) at ISO. +

+
+

D.2.  Adoption of an ISO Standard by CalConnect

CalConnect may wish to formally adopt a published ISO International +Standard as described in Clause 4.8.2,

+

Such adoption shall be subject to an agreement between CalConnect and +the ISO member body in the country where CalConnect has its legal seat +(ANSI).

+

D.3.  Adoption of a CalConnect Standard by ISO

D.3.1.  General

As described in Clause 4.8.3, a CalConnect +standard may be adopted by ISO.

+

The adoption of a CalConnect standard at ISO is through FDIS fast-track +as described in this clause.

+

Adoption by ISO FDIS approval is intended to validate an existing +CalConnect standard through ISO’s established member body approval +mechanism.

+

D.3.2.  Initiation by CalConnect

CalConnect may propose an existing CalConnect standard to be submitted +as a final draft International Standard (FDIS) at ISO.

+

Such requests shall be submitted to the Secretary-General of ISO for +acceptance.

+

The ISO Secretary-General shall then submit a proposal to the relevant +ISO committee for a 30-day ballot which shall decide, by simple majority +vote, on:

+ +

+the need for an ISO International Standard on the subject; and +

+

+submission of the proposal for FDIS ballot. +

+
+

D.3.3.  Initiation by ISO

Any ISO TC may decide to invite, by simple majority vote, CalConnect to +offer a particular CalConnect standard for adoption under this +agreement, provided agreement has been obtained from CalConnect.

+

Where an ISO TC confirms the need for an ISO International Standard, +but determines that the proposed CalConnect standard should not be +submitted for FDIS ballot, CalConnect shall be consulted on its +interest to proceed with the project jointly.

+

D.3.4.  Approval

Requirements for acceptance shall be those pertaining to the FDIS +approval stage in ISO 1 (all parts).

+

Upon acceptance by CalConnect and the relevant ISO TC, the CalConnect +standard shall be circulated to ISO members for a five-month approval +vote (to also allow for national public review and, where necessary, +translation).

+

The adoption is considered approved once the FDIS ballot is approved.

+

The process described in Appendix C.8.2 also applies.

+
+

+
+

+
+

Appendix E
(normative)
Maintenance of joint deliverables

+

E.1.  General

The project groups in both organizations responsible for +the published deliverable shall work in collaboration to +address any corrections or necessary amendments.

+

The intention is to coordinate the initiation of revisions and to +maintain, to the greatest extent possible, one common ISO/CalConnect +Standard on a given subject.

+

When a joint deliverable is deemed to be updated, both parties agree that each +other has the first right of refusal.

+

The revisions shall be published jointly as described +in Appendix C.8.

+

E.2.  Systematic review and outcome

Joint publications that have been published for four (4) years since +their last approval date shall be reviewed in their entirety by the +responsible JMG, as determined by the JCG.

+

A decision shall be made by both parties at the end of the review +period, on whether to:

+ +

+confirm the standard, for which no change is necessary; +

+

+revise, as a new joint work item; or +

+

+withdraw the standard. +

+ +

The decided action shall be initiated within five (5) years of the last +approval date.

+

NOTE  The four (4) years review period provides a one (1) year +timeframe for which a review decision can be made, in accordance with +ISO 1 (all parts) and CC/DIR 10001 where a maximum of five (5) years is +allowed between reviews.

+

E.3.  Participation

E.3.1.  Agree to jointly maintain

When both the ISO TC and CalConnect agree to jointly revise the +standard, a joint maintenance group (JMG) is established consisting of +nominated experts from the relevant CalConnect and ISO TCs.

+

ISO and CalConnect mutually agree on a Convener for the MG.

+

E.3.2.  Non-participation of ISO TC

If CalConnect initiates revision to the document and the relevant ISO +TC decides not to participate in the revision process, ISO shall ensure +that the ISO/CalConnect Standard is not revised until CalConnect has +completed its revision.

+

Once the document has been revised, CalConnect may submit the document +to ISO as a potential new Standard for FDIS fast-track approval to +supercede the earlier ISO/CalConnect Standard.

+

Should the revised document not be submitted by CalConnect, or accepted +by the relevant ISO Committee, the original ISO FDIS fast track +Standard shall be withdrawn, unless otherwise agreed by both +organizations.

+

E.3.3.  Non-participation of CalConnect

If ISO initiates the revision and CalConnect decides not to participate +in the process, then ISO may continue to revise the Standard.

+

However, any material used from the original ISO/CalConnect Standard +will require a separate agreement with CalConnect.

+

E.4.  Comment distribution

+ +

When a party receives formal comments on the joint work item, it shall +share it with the other party within 2 weeks of receiving them, +documented and distributed through the JCG.

+
+

E.5.  Withdrawal

+ +

When a review determines that a joint published item should be +withdrawn, both parties agree that the item to be indicated as +withdrawn.

+
+

E.6.  Revision of deliverables

E.6.1.  Initiation of revision process

+ +

Revisions to joint publications can be proposed to the relevant +CalConnect or ISO TC at any time by members of CalConnect or the +ISO TC.

+
+

E.6.2.  Amendments and full revisions

+ +

Amendments and full revisions of a joint deliverable +are considered joint new work items, and shall be developed in +accordance with the procedures in Appendix C.

+
+

E.6.3.  Corrections

+ +

Corrections, such as technical corrigenda, of an ISO/CalConnect +standard, shall be jointly developed by the appropriate ISO TC +and CalConnect TC in accordance with each organizations’ internal +procedures.

+
+

E.7.  Maintenance agency and registration authority

+ +
+

E.8.  General

+ +

Both organizations recognize that a maintenance agency or +registration authority is required for the successful implementation of +certain standardization deliverables resulting from this agreement.

+
+

E.9.  Default volunteer role

For standards developed under this agreement, CalConnect volunteers +to serve as their maintenance agency or registration authority as +necessary.

+

CalConnect shall submit a suitable application to ISO once a NWIP +requiring establishment of a maintenance agency or registration +authority for a joint work item is approved.

+
+

+
+

+
+

Appendix F
(normative)
Deliverable requirements

+

F.1.  Document layout

+ +

CalConnect and ISO will establish a consistent layout, including +associated supporting information (e.g. foreword, introduction), for +joint publications.

+
+

F.2.  Trademark and copyright statements

+ +

Similar to the process applied on national adoption +of an ISO deliverable, trademarks and copyright statements +of both organizations shall appear on the document cover page as +well as in the foreword.

+
+

F.3.  Patent statement

+ +

A suitable patent statement in accordance with the ISO patent policy +and the CalConnect patent policy shall be stated in the foreword +of the document.

+
+

F.4.  Publication dates

+ +

The edition year and the year of publishing of a joint deliverable +shall be identical in the ISO and CalConnect deliverables.

+
+

F.5.  Cover page

In ISO and CalConnect publications of the joint publication, +as well as any further adoptions, shall retain the logographic marks +of both organizations.

+

The joint publication shall also provide a single document identifier +on the cover page.

+

F.6.  Introduction part

+ +

The introduction shall state that it is a joint work product +between ISO and CalConnect.

+
+

F.7.  Document identifier and references

ISO publications published through joint publication under this +agreement will be referenced with the following prefixes:

+ +

+“ISO/CC” in ISO documents +

+

+“CC/ISO” in CalConnect documents +

+ +

In case that a joint publication is performed under ISO/IEC JTC 1, +the resulting prefixes are:

+ +

+“ISO/IEC/CC” in ISO and IEC documents; +

+

+“CC/ISO/IEC” in CalConnect documents +

+ +

References shall contain sufficient information for those wishing +to obtain the equivalent documents of the other party to be +able to do so.

+

EXAMPLE 1

+

In the document identifier “ISO/CC 18001:2018”, “ISO/CC” is the prefix, +“18001” the project code, and “2018” the edition date.

+
+

EXAMPLE 2

+

In the document identifier “ISO/IEC/CC 28001:2018”, “ISO/IEC/CC” is the +prefix, “28001” the project code, and “2018” the edition date.

+
+

F.8.  Project code

A mutually acceptable number will be used for the project code, with +the goal of achieving identical deliverable numbers in ISO and +CalConnect to prevent potential ambiguity.

+

ISO and CalConnect shall also give consideration to any previous numbering +used by ISO or CalConnect to determine the number designation for the +Standards developed in accordance with this agreement.

+

F.9.  Editorial work

ISO and CalConnect will perform final editorial/production work on the +joint work item with approval of the final proof by both parties prior +to ISO publication.

+

CalConnect and ISO will not charge each other for any editing or +production work undertaken in development of the final +ISO/CalConnect Standard.

+
+

+
+

+

Bibliography

+

[1]  WTO TBT Agreements, World Trade Organization, The WTO Agreements Series Technical Barriers to Trade

+ +
+
+
+ + + +------=_NextPart_86bf3968.c2a0.4313 +Content-Location: file:///C:/Doc/cc-10010_files/filelist.xml +Content-Transfer-Encoding: base64 +Content-Type: application/xml + +PHhtbCB4bWxuczpvPSJ1cm46c2NoZW1hcy1taWNyb3NvZnQtY29tOm9mZmljZTpvZmZpY2UiPgog +ICAgICAgIDxvOk1haW5GaWxlIEhSZWY9Ii4uL2RvY3VtZW50cy9jYy0xMDAxMC5odG0iLz4gIDxv +OkZpbGUgSFJlZj0iZmlsZWxpc3QueG1sIi8+CiAgPG86RmlsZSBIUmVmPSJoZWFkZXIuaHRtbCIv +Pgo8L3htbD4K + +------=_NextPart_86bf3968.c2a0.4313 +Content-Location: file:///C:/Doc/cc-10010_files/header.html +Content-Transfer-Encoding: base64 +Content-Type: text/html charset="utf-8" + +PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiDQp4bWxuczpvPSJ1 +cm46c2NoZW1hcy1taWNyb3NvZnQtY29tOm9mZmljZTpvZmZpY2UiDQp4bWxuczp3PSJ1cm46c2No +ZW1hcy1taWNyb3NvZnQtY29tOm9mZmljZTp3b3JkIg0KeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMu +bWljcm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIg0KeG1sbnM6bXY9Imh0dHA6Ly9tYWNW +bWxTY2hlbWFVcmkiIHhtbG5zPSJodHRwOi8vd3d3LnczLm9yZy9UUi9SRUMtaHRtbDQwIj4NCg0K +PGhlYWQ+DQo8bWV0YSBuYW1lPVRpdGxlIGNvbnRlbnQ9IiI+DQo8bWV0YSBuYW1lPUtleXdvcmRz +IGNvbnRlbnQ9IiI+DQo8bWV0YSBodHRwLWVxdWl2PUNvbnRlbnQtVHlwZSBjb250ZW50PSJ0ZXh0 +L2h0bWw7IGNoYXJzZXQ9dXRmLTgiPg0KPG1ldGEgbmFtZT1Qcm9nSWQgY29udGVudD1Xb3JkLkRv +Y3VtZW50Pg0KPG1ldGEgbmFtZT1HZW5lcmF0b3IgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUi +Pg0KPG1ldGEgbmFtZT1PcmlnaW5hdG9yIGNvbnRlbnQ9Ik1pY3Jvc29mdCBXb3JkIDE1Ij4NCjxs +aW5rIGlkPU1haW4tRmlsZSByZWw9TWFpbi1GaWxlIGhyZWY9Ii4uL2RvY3VtZW50cy9jYy0xMDAx +MC5odG1sIj4NCjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0KIDxvOnNoYXBlZGVmYXVsdHMgdjpl +eHQ9ImVkaXQiIHNwaWRtYXg9IjIwNDkiLz4NCjwveG1sPjwhW2VuZGlmXS0tPg0KPC9oZWFkPg0K +DQo8Ym9keSBsYW5nPUVOIGxpbms9Ymx1ZSB2bGluaz0iIzk1NEY3MiI+DQoNCjxkaXYgc3R5bGU9 +J21zby1lbGVtZW50OmZvb3Rub3RlLXNlcGFyYXRvcicgaWQ9ZnM+DQoNCjxwIGNsYXNzPU1zb05v +cm1hbCBzdHlsZT0nbWFyZ2luLWJvdHRvbTowY207bWFyZ2luLWJvdHRvbTouMDAwMXB0O2xpbmUt +aGVpZ2h0Og0Kbm9ybWFsJz48c3BhbiBsYW5nPUVOLUdCPjxzcGFuIHN0eWxlPSdtc28tc3BlY2lh +bC1jaGFyYWN0ZXI6Zm9vdG5vdGUtc2VwYXJhdG9yJz48IVtpZiAhc3VwcG9ydEZvb3Rub3Rlc10+ +DQoNCjxociBhbGlnbj1sZWZ0IHNpemU9MSB3aWR0aD0iMzMlIj4NCg0KPCFbZW5kaWZdPjwvc3Bh +bj48L3NwYW4+PC9wPg0KDQo8L2Rpdj4NCg0KPGRpdiBzdHlsZT0nbXNvLWVsZW1lbnQ6Zm9vdG5v +dGUtY29udGludWF0aW9uLXNlcGFyYXRvcicgaWQ9ZmNzPg0KDQo8cCBjbGFzcz1Nc29Ob3JtYWwg +c3R5bGU9J21hcmdpbi1ib3R0b206MGNtO21hcmdpbi1ib3R0b206LjAwMDFwdDtsaW5lLWhlaWdo +dDoNCm5vcm1hbCc+PHNwYW4gbGFuZz1FTi1HQj48c3BhbiBzdHlsZT0nbXNvLXNwZWNpYWwtY2hh +cmFjdGVyOmZvb3Rub3RlLWNvbnRpbnVhdGlvbi1zZXBhcmF0b3InPjwhW2lmICFzdXBwb3J0Rm9v +dG5vdGVzXT4NCg0KPGhyIGFsaWduPWxlZnQgc2l6ZT0xPg0KDQo8IVtlbmRpZl0+PC9zcGFuPjwv +c3Bhbj48L3A+DQoNCjwvZGl2Pg0KDQo8ZGl2IHN0eWxlPSdtc28tZWxlbWVudDplbmRub3RlLXNl +cGFyYXRvcicgaWQ9ZXM+DQoNCjxwIGNsYXNzPU1zb05vcm1hbCBzdHlsZT0nbWFyZ2luLWJvdHRv +bTowY207bWFyZ2luLWJvdHRvbTouMDAwMXB0O2xpbmUtaGVpZ2h0Og0Kbm9ybWFsJz48c3BhbiBs +YW5nPUVOLUdCPjxzcGFuIHN0eWxlPSdtc28tc3BlY2lhbC1jaGFyYWN0ZXI6Zm9vdG5vdGUtc2Vw +YXJhdG9yJz48IVtpZiAhc3VwcG9ydEZvb3Rub3Rlc10+DQoNCjxociBhbGlnbj1sZWZ0IHNpemU9 +MSB3aWR0aD0iMzMlIj4NCg0KPCFbZW5kaWZdPjwvc3Bhbj48L3NwYW4+PC9wPg0KDQo8L2Rpdj4N +Cg0KPGRpdiBzdHlsZT0nbXNvLWVsZW1lbnQ6ZW5kbm90ZS1jb250aW51YXRpb24tc2VwYXJhdG9y +JyBpZD1lY3M+DQoNCjxwIGNsYXNzPU1zb05vcm1hbCBzdHlsZT0nbWFyZ2luLWJvdHRvbTowY207 +bWFyZ2luLWJvdHRvbTouMDAwMXB0O2xpbmUtaGVpZ2h0Og0Kbm9ybWFsJz48c3BhbiBsYW5nPUVO +LUdCPjxzcGFuIHN0eWxlPSdtc28tc3BlY2lhbC1jaGFyYWN0ZXI6Zm9vdG5vdGUtY29udGludWF0 +aW9uLXNlcGFyYXRvcic+PCFbaWYgIXN1cHBvcnRGb290bm90ZXNdPg0KDQo8aHIgYWxpZ249bGVm +dCBzaXplPTE+DQoNCjwhW2VuZGlmXT48L3NwYW4+PC9zcGFuPjwvcD4NCg0KPC9kaXY+DQoNCjxk +aXYgc3R5bGU9J21zby1lbGVtZW50OmhlYWRlcicgaWQ9ZWgxPg0KPHAgY2xhc3M9TXNvSGVhZGVy +IGFsaWduPWxlZnQgc3R5bGU9J3RleHQtYWxpZ246bGVmdDtsaW5lLWhlaWdodDoxMi4wcHQ7DQpt +c28tbGluZS1oZWlnaHQtcnVsZTpleGFjdGx5Jz48c3BhbiBsYW5nPUVOLUdCPkNDJm5ic3A7Q0Mv +RkRTIDEwMDEwOjIwMTk6MjAxOTwvc3Bhbj48L3A+DQo8L2Rpdj4NCg0KPGRpdiBzdHlsZT0nbXNv +LWVsZW1lbnQ6aGVhZGVyJyBpZD1oMT4NCg0KPHAgY2xhc3M9TXNvSGVhZGVyIHN0eWxlPSdtYXJn +aW4tYm90dG9tOjE4LjBwdCc+PHNwYW4gbGFuZz1FTi1HQg0Kc3R5bGU9J2ZvbnQtc2l6ZToxMC4w +cHQ7bXNvLWJpZGktZm9udC1zaXplOjExLjBwdDtmb250LXdlaWdodDpub3JtYWwnPsKpDQpUaGUg +Q2FsZW5kYXJpbmcgYW5kIFNjaGVkdWxpbmcgQ29uc29ydGl1bSwgSW5jLiZuYnNwOzIwMTkmbmJz +cDvigJMgQWxsIHJpZ2h0cyByZXNlcnZlZDwvc3Bhbj48c3BhbiBsYW5nPUVOLUdCDQpzdHlsZT0n +Zm9udC13ZWlnaHQ6bm9ybWFsJz48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQoNCjwvZGl2Pg0KDQo8 +ZGl2IHN0eWxlPSdtc28tZWxlbWVudDpmb290ZXInIGlkPWVmMT4NCg0KPHAgY2xhc3M9TXNvRm9v +dGVyIHN0eWxlPSdtYXJnaW4tdG9wOjEyLjBwdDtsaW5lLWhlaWdodDoxMi4wcHQ7bXNvLWxpbmUt +aGVpZ2h0LXJ1bGU6DQpleGFjdGx5Jz48IS0tW2lmIHN1cHBvcnRGaWVsZHNdPjxiIHN0eWxlPSdt +c28tYmlkaS1mb250LXdlaWdodDpub3JtYWwnPjxzcGFuDQpsYW5nPUVOLUdCIHN0eWxlPSdmb250 +LXNpemU6MTAuMHB0O21zby1iaWRpLWZvbnQtc2l6ZToxMS4wcHQnPjxzcGFuDQpzdHlsZT0nbXNv +LWVsZW1lbnQ6ZmllbGQtYmVnaW4nPjwvc3Bhbj48c3Bhbg0Kc3R5bGU9J21zby1zcGFjZXJ1bjp5 +ZXMnPsKgPC9zcGFuPlBBR0U8c3BhbiBzdHlsZT0nbXNvLXNwYWNlcnVuOnllcyc+wqDCoA0KPC9z +cGFuPlwqIE1FUkdFRk9STUFUIDxzcGFuIHN0eWxlPSdtc28tZWxlbWVudDpmaWVsZC1zZXBhcmF0 +b3InPjwvc3Bhbj48L3NwYW4+PC9iPjwhW2VuZGlmXS0tPjxiDQpzdHlsZT0nbXNvLWJpZGktZm9u +dC13ZWlnaHQ6bm9ybWFsJz48c3BhbiBsYW5nPUVOLUdCIHN0eWxlPSdmb250LXNpemU6MTAuMHB0 +Ow0KbXNvLWJpZGktZm9udC1zaXplOjExLjBwdCc+PHNwYW4gc3R5bGU9J21zby1uby1wcm9vZjp5 +ZXMnPjI8L3NwYW4+PC9zcGFuPjwvYj48IS0tW2lmIHN1cHBvcnRGaWVsZHNdPjxiDQpzdHlsZT0n +bXNvLWJpZGktZm9udC13ZWlnaHQ6bm9ybWFsJz48c3BhbiBsYW5nPUVOLUdCIHN0eWxlPSdmb250 +LXNpemU6MTAuMHB0Ow0KbXNvLWJpZGktZm9udC1zaXplOjExLjBwdCc+PHNwYW4gc3R5bGU9J21z +by1lbGVtZW50OmZpZWxkLWVuZCc+PC9zcGFuPjwvc3Bhbj48L2I+PCFbZW5kaWZdLS0+PHNwYW4N +Cmxhbmc9RU4tR0Igc3R5bGU9J2ZvbnQtc2l6ZToxMC4wcHQ7bXNvLWJpZGktZm9udC1zaXplOjEx +LjBwdCc+PHNwYW4NCnN0eWxlPSdtc28tdGFiLWNvdW50OjEnPsKgwqDCoMKgwqDCoMKgwqDCoMKg +wqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDC +oMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKg +wqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDC +oMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKg +wqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDC +oMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqAgPC9zcGFuPsKpDQpUaGUgQ2FsZW5k +YXJpbmcgYW5kIFNjaGVkdWxpbmcgQ29uc29ydGl1bSwgSW5jLiZuYnNwOzIwMTkmbmJzcDvigJMg +QWxsIHJpZ2h0cyByZXNlcnZlZDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCg0KPC9kaXY+DQoNCjxk +aXYgc3R5bGU9J21zby1lbGVtZW50OmhlYWRlcicgaWQ9ZWgyPg0KPHAgY2xhc3M9TXNvSGVhZGVy +IGFsaWduPWxlZnQgc3R5bGU9J3RleHQtYWxpZ246bGVmdDtsaW5lLWhlaWdodDoxMi4wcHQ7DQpt +c28tbGluZS1oZWlnaHQtcnVsZTpleGFjdGx5Jz48c3BhbiBsYW5nPUVOLUdCPlRoZSBDYWxlbmRh +cmluZyBhbmQgU2NoZWR1bGluZyBDb25zb3J0aXVtLCBJbmMuJm5ic3A7Q0MvRkRTIDEwMDEwOjIw +MTk6MjAxOTwvc3Bhbj48L3A+DQo8L2Rpdj4NCg0KPGRpdiBzdHlsZT0nbXNvLWVsZW1lbnQ6aGVh +ZGVyJyBpZD1laDJsPg0KPHAgY2xhc3M9TXNvSGVhZGVyTGFuZHNjYXBlIGFsaWduPWxlZnQgc3R5 +bGU9J3RleHQtYWxpZ246bGVmdDtsaW5lLWhlaWdodDoxMi4wcHQ7DQptc28tbGluZS1oZWlnaHQt +cnVsZTpleGFjdGx5Jz48c3BhbiBsYW5nPUVOLUdCPlRoZSBDYWxlbmRhcmluZyBhbmQgU2NoZWR1 +bGluZyBDb25zb3J0aXVtLCBJbmMuJm5ic3A7Q0MvRkRTIDEwMDEwOjIwMTk6MjAxOTwvc3Bhbj48 +L3A+DQo8L2Rpdj4NCg0KPGRpdiBzdHlsZT0nbXNvLWVsZW1lbnQ6aGVhZGVyJyBpZD1oMj4NCjxw +IGNsYXNzPU1zb0hlYWRlciBhbGlnbj1yaWdodCBzdHlsZT0ndGV4dC1hbGlnbjpyaWdodDtsaW5l +LWhlaWdodDoxMi4wcHQ7DQptc28tbGluZS1oZWlnaHQtcnVsZTpleGFjdGx5Jz48c3BhbiBsYW5n +PUVOLUdCPlRoZSBDYWxlbmRhcmluZyBhbmQgU2NoZWR1bGluZyBDb25zb3J0aXVtLCBJbmMuJm5i +c3A7Q0MvRkRTIDEwMDEwOjIwMTk6MjAxOTwvc3Bhbj48L3A+DQo8L2Rpdj4NCg0KPGRpdiBzdHls +ZT0nbXNvLWVsZW1lbnQ6aGVhZGVyJyBpZD1oMmw+DQo8cCBjbGFzcz1Nc29IZWFkZXJMYW5kc2Nh +cGUgYWxpZ249cmlnaHQgc3R5bGU9J3RleHQtYWxpZ246cmlnaHQ7bGluZS1oZWlnaHQ6MTIuMHB0 +Ow0KbXNvLWxpbmUtaGVpZ2h0LXJ1bGU6ZXhhY3RseSc+PHNwYW4gbGFuZz1FTi1HQj5UaGUgQ2Fs +ZW5kYXJpbmcgYW5kIFNjaGVkdWxpbmcgQ29uc29ydGl1bSwgSW5jLiZuYnNwO0NDL0ZEUyAxMDAx +MDoyMDE5OjIwMTk8L3NwYW4+PC9wPg0KPC9kaXY+DQoNCjxkaXYgc3R5bGU9J21zby1lbGVtZW50 +OmZvb3RlcicgaWQ9ZWYyPg0KPHAgY2xhc3M9TXNvRm9vdGVyIHN0eWxlPSdsaW5lLWhlaWdodDox +Mi4wcHQ7bXNvLWxpbmUtaGVpZ2h0LXJ1bGU6ZXhhY3RseSc+PCEtLVtpZiBzdXBwb3J0RmllbGRz +XT48c3Bhbg0KbGFuZz1FTi1HQiBzdHlsZT0nZm9udC1zaXplOjEwLjBwdDttc28tYmlkaS1mb250 +LXNpemU6MTEuMHB0Jz48c3Bhbg0Kc3R5bGU9J21zby1lbGVtZW50OmZpZWxkLWJlZ2luJz48L3Nw +YW4+PHNwYW4NCnN0eWxlPSdtc28tc3BhY2VydW46eWVzJz7CoDwvc3Bhbj5QQUdFPHNwYW4gc3R5 +bGU9J21zby1zcGFjZXJ1bjp5ZXMnPsKgwqANCjwvc3Bhbj5cKiBNRVJHRUZPUk1BVCA8c3BhbiBz +dHlsZT0nbXNvLWVsZW1lbnQ6ZmllbGQtc2VwYXJhdG9yJz48L3NwYW4+PC9zcGFuPjwhW2VuZGlm +XS0tPjxzcGFuDQpsYW5nPUVOLUdCIHN0eWxlPSdmb250LXNpemU6MTAuMHB0O21zby1iaWRpLWZv +bnQtc2l6ZToxMS4wcHQnPjxzcGFuDQpzdHlsZT0nbXNvLW5vLXByb29mOnllcyc+aWk8L3NwYW4+ +PC9zcGFuPjwhLS1baWYgc3VwcG9ydEZpZWxkc10+PHNwYW4NCmxhbmc9RU4tR0Igc3R5bGU9J2Zv +bnQtc2l6ZToxMC4wcHQ7bXNvLWJpZGktZm9udC1zaXplOjExLjBwdCc+PHNwYW4NCnN0eWxlPSdt +c28tZWxlbWVudDpmaWVsZC1lbmQnPjwvc3Bhbj48L3NwYW4+PCFbZW5kaWZdLS0+PHNwYW4gbGFu +Zz1FTi1HQg0Kc3R5bGU9J2ZvbnQtc2l6ZToxMC4wcHQ7bXNvLWJpZGktZm9udC1zaXplOjExLjBw +dCc+PHNwYW4gc3R5bGU9J21zby10YWItY291bnQ6DQoxJz7CoMKgwqDCoMKgwqDCoMKgwqDCoMKg +wqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDC +oMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKg +wqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDC +oMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKg +wqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDC +oMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgIDwvc3Bhbj7CqQ0KVGhlIENhbGVuZGFy +aW5nIGFuZCBTY2hlZHVsaW5nIENvbnNvcnRpdW0sIEluYy4mbmJzcDsyMDE5Jm5ic3A74oCTIEFs +bCByaWdodHMgcmVzZXJ2ZWQ8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCg0KPGRpdiBz +dHlsZT0nbXNvLWVsZW1lbnQ6Zm9vdGVyJyBpZD1lZjJsPg0KPHAgY2xhc3M9TXNvRm9vdGVyTGFu +ZHNjYXBlIHN0eWxlPSdsaW5lLWhlaWdodDoxMi4wcHQ7bXNvLWxpbmUtaGVpZ2h0LXJ1bGU6ZXhh +Y3RseSc+PCEtLVtpZiBzdXBwb3J0RmllbGRzXT48c3Bhbg0KbGFuZz1FTi1HQiBzdHlsZT0nZm9u +dC1zaXplOjEwLjBwdDttc28tYmlkaS1mb250LXNpemU6MTEuMHB0Jz48c3Bhbg0Kc3R5bGU9J21z +by1lbGVtZW50OmZpZWxkLWJlZ2luJz48L3NwYW4+PHNwYW4NCnN0eWxlPSdtc28tc3BhY2VydW46 +eWVzJz7CoDwvc3Bhbj5QQUdFPHNwYW4gc3R5bGU9J21zby1zcGFjZXJ1bjp5ZXMnPsKgwqANCjwv +c3Bhbj5cKiBNRVJHRUZPUk1BVCA8c3BhbiBzdHlsZT0nbXNvLWVsZW1lbnQ6ZmllbGQtc2VwYXJh +dG9yJz48L3NwYW4+PC9zcGFuPjwhW2VuZGlmXS0tPjxzcGFuDQpsYW5nPUVOLUdCIHN0eWxlPSdm +b250LXNpemU6MTAuMHB0O21zby1iaWRpLWZvbnQtc2l6ZToxMS4wcHQnPjxzcGFuDQpzdHlsZT0n +bXNvLW5vLXByb29mOnllcyc+aWk8L3NwYW4+PC9zcGFuPjwhLS1baWYgc3VwcG9ydEZpZWxkc10+ +PHNwYW4NCmxhbmc9RU4tR0Igc3R5bGU9J2ZvbnQtc2l6ZToxMC4wcHQ7bXNvLWJpZGktZm9udC1z +aXplOjExLjBwdCc+PHNwYW4NCnN0eWxlPSdtc28tZWxlbWVudDpmaWVsZC1lbmQnPjwvc3Bhbj48 +L3NwYW4+PCFbZW5kaWZdLS0+PHNwYW4gbGFuZz1FTi1HQg0Kc3R5bGU9J2ZvbnQtc2l6ZToxMC4w +cHQ7bXNvLWJpZGktZm9udC1zaXplOjExLjBwdCc+PHNwYW4gc3R5bGU9J21zby10YWItY291bnQ6 +DQoxJz7CoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKg +wqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDC +oMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKg +wqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDC +oMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKg +wqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDC +oMKgIDwvc3Bhbj7CqQ0KVGhlIENhbGVuZGFyaW5nIGFuZCBTY2hlZHVsaW5nIENvbnNvcnRpdW0s +IEluYy4mbmJzcDsyMDE5Jm5ic3A74oCTIEFsbCByaWdodHMgcmVzZXJ2ZWQ8bzpwPjwvbzpwPjwv +c3Bhbj48L3A+DQo8L2Rpdj4NCg0KPGRpdiBzdHlsZT0nbXNvLWVsZW1lbnQ6Zm9vdGVyJyBpZD1m +Mj4NCjxwIGNsYXNzPU1zb0Zvb3RlciBzdHlsZT0nbGluZS1oZWlnaHQ6MTIuMHB0Jz48c3BhbiBs +YW5nPUVOLUdCDQpzdHlsZT0nZm9udC1zaXplOjEwLjBwdDttc28tYmlkaS1mb250LXNpemU6MTEu +MHB0Jz7CqSBUaGUgQ2FsZW5kYXJpbmcgYW5kIFNjaGVkdWxpbmcgQ29uc29ydGl1bSwgSW5jLiZu +YnNwOzIwMTkmbmJzcDvigJMgQWxsDQpyaWdodHMgcmVzZXJ2ZWQ8c3BhbiBzdHlsZT0nbXNvLXRh +Yi1jb3VudDoxJz7CoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKg +wqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDC +oMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKg +wqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDC +oMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKg +wqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDC +oMKgwqDCoCA8L3NwYW4+PC9zcGFuPjwhLS1baWYgc3VwcG9ydEZpZWxkc10+PHNwYW4NCmxhbmc9 +RU4tR0Igc3R5bGU9J2ZvbnQtc2l6ZToxMC4wcHQ7bXNvLWJpZGktZm9udC1zaXplOjExLjBwdCc+ +PHNwYW4NCnN0eWxlPSdtc28tZWxlbWVudDpmaWVsZC1iZWdpbic+PC9zcGFuPiBQQUdFPHNwYW4g +c3R5bGU9J21zby1zcGFjZXJ1bjp5ZXMnPsKgwqANCjwvc3Bhbj5cKiBNRVJHRUZPUk1BVCA8c3Bh +biBzdHlsZT0nbXNvLWVsZW1lbnQ6ZmllbGQtc2VwYXJhdG9yJz48L3NwYW4+PC9zcGFuPjwhW2Vu +ZGlmXS0tPjxzcGFuDQpsYW5nPUVOLUdCIHN0eWxlPSdmb250LXNpemU6MTAuMHB0O21zby1iaWRp +LWZvbnQtc2l6ZToxMS4wcHQnPjxzcGFuDQpzdHlsZT0nbXNvLW5vLXByb29mOnllcyc+aWlpPC9z +cGFuPjwvc3Bhbj48IS0tW2lmIHN1cHBvcnRGaWVsZHNdPjxzcGFuDQpsYW5nPUVOLUdCIHN0eWxl +PSdmb250LXNpemU6MTAuMHB0O21zby1iaWRpLWZvbnQtc2l6ZToxMS4wcHQnPjxzcGFuDQpzdHls +ZT0nbXNvLWVsZW1lbnQ6ZmllbGQtZW5kJz48L3NwYW4+PC9zcGFuPjwhW2VuZGlmXS0tPjxzcGFu +IGxhbmc9RU4tR0INCnN0eWxlPSdmb250LXNpemU6MTAuMHB0O21zby1iaWRpLWZvbnQtc2l6ZTox +MS4wcHQnPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KDQo8ZGl2IHN0eWxlPSdtc28t +ZWxlbWVudDpmb290ZXInIGlkPWYybD4NCjxwIGNsYXNzPU1zb0Zvb3RlckxhbmRzY2FwZSBzdHls +ZT0nbGluZS1oZWlnaHQ6MTIuMHB0Jz48c3BhbiBsYW5nPUVOLUdCDQpzdHlsZT0nZm9udC1zaXpl +OjEwLjBwdDttc28tYmlkaS1mb250LXNpemU6MTEuMHB0Jz7CqSBUaGUgQ2FsZW5kYXJpbmcgYW5k +IFNjaGVkdWxpbmcgQ29uc29ydGl1bSwgSW5jLiZuYnNwOzIwMTkmbmJzcDvigJMgQWxsDQpyaWdo +dHMgcmVzZXJ2ZWQ8c3BhbiBzdHlsZT0nbXNvLXRhYi1jb3VudDoxJz7CoMKgwqDCoMKgwqDCoMKg +wqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDC +oMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKg +wqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDC +oMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKg +wqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDC +oMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoCA8L3NwYW4+PC9zcGFuPjwhLS1b +aWYgc3VwcG9ydEZpZWxkc10+PHNwYW4NCmxhbmc9RU4tR0Igc3R5bGU9J2ZvbnQtc2l6ZToxMC4w +cHQ7bXNvLWJpZGktZm9udC1zaXplOjExLjBwdCc+PHNwYW4NCnN0eWxlPSdtc28tZWxlbWVudDpm +aWVsZC1iZWdpbic+PC9zcGFuPiBQQUdFPHNwYW4gc3R5bGU9J21zby1zcGFjZXJ1bjp5ZXMnPsKg +wqANCjwvc3Bhbj5cKiBNRVJHRUZPUk1BVCA8c3BhbiBzdHlsZT0nbXNvLWVsZW1lbnQ6ZmllbGQt +c2VwYXJhdG9yJz48L3NwYW4+PC9zcGFuPjwhW2VuZGlmXS0tPjxzcGFuDQpsYW5nPUVOLUdCIHN0 +eWxlPSdmb250LXNpemU6MTAuMHB0O21zby1iaWRpLWZvbnQtc2l6ZToxMS4wcHQnPjxzcGFuDQpz +dHlsZT0nbXNvLW5vLXByb29mOnllcyc+aWlpPC9zcGFuPjwvc3Bhbj48IS0tW2lmIHN1cHBvcnRG +aWVsZHNdPjxzcGFuDQpsYW5nPUVOLUdCIHN0eWxlPSdmb250LXNpemU6MTAuMHB0O21zby1iaWRp +LWZvbnQtc2l6ZToxMS4wcHQnPjxzcGFuDQpzdHlsZT0nbXNvLWVsZW1lbnQ6ZmllbGQtZW5kJz48 +L3NwYW4+PC9zcGFuPjwhW2VuZGlmXS0tPjxzcGFuIGxhbmc9RU4tR0INCnN0eWxlPSdmb250LXNp +emU6MTAuMHB0O21zby1iaWRpLWZvbnQtc2l6ZToxMS4wcHQnPjxvOnA+PC9vOnA+PC9zcGFuPjwv +cD4NCjwvZGl2Pg0KDQo8ZGl2IHN0eWxlPSdtc28tZWxlbWVudDpmb290ZXInIGlkPWVmMz4NCjxw +IGNsYXNzPU1zb0Zvb3RlciBzdHlsZT0nbWFyZ2luLXRvcDoxMi4wcHQ7bGluZS1oZWlnaHQ6MTIu +MHB0O21zby1saW5lLWhlaWdodC1ydWxlOg0KZXhhY3RseSc+PCEtLVtpZiBzdXBwb3J0RmllbGRz +XT48YiBzdHlsZT0nbXNvLWJpZGktZm9udC13ZWlnaHQ6bm9ybWFsJz48c3Bhbg0KbGFuZz1FTi1H +QiBzdHlsZT0nZm9udC1zaXplOjEwLjBwdDttc28tYmlkaS1mb250LXNpemU6MTEuMHB0Jz48c3Bh +bg0Kc3R5bGU9J21zby1lbGVtZW50OmZpZWxkLWJlZ2luJz48L3NwYW4+PHNwYW4NCnN0eWxlPSdt +c28tc3BhY2VydW46eWVzJz7CoDwvc3Bhbj5QQUdFPHNwYW4gc3R5bGU9J21zby1zcGFjZXJ1bjp5 +ZXMnPsKgwqANCjwvc3Bhbj5cKiBNRVJHRUZPUk1BVCA8c3BhbiBzdHlsZT0nbXNvLWVsZW1lbnQ6 +ZmllbGQtc2VwYXJhdG9yJz48L3NwYW4+PC9zcGFuPjwvYj48IVtlbmRpZl0tLT48Yg0Kc3R5bGU9 +J21zby1iaWRpLWZvbnQtd2VpZ2h0Om5vcm1hbCc+PHNwYW4gbGFuZz1FTi1HQiBzdHlsZT0nZm9u +dC1zaXplOjEwLjBwdDsNCm1zby1iaWRpLWZvbnQtc2l6ZToxMS4wcHQnPjxzcGFuIHN0eWxlPSdt +c28tbm8tcHJvb2Y6eWVzJz4yPC9zcGFuPjwvc3Bhbj48L2I+PCEtLVtpZiBzdXBwb3J0RmllbGRz +XT48Yg0Kc3R5bGU9J21zby1iaWRpLWZvbnQtd2VpZ2h0Om5vcm1hbCc+PHNwYW4gbGFuZz1FTi1H +QiBzdHlsZT0nZm9udC1zaXplOjEwLjBwdDsNCm1zby1iaWRpLWZvbnQtc2l6ZToxMS4wcHQnPjxz +cGFuIHN0eWxlPSdtc28tZWxlbWVudDpmaWVsZC1lbmQnPjwvc3Bhbj48L3NwYW4+PC9iPjwhW2Vu +ZGlmXS0tPjxzcGFuDQpsYW5nPUVOLUdCIHN0eWxlPSdmb250LXNpemU6MTAuMHB0O21zby1iaWRp +LWZvbnQtc2l6ZToxMS4wcHQnPjxzcGFuDQpzdHlsZT0nbXNvLXRhYi1jb3VudDoxJz7CoMKgwqDC +oMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKg +wqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDC +oMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKg +wqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDC +oMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKg +wqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgIDwvc3Bhbj7C +qQ0KVGhlIENhbGVuZGFyaW5nIGFuZCBTY2hlZHVsaW5nIENvbnNvcnRpdW0sIEluYy4mbmJzcDsy +MDE5Jm5ic3A74oCTIEFsbCByaWdodHMgcmVzZXJ2ZWQ8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8 +L2Rpdj4NCg0KPGRpdiBzdHlsZT0nbXNvLWVsZW1lbnQ6Zm9vdGVyJyBpZD1lZjNsPg0KPHAgY2xh +c3M9TXNvRm9vdGVyTGFuZHNjYXBlIHN0eWxlPSdtYXJnaW4tdG9wOjEyLjBwdDtsaW5lLWhlaWdo +dDoxMi4wcHQ7bXNvLWxpbmUtaGVpZ2h0LXJ1bGU6DQpleGFjdGx5Jz48IS0tW2lmIHN1cHBvcnRG +aWVsZHNdPjxiIHN0eWxlPSdtc28tYmlkaS1mb250LXdlaWdodDpub3JtYWwnPjxzcGFuDQpsYW5n +PUVOLUdCIHN0eWxlPSdmb250LXNpemU6MTAuMHB0O21zby1iaWRpLWZvbnQtc2l6ZToxMS4wcHQn +PjxzcGFuDQpzdHlsZT0nbXNvLWVsZW1lbnQ6ZmllbGQtYmVnaW4nPjwvc3Bhbj48c3Bhbg0Kc3R5 +bGU9J21zby1zcGFjZXJ1bjp5ZXMnPsKgPC9zcGFuPlBBR0U8c3BhbiBzdHlsZT0nbXNvLXNwYWNl +cnVuOnllcyc+wqDCoA0KPC9zcGFuPlwqIE1FUkdFRk9STUFUIDxzcGFuIHN0eWxlPSdtc28tZWxl +bWVudDpmaWVsZC1zZXBhcmF0b3InPjwvc3Bhbj48L3NwYW4+PC9iPjwhW2VuZGlmXS0tPjxiDQpz +dHlsZT0nbXNvLWJpZGktZm9udC13ZWlnaHQ6bm9ybWFsJz48c3BhbiBsYW5nPUVOLUdCIHN0eWxl +PSdmb250LXNpemU6MTAuMHB0Ow0KbXNvLWJpZGktZm9udC1zaXplOjExLjBwdCc+PHNwYW4gc3R5 +bGU9J21zby1uby1wcm9vZjp5ZXMnPjI8L3NwYW4+PC9zcGFuPjwvYj48IS0tW2lmIHN1cHBvcnRG +aWVsZHNdPjxiDQpzdHlsZT0nbXNvLWJpZGktZm9udC13ZWlnaHQ6bm9ybWFsJz48c3BhbiBsYW5n +PUVOLUdCIHN0eWxlPSdmb250LXNpemU6MTAuMHB0Ow0KbXNvLWJpZGktZm9udC1zaXplOjExLjBw +dCc+PHNwYW4gc3R5bGU9J21zby1lbGVtZW50OmZpZWxkLWVuZCc+PC9zcGFuPjwvc3Bhbj48L2I+ +PCFbZW5kaWZdLS0+PHNwYW4NCmxhbmc9RU4tR0Igc3R5bGU9J2ZvbnQtc2l6ZToxMC4wcHQ7bXNv +LWJpZGktZm9udC1zaXplOjExLjBwdCc+PHNwYW4NCnN0eWxlPSdtc28tdGFiLWNvdW50OjEnPsKg +wqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDC +oMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKg +wqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDC +oMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKg +wqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDC +oMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqAgPC9z +cGFuPsKpDQpUaGUgQ2FsZW5kYXJpbmcgYW5kIFNjaGVkdWxpbmcgQ29uc29ydGl1bSwgSW5jLiZu +YnNwOzIwMTkmbmJzcDvigJMgQWxsIHJpZ2h0cyByZXNlcnZlZDxvOnA+PC9vOnA+PC9zcGFuPjwv +cD4NCjwvZGl2Pg0KDQo8ZGl2IHN0eWxlPSdtc28tZWxlbWVudDpmb290ZXInIGlkPWYzPg0KPHAg +Y2xhc3M9TXNvRm9vdGVyIHN0eWxlPSdsaW5lLWhlaWdodDoxMi4wcHQnPjxzcGFuIGxhbmc9RU4t +R0INCnN0eWxlPSdmb250LXNpemU6MTAuMHB0O21zby1iaWRpLWZvbnQtc2l6ZToxMS4wcHQnPsKp +IFRoZSBDYWxlbmRhcmluZyBhbmQgU2NoZWR1bGluZyBDb25zb3J0aXVtLCBJbmMuJm5ic3A7MjAx +OSZuYnNwO+KAkyBBbGwNCnJpZ2h0cyByZXNlcnZlZDxzcGFuIHN0eWxlPSdtc28tdGFiLWNvdW50 +OjEnPsKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDC +oMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKg +wqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDC +oMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKg +wqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDC +oMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKg +wqAgPC9zcGFuPjwvc3Bhbj48IS0tW2lmIHN1cHBvcnRGaWVsZHNdPjxiDQpzdHlsZT0nbXNvLWJp +ZGktZm9udC13ZWlnaHQ6bm9ybWFsJz48c3BhbiBsYW5nPUVOLUdCIHN0eWxlPSdmb250LXNpemU6 +MTAuMHB0Ow0KbXNvLWJpZGktZm9udC1zaXplOjExLjBwdCc+PHNwYW4gc3R5bGU9J21zby1lbGVt +ZW50OmZpZWxkLWJlZ2luJz48L3NwYW4+DQpQQUdFPHNwYW4gc3R5bGU9J21zby1zcGFjZXJ1bjp5 +ZXMnPsKgwqAgPC9zcGFuPlwqIE1FUkdFRk9STUFUIDxzcGFuDQpzdHlsZT0nbXNvLWVsZW1lbnQ6 +ZmllbGQtc2VwYXJhdG9yJz48L3NwYW4+PC9zcGFuPjwvYj48IVtlbmRpZl0tLT48Yg0Kc3R5bGU9 +J21zby1iaWRpLWZvbnQtd2VpZ2h0Om5vcm1hbCc+PHNwYW4gbGFuZz1FTi1HQiBzdHlsZT0nZm9u +dC1zaXplOjEwLjBwdDsNCm1zby1iaWRpLWZvbnQtc2l6ZToxMS4wcHQnPjxzcGFuIHN0eWxlPSdt +c28tbm8tcHJvb2Y6eWVzJz4zPC9zcGFuPjwvc3Bhbj48L2I+PCEtLVtpZiBzdXBwb3J0RmllbGRz +XT48Yg0Kc3R5bGU9J21zby1iaWRpLWZvbnQtd2VpZ2h0Om5vcm1hbCc+PHNwYW4gbGFuZz1FTi1H +QiBzdHlsZT0nZm9udC1zaXplOjEwLjBwdDsNCm1zby1iaWRpLWZvbnQtc2l6ZToxMS4wcHQnPjxz +cGFuIHN0eWxlPSdtc28tZWxlbWVudDpmaWVsZC1lbmQnPjwvc3Bhbj48L3NwYW4+PC9iPjwhW2Vu +ZGlmXS0tPjxzcGFuDQpsYW5nPUVOLUdCIHN0eWxlPSdmb250LXNpemU6MTAuMHB0O21zby1iaWRp +LWZvbnQtc2l6ZToxMS4wcHQnPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KDQo8ZGl2 +IHN0eWxlPSdtc28tZWxlbWVudDpmb290ZXInIGlkPWYzbD4NCjxwIGNsYXNzPU1zb0Zvb3Rlckxh +bmRzY2FwZSBzdHlsZT0nbGluZS1oZWlnaHQ6MTIuMHB0Jz48c3BhbiBsYW5nPUVOLUdCDQpzdHls +ZT0nZm9udC1zaXplOjEwLjBwdDttc28tYmlkaS1mb250LXNpemU6MTEuMHB0Jz7CqSBUaGUgQ2Fs +ZW5kYXJpbmcgYW5kIFNjaGVkdWxpbmcgQ29uc29ydGl1bSwgSW5jLiZuYnNwOzIwMTkmbmJzcDvi +gJMgQWxsDQpyaWdodHMgcmVzZXJ2ZWQ8c3BhbiBzdHlsZT0nbXNvLXRhYi1jb3VudDoxJz7CoMKg +wqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDC +oMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKg +wqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDC +oMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKg +wqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDC +oMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgIDwvc3Bh +bj48L3NwYW4+PCEtLVtpZiBzdXBwb3J0RmllbGRzXT48Yg0Kc3R5bGU9J21zby1iaWRpLWZvbnQt +d2VpZ2h0Om5vcm1hbCc+PHNwYW4gbGFuZz1FTi1HQiBzdHlsZT0nZm9udC1zaXplOjEwLjBwdDsN +Cm1zby1iaWRpLWZvbnQtc2l6ZToxMS4wcHQnPjxzcGFuIHN0eWxlPSdtc28tZWxlbWVudDpmaWVs +ZC1iZWdpbic+PC9zcGFuPg0KUEFHRTxzcGFuIHN0eWxlPSdtc28tc3BhY2VydW46eWVzJz7CoMKg +IDwvc3Bhbj5cKiBNRVJHRUZPUk1BVCA8c3Bhbg0Kc3R5bGU9J21zby1lbGVtZW50OmZpZWxkLXNl +cGFyYXRvcic+PC9zcGFuPjwvc3Bhbj48L2I+PCFbZW5kaWZdLS0+PGINCnN0eWxlPSdtc28tYmlk +aS1mb250LXdlaWdodDpub3JtYWwnPjxzcGFuIGxhbmc9RU4tR0Igc3R5bGU9J2ZvbnQtc2l6ZTox +MC4wcHQ7DQptc28tYmlkaS1mb250LXNpemU6MTEuMHB0Jz48c3BhbiBzdHlsZT0nbXNvLW5vLXBy +b29mOnllcyc+Mzwvc3Bhbj48L3NwYW4+PC9iPjwhLS1baWYgc3VwcG9ydEZpZWxkc10+PGINCnN0 +eWxlPSdtc28tYmlkaS1mb250LXdlaWdodDpub3JtYWwnPjxzcGFuIGxhbmc9RU4tR0Igc3R5bGU9 +J2ZvbnQtc2l6ZToxMC4wcHQ7DQptc28tYmlkaS1mb250LXNpemU6MTEuMHB0Jz48c3BhbiBzdHls +ZT0nbXNvLWVsZW1lbnQ6ZmllbGQtZW5kJz48L3NwYW4+PC9zcGFuPjwvYj48IVtlbmRpZl0tLT48 +c3Bhbg0KbGFuZz1FTi1HQiBzdHlsZT0nZm9udC1zaXplOjEwLjBwdDttc28tYmlkaS1mb250LXNp +emU6MTEuMHB0Jz48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCg0KPC9ib2R5Pg0KDQo8 +L2h0bWw+DQo= + +------=_NextPart_86bf3968.c2a0.4313-- \ No newline at end of file diff --git a/documents/cc-10010.html b/documents/cc-10010.html new file mode 100644 index 0000000..3f8aeed --- /dev/null +++ b/documents/cc-10010.html @@ -0,0 +1,1937 @@ + + + + ISO/CalConnect Partner Standards Development Organization (PSDO) Cooperation Agreement + + + + + + + + + + + + + + + + +
+

Final Draft

+
+ +
+

CalConnect Standard

+
+ +
+ +
+ + +
+
+ +
+
+ CC/FDS 10010:2019 + +
+ +
+ ISO/CalConnect Partner Standards Development Organization (PSDO) Cooperation Agreement + +
+
+ + + +
+ TC PUBLISH +
+ + + + + +
+ + +
+
+ +
+
+ CalConnect Standard +
+ +
+ Final Draft +
+ + +
+
+

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. +

+
+
+
+ + + + +
+
+
+
+ +

 

+
+
+
+ + +
+ +

 

+
+
+
+
+ + + + + + + + + +
+
+
+

Foreword

+

The Calendaring and Scheduling Consortium (“CalConnect”) is a global +non-profit organization that pursues the wide availability of truly +interoperable collaboration systems and applications through the use of +open standards. +CalConnect works closely with liaison partners and international +standard organizations including ISO, OASIS and M3AAWG.

+

ISO (the International Organization for Standardization) +is a worldwide federation of national standards bodies (ISO member +bodies). The work of preparing International Standards is normally +carried out through ISO technical committees. Each member body +interested in a subject for which a technical committee has been +established has the right to be represented on that committee. +International organizations, governmental and non-governmental, in +liaison with ISO, also take part in the work. ISO collaborates closely +with the International Electrotechnical Commission (IEC) on all matters +of electrotechnical standardization.

+

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 the Joint Coordination Group of +ISO and CalConnect.

+

This is the first edition of this document.

+
+
+
+

Introduction

+

Purpose

The purpose of this document is to establish an understanding between +ISO and CalConnect on cooperation on standards +development.

+

This document formalizes the process of collaboration of +ISO and CalConnect to cooperate and to +enable the collaborative development of standards.

+

The resulting standards are to be jointly published by +ISO and CalConnect as “ISO/CalConnect Standards”, +according to processes described in this document.

+

Background

One of the objectives of ISO is to facilitate the international +exchange of goods and services through the development of International +Standards.

+

The ISO Council has adopted a policy of inclusiveness +and encourages cooperation between ISO and other standardizing bodies, +where such cooperation would serve to ensure effective and efficient +use of resources available for standardization activities.

+

CalConnect aims to facilitate interoperability of collaborative +technologies with open standards, in particular on calendar, scheduling, +and contacts; its standards are globally recognized and widely applied.

+

Intention

+ +

ISO and CalConnect agree to the principles of cooperation described in +this document, in all fields subject to approval by the ISO TMB and the +CalConnect TC PUBLISH and TCC.

+
+

Process cooperation

ISO and CalConnect wish to avoid duplication of efforts by their +respective committees.

+

ISO produces International Standards in accordance with processes +described in ISO 1 (all parts) and ISO 1 (all parts), with the standard documents +drafted in accordance with the editorial rules of ISO/IEC Guide 2 (all parts).

+

CalConnect creates publicly available CalConnect Standards through +a consensus-based standardization process described in CC/DIR 10001, and +standard documents created in accordance with CC/DIR 10002.

+

Both ISO and CalConnect believe that cooperation at +the standards development process level provides the following benefits:

+
    +
  • +

    maximizes the deliverable expertise of their experts; and

    +
  • +
  • +

    maximizes the quality of the resulting International Standard.

    +
  • +
+

This agreement facilitates a collaborative development process +for the creation of joint publications (ISO/CalConnect Standards) +between ISO and CalConnect.

+
+

ISO/CalConnect Partner Standards Development Organization (PSDO) Cooperation Agreement

+
+

1.  Scope

+

This document describes the agreement between CalConnect and ISO for +the cooperation of standards development and publication.

+

Specifically, it provides the principles and necessary processes for these +collaborative cases between ISO and CalConnect (“Parties”):

+
    +
  • +

    co-development of a standardization work item, proposed by either party

    +
  • +
  • +

    submission of a CalConnect document to ISO for its +standardization process

    +
  • +
+

Standardization processes in this document is intended to align +with ISO 1 (all parts), ISO 1 (all parts), CC/DIR 10001 and CC/DIR 10002.

+
+

2.  Normative references

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.

CC CC/DIR 10001, CalConnect Directive: Standardization and publication

CC CC/DIR 10002, CalConnect Directive: Standard document requirements

ISO 1 (all parts), Geometrical product specifications (GPS) – Standard reference temperature for the specification of geometrical and dimensional properties

ISO 1 (all parts), Geometrical product specifications (GPS) – Standard reference temperature for the specification of geometrical and dimensional properties

ISO/IEC Guide 2 (all parts), Standardization and related activities – General vocabulary

ISO/IEC Guide 2:2004, Standardization and related activities – General vocabulary

+
+

3.  Terms and definitions

+

For the purposes of this document, the terms and definitions + given in ISO/IEC Guide 2:2004 and the following apply.

+

3.1.  Terms and definitions

3.1.1. 

ISO members

+ +

ISO member bodies and correspondent members

+ +

3.1.2. 

CalConnect members

+ +

CalConnect member bodies

+ +

3.1.3. 

ISO committee

+

ISO TC

+ +

ISO Technical Committee (including ISO/IEC JTC1) or Subcommittee

+

3.1.4. 

CalConnect technical committee

+

CalConnect TC

+ +

internal committee of CalConnect tasked with a scope of work it +is responsible for

+

3.1.5. 

standardization project

+ +

an organized process with one or more standardization work items that +contributes towards a defined scope of work

+ +

3.1.6. 

standardization work item

+ +

publishable work item that creates output that relates +to standardization within a standardization project (Clause 3.1.5)

+ +

3.1.7. 

project owner

+ +

entity with authority in charge of a standardization project +(Clause 3.1.5)

+ +

3.1.8. 

document

+ +

written output of a work item

+ +

3.1.9. 

CalConnect deliverable

document (Clause 3.1.8) produced by a CalConnect TC +(Clause 3.1.4) as described in CC/DIR 10001

+

Note 1 to entry: According to CC/DIR 10001, CalConnect deliverables include the +following types: CalConnect Standard, Guide, Specification, Report and +Directives. Directives are not considered a standardization work item.

+

3.1.10. 

ISO TC deliverable

document (Clause 3.1.8) produced by an ISO TC +(Clause 3.1.3) as described in ISO 1 (all parts)

+

Note 1 to entry: According to ISO 1 (all parts), ISO TC deliverables include the +following types: International Standards, Technical Specifications, +Publicly Available Specifications and Technical Reports.

+

3.1.11. 

document stage

+ +

stage of document as specified in the ISO harmonized stages (as defined +in ISO 1 (all parts))

+ +

3.1.12. 

standardization project output

output of a standardization project (Clause 3.1.5)

+

Note 1 to entry: In this document, it explicitly means any documents and IP rights +produced by the standardization project.

+

3.1.13. 

proposal for standardization

+ +

proposal for a new work item for standardization

+ +

3.1.14. 

co-develop

+ +

act of developing a work item by multiple parties from the proposal stage

+ +

3.1.15. 

co-publish

+ +

act of publishing documents (Clause 3.1.8) of identical content +by multiple parties

+ +

3.1.16. 

joint work item

+ +

work item co-developed (Clause 3.1.14) by both parties

+ +

3.1.17. 

joint deliverable

+ +

completed form of a joint work item that is designated to be +co-published (Clause 3.1.15) by ISO +and CalConnect

+ +

3.1.18. 

joint publication

publication that is co-published (Clause 3.1.15) by +ISO and CalConnect

+

Note 1 to entry: Different publishers of a joint publication may utilize a +different document layout.

+

3.1.19. 

Joint Coordination Group

+

JCG

+ +

advisory group with representatives from ISO and CalConnect on +the execution and maintenance of this agreement

+

3.1.20. 

joint project group

+

JPG

+ +

group created to be project owner (Clause 3.1.7) of a joint work item (Clause 3.1.16), +composed of participants from ISO committees (Clause 3.1.3) and CalConnect TCs (Clause 3.1.4)

+

3.1.21. 

joint maintenance group

+

JMG

+ +

joint project group (Clause 3.1.20) for the sole +purpose of maintaining a +joint publication (Clause 3.1.18)

+

3.1.22. 

co-development document register

+ +

document register of a list of co-developed (Clause 3.1.14) +documents (Clause 3.1.8) developed under this agreement, +held by the Joint Coordination Group (Clause 3.1.19)

+
+

3.2.  Abbreviations

+ +

IPR

+

Intellectual Property Rights

+

TCC

+

CalConnect Technical Coordination Committee

+

TMB

+

ISO Technical Management Board

+
+
+
+
+

4.  Principles of cooperation

+

4.1.  Collaborative development process

A collaborative development process is crucial to effective development +of work items between ISO and CalConnect.

+

Both organizations agree to align appropriate internal processes +and procedures in order to facilitate joint development of work items.

+

Three mechanisms are provided below for cooperative development of +joint publications between ISO and CalConnect, namely:

+
    +
  1. +

    CalConnect contributes content to ISO;

    +
  2. +
  3. +

    ISO and CalConnect co-develop a joint deliverable;

    +
  4. +
  5. +

    Adoption of an existing standard from either party.

    +
  6. +
+

4.2.  Central coordination group

+ +

ISO and CalConnect agree to the establishment of a joint coordination group +(JCG) to coordinate matters relevant to the execution and maintenance +of this agreement.

+
+

4.3.  Across subject fields

ISO and CalConnect agree that this agreement applies to all subject fields +subject to approval by both parties.

+

Details of implementation are provided in Clause 5.4.

+

4.4.  Normative referencing

ISO and CalConnect agree to the normative referencing of their +standards as appropriate in publications of the other organization in +compliance with each organization’s policies and directives relative to +normative references.

+

Implementation details are provided in Appendix A.1.

+

4.5.  Patent policy

ISO and CalConnect agree that content of joint deliverables, +including the ISO published form of joint publications, +will remain free of IPR restrictions that would limit their application.

+

Patented content in a joint deliverable is governed by the +ISO patent policy and the CalConnect IPR policy.

+

Any patents involved knowingly in the document shall be made +transparent prior to the DIS stage of the joint deliverable.

+

4.6.  Contributions to ISO standards

ISO International Standards are normally developed within ISO +Committees. As part of this normal development process, an ISO +committee may determine that specific elements of an CalConnect +standard (e.g. figures, data, definitions), along with information from +other sources, would contribute to the development of an ISO Standard.

+

As specified in the ISO 1 (all parts), original material contributed to +become part of an ISO publication is normally copied and distributed +within the ISO system as part of the consensus-building process, this +being without prejudice to the rights of the original copyright owner +to exploit the original text.

+

It is also recognized that, where such material is already subject to +copyright, rights have to be granted to ISO to reproduce and circulate +the material.

+

As part of this agreement, CalConnect grants a licence to ISO described +in Appendix A.2 +for using elements of a CalConnect standard in the development of joint +publications.

+

4.7.  Co-development of standards

In cases where CalConnect has developed a standard, or where CalConnect +is proposing or developing a standard (yet unpublished), which +corresponds to a stated ISO TC need covered by this agreement.

+

In these instances, the relevant ISO TC and CalConnect TC +may agree that it would be mutually beneficial to develop work jointly.

+

ISO and CalConnect agree to a coordinated and specified process for the +co-development of joint publications.

+

The detailed process and procedures are provided in Appendix C; copyright of the +resulting deliverables is explained in Appendix A.3.2.

+

4.8.  Adoption of existing standards

4.8.1.  General

ISO and CalConnect agree to a coordinated and specified process for the +adoption of either party’s standardization work items, where:

+
    +
  • +

    CalConnect may wish to formally adopt a published ISO +International Standard;

    +
  • +
  • +

    CalConnect may propose that an existing CalConnect standard be +submitted as a final draft International Standard (FDIS) at ISO.

    +
  • +
+

Copyright of joint publications created through adoption is +explained in Appendix A.3.1.

+

4.8.2.  Adoption of an ISO Standard by CalConnect

CalConnect may wish to formally adopt a published ISO International +Standard.

+

In this case, the source party is ISO and the adopting party +is CalConnect.

+

The method of adoption is specified in Appendix D.2.

+

4.8.3.  Adoption of a CalConnect Standard by ISO

A published CalConnect standard with global use and acceptance may be +proposed for adoption as an ISO International Standard, through the +FDIS fast-track procedure of submitting a CalConnect standard to ISO.

+

In this case, the source party is CalConnect and the adopting party +is ISO.

+

The method of adoption is detailed in Appendix D.3.

+

4.9.  Maintenance of joint publications

Maintenance of joint publications shall be a joint responsibility under +a joint process.

+

Details of the implementation of this clause is described in Appendix E.

+

In joint publications where a maintenance agency or registration authority +is necessary, CalConnect agrees to serve as the default volunteer, as +described in Appendix E.7.

+

4.10.  Mutual recognition and joint deliverables requirements

ISO and CalConnect shall establish rules to ensure +the collaborative effort by both parties are mutually +recognized within joint deliverables.

+

The associated requirements are provided in Appendix F.

+

4.11.  Promotional activities

+ +

ISO and CalConnect agree to share and coordinate promotional activities +for the joint publication via the JCG.

+
+
+
+

5.  Joint Coordination Group

+

5.1.  General

ISO and CalConnect agrees to establish a standing body, +the Joint Coordination Group (“JCG”), for:

+
    +
  • +

    maintenance and execution of this agreement; and

    +
  • +
  • +

    coordination and maintenance of procedures between two organizations.

    +
  • +
+

5.2.  Mediator for coordination issues

+ +

This group meets as necessary and serves as the forum for discussing +and resolving issues relating to coordination that may arise from time to time.

+
+

5.3.  Coordination role

The JCG will support the individual liaisons between +ISO Technical Committee working groups and project teams, +with CalConnect technical committees.

+

The presence of the JCG is not intended to affect +responsibilities of existing organizational structures +in ISO and CalConnect.

+

5.4.  Fields of collaboration

+ +

The JCG is responsible with the determination of the subject fields +of which this agreement applies to, subject to approval by +the ISO Technical Management Board and the CalConnect TC PUBLISH and TCC.

+
+

5.5.  Members

The JCG is composed of an equal number of representatives from both parties:

+
    +
  • +

    Two representatives from ISO

    +
  • +
  • +

    Two representatives from CalConnect

    +
  • +
+
+
+

6.  Amendments to this agreement

+

ISO and CalConnect agree that changes to this agreement shall be +first proposed through the JCG, and formalized by a resolution from one +party to the other.

+
+
+
+

Appendix A
(normative)
Publication, copyright and commercial arrangements

+ +

A.2.  CalConnect content license for joint development

In the development, review and adoption process, ISO members are free to copy and +distribute the relevant CalConnect documents for standards development +purposes and in accordance with ISO policies for the circulation of +draft standards and working documents.

+

CalConnect grants ISO a world-wide, non-exclusive, non-sub-licensable +license (except for national body adoption), +to use contents of CalConnect submitted documents to ISO, +within the development, review and adoption process of the +deliverables under this agreement.

+ +

A.4.  Re-publishing

ISO and CalConnect agree that any re-publishing of content +developed under this agreement, such as the national adoption +of a joint publication by an ISO member body, or the re-publishing +of a joint publication by another organization, +will adhere to this agreement.

+

Publishing arrangements between ISO and ISO member countries are +unchanged by this agreement.

+

A.5.  Statement indicating source

+ +

ISO and CalConnect agree that the resulting publication created with +the joint deliverable will contain a suitable statement that describes +the base standard the joint deliverable was derived from.

+
+

A.6.  Notification of right infringement

Each party shall promptly inform the other party if it becomes aware of +any copyright infringement or potential infringement of a joint publication.

+

CalConnect and ISO shall consult with each other to decide the best +way to respond to such infringement.

+
+
+
+

Appendix B
(normative)
Alignment of project timeline

+

B.1.  Project stage mapping

The following table provides a mapping between ISO project stages and +CalConnect project stages. This document identifies stages +according to the ISO project stage names.

+

Table B.1 — Alignment between ISO and CalConnect project stages

Identification in this documentISO harmonized stage (ISO 1 (all parts))CalConnect stage
+Preliminary +00 Preliminary00 Preliminary
+Proposal +10 Proposal10 Proposal
+Preparatory +20 Preparatory20 Preparatory
+Committee +30 Committee30 Committee
+Enquiry +40 Enquiry40 Enquiry
+Approval +50 Approval50 Approval
+Publication +60 Publication60 Publication
+Review +90 Review90 Review
+Withdrawal +95 Withdrawal95 Withdrawal
+

B.2.  Track synchronization

ISO deliverables can be developed according to different tracks +and timelines detailed in ISO 1 (all parts) and ISO 1 (all parts).

+

CalConnect deliverables are developed according to the +timelines detailed in CC/DIR 10001.

+

For a project under this agreement, CalConnect agrees to adopt +a developmental track not slower than the track selected in +ISO to ensure the synchronicity between +development outcome and publication.

+
+
+
+

Appendix C
(normative)
Co-development process

+

C.1.  General

In joint development, technical level support for the development of +these standards is provided through the associated CalConnect TC as +well as the ISO member bodies and their duly appointed technical +experts through the relevant ISO TC.

+

Experts in ISO are encouraged to participate in the +technical work on CalConnect technologies by participating in +CalConnect technical committees.

+

C.2.  First draft

A first draft of the standardization deliverable may be created +for proposal submission, or may be created in the Committee stage. +The draft shall be created through a collaboration process between +experts from both organizations, or at least, the proposing +organization should have received input from the other organization.

+

CalConnect agrees that any draft submitted to ISO +shall adhere to the requirements detailed in CC/DIR 10002, ISO/IEC Guide 2 (all parts) and +applicable internal guidelines of ISO.

+

C.3.  Disapproval and continuance

If the project proposal is rejected by the JCG, its output may still be +developed by the project proposer if appropriate, and its output may +still be proposed to the JCG for co-development in later stages.

+

At any time, if a ballot to approve the development of a joint work item +is disapproved by ISO or CalConnect, each organization may proceed +to develop the joint work item independently of each other.

+

C.4.  Proposal development: Preliminary stage

C.4.1.  General

At the first instance where either party wishes to co-develop +a project with the other party, it should be raised to the JCG.

+

The JCG shall consult the stakeholders to determine appropriateness +of the project and advise the proposer.

+

C.4.2.  Initiation by CalConnect

+ +

CalConnect may propose to the appropriate ISO TC(s) to +jointly develop a new or existing CalConnect standard +to gain recognition as an ISO/CalConnect Standard.

+
+

C.4.3.  Initiation by ISO TC

+ +

If an ISO TC wishes to initiate the joint development of a +standard, the ISO TC secretariat shall contact the appropriate +CalConnect TC to gauge mutual interest.

+
+

C.5.  Proposal submission: Proposal stage

C.5.1.  General

+ +

When the JCG determines interest within ISO to co-develop the +proposed project, the project proposer should submit a proposal +indicating its wish to co-develop the proposed project, +to be approved by the relevant ISO and CalConnect TCs via ballot.

+
+

C.5.2.  Initiation by CalConnect

CalConnect shall provide a NWIP in accordance with ISO 1 (all parts) for the +proposal of new work items.

+

In addition, the NWIP shall include:

+
    +
  • +

    rationale for using this process; and

    +
  • +
  • +

    justification of the need for an ISO/CalConnect International +Standard.

    +
  • +
+

C.5.3.  Initiation by ISO TC

An ISO member shall submit a NWIP to the ISO TC for approval +in accordance with ISO 1 (all parts).

+

Concurrently, the corresponding CalConnect TC will submit a +project proposal to the CalConnect TCC, providing the relevant +information for the project and a statement that the project +is to be developed jointly with the relevant ISO TC.

+

C.5.4.  Fast-track proposal at ISO

When the ISO NWIP is accompanied by an existing CalConnect standard, +members of the ISO TC will be invited to approve its submission as a DIS.

+

NOTE  A two-thirds (2/3) majority vote of participating ISO P-members +is required for approval (ISO 1 (all parts)).

+

C.5.5.  Approval of co-development

If both organizations approve the proposal for joint development, +the project shall be adopted on both sides by a CalConnect +TC and an ISO TC.

+

The JCG shall then create a joint project group to be the project +owner of the proposed joint work item through the CalConnect TCC and the +secretariat of the ISO TC, consisting of nominated experts from the +relevant CalConnect and ISO TCs.

+

ISO and CalConnect will mutually agree on a Convener for the JPG.

+

This approved project shall be listed in the JCG register of +co-developed projects.

+

C.6.  Content development: Preparatory, Committee, Enquiry stages

C.6.1.  General

The goal of these stages are to create an approved, balloted +draft of the joint deliverable by both parties.

+

In these stages, members of the joint project group shall +collaborate closely to ensure efficient and effective +development of the deliverable of the respective stages. +The deliverable shall be developed jointly by experts of +both organizations.

+

C.6.2.  Stage synchronization

The approval process at CalConnect and ISO shall be adhered to. +CalConnect agrees to synchronize its project stage with +the corresponding ISO project stage.

+

Specifically:

+
    +
  • +

    If a deliverable is approved by ballot at both ISO and CalConnect, +CalConnect will advance the project stage at its +project group accordingly.

    +
  • +
  • +

    If a deliverable is rejected by ballot at either party, +CalConnect will not advance project stage at its +project group, unless a re-ballot at ISO approves +advancement of the deliverable.

    +
  • +
  • +

    In cases where a development stage is optional and skipped +in accordance with ISO 1 (all parts) and ISO 1 (all parts), CalConnect +shall set the stage of its project at the corresponding +stage.

    +
  • +
+

C.6.3.  Approval of a committee draft

Once consensus is reached within the JPG, the draft is circulated to +the relevant ISO and CalConnect TCs for three-month comment.

+

The JPG prepares a compilation of comments received from both +organizations and develops a revised draft.

+

C.6.4.  Approval of a draft standard

Once consensus within the JPG is achieved, the draft is provided to ISO +for DIS ballot and CalConnect for DS ballot.

+

Once balloting and approval at that stage, from both organizations, is +completed, the JPG prepares the document for circulation by ISO for a +two-month FDIS vote (according to ISO 1 (all parts), unanimous approval in +ISO during DIS ballot implies that a further FDIS ballot is not +necessary).

+

In parallel, CalConnect submits the draft to the CalConnect TCC for FS +ballot.

+

C.6.5.  Approval for publication

The document is considered approved when:

+
    +
  • +

    ISO achieves the requisite FDIS approval (or unanimous DIS approval), +in accordance with ISO 1 (all parts), and;

    +
  • +
  • +

    CalConnect TCC has provided its requisite approval, in accordance +with CC/DIR 10001.

    +
  • +
+

Once the document has been approved by both ISO and CalConnect, the +document is published as a joint ISO/CalConnect standard.

+

C.7.  Pre-publication: Public review

A public review period of 60 days is required for the compliance +to WTO TBT Agreements rules, for which both ISO and CalConnect adhere to.

+

A 60-day public review shall be held in the DIS stage of the ISO deliverable.

+

Comments to ISO shall be performed according to ISO 1 (all parts) and ISO 1 (all parts); +comments to CalConnect shall be performed through CalConnect’s public review procedure.

+

The parties agree to synchronize the dates of review periods for the +maximum benefit to the joint work item.

+

C.8.  Publication

C.8.1.  As a CalConnect Standard

+ +

After an ISO ballot on the acceptance of a joint work item as +DIS, FDIS or IS, the joint work item will be published +as a CalConnect Standard.

+
+

C.8.2.  As an ISO/CalConnect Standard

+ +

After an ISO ballot on the acceptance of a joint work item’s status +to proceed to IS from FDIS, the joint work item will be published by +ISO and CalConnect as an ISO/CalConnect Standard.

+
+

C.9.  Abandonment

A joint work item may be abandoned by one of the two parties if it sees +it being inappropriate or is no longer interested or able to contribute +to the joint work item. Each party is allowed to abandon the joint +work, which at that point will become sole work of the other party.

+

A notice of such must be sent by the abandoning party to the JCG and +distributed by both parties to its members.

+

The abandoning party, if the abandoned work is carried on by the other +party, is required to explicitly agree that the copyright of such work +is to be waived to the continuing party to allow publication of the document.

+

The rejoining an abandoned work item prior to publication, by the abandoning party, +is explicitly allowed by this agreement, given a notice is filed at +the JCG, unless in exceptional circumstances.

+

C.10.  Additional collaborators

+ +

Parties may bring in additional collaborators under this agreement, +given it is approved by the JCG, that the provisions of this agreement +are fully satisfied by agreements present between all collaborators.

+
+

C.11.  Notification

+ +

Notification of availability of new documents within CalConnect +will be announced to the appropriate ISO TCs and CalConnect TCs.

+
+

C.12.  Availability of working documents

+ +

Drafts and working documents are available according to +each party’s normal practices.

+
+
+
+
+

Appendix D
(normative)
Adoption process

+

D.1.  General

ISO and CalConnect agree to a coordinated and specified process for the +adoption of either party’s standardization work items, where:

+
    +
  • +

    CalConnect may wish to formally adopt a published ISO International Standard;

    +
  • +
  • +

    CalConnect may propose that an existing CalConnect standard be +submitted as a final draft International Standard (FDIS) at ISO.

    +
  • +
+

D.2.  Adoption of an ISO Standard by CalConnect

CalConnect may wish to formally adopt a published ISO International +Standard as described in Clause 4.8.2,

+

Such adoption shall be subject to an agreement between CalConnect and +the ISO member body in the country where CalConnect has its legal seat +(ANSI).

+

D.3.  Adoption of a CalConnect Standard by ISO

D.3.1.  General

As described in Clause 4.8.3, a CalConnect +standard may be adopted by ISO.

+

The adoption of a CalConnect standard at ISO is through FDIS fast-track +as described in this clause.

+

Adoption by ISO FDIS approval is intended to validate an existing +CalConnect standard through ISO’s established member body approval +mechanism.

+

D.3.2.  Initiation by CalConnect

CalConnect may propose an existing CalConnect standard to be submitted +as a final draft International Standard (FDIS) at ISO.

+

Such requests shall be submitted to the Secretary-General of ISO for +acceptance.

+

The ISO Secretary-General shall then submit a proposal to the relevant +ISO committee for a 30-day ballot which shall decide, by simple majority +vote, on:

+
    +
  1. +

    the need for an ISO International Standard on the subject; and

    +
  2. +
  3. +

    submission of the proposal for FDIS ballot.

    +
  4. +
+

D.3.3.  Initiation by ISO

Any ISO TC may decide to invite, by simple majority vote, CalConnect to +offer a particular CalConnect standard for adoption under this +agreement, provided agreement has been obtained from CalConnect.

+

Where an ISO TC confirms the need for an ISO International Standard, +but determines that the proposed CalConnect standard should not be +submitted for FDIS ballot, CalConnect shall be consulted on its +interest to proceed with the project jointly.

+

D.3.4.  Approval

Requirements for acceptance shall be those pertaining to the FDIS +approval stage in ISO 1 (all parts).

+

Upon acceptance by CalConnect and the relevant ISO TC, the CalConnect +standard shall be circulated to ISO members for a five-month approval +vote (to also allow for national public review and, where necessary, +translation).

+

The adoption is considered approved once the FDIS ballot is approved.

+

The process described in Appendix C.8.2 also applies.

+
+
+
+

Appendix E
(normative)
Maintenance of joint deliverables

+

E.1.  General

The project groups in both organizations responsible for +the published deliverable shall work in collaboration to +address any corrections or necessary amendments.

+

The intention is to coordinate the initiation of revisions and to +maintain, to the greatest extent possible, one common ISO/CalConnect +Standard on a given subject.

+

When a joint deliverable is deemed to be updated, both parties agree that each +other has the first right of refusal.

+

The revisions shall be published jointly as described +in Appendix C.8.

+

E.2.  Systematic review and outcome

Joint publications that have been published for four (4) years since +their last approval date shall be reviewed in their entirety by the +responsible JMG, as determined by the JCG.

+

A decision shall be made by both parties at the end of the review +period, on whether to:

+
    +
  1. +

    confirm the standard, for which no change is necessary;

    +
  2. +
  3. +

    revise, as a new joint work item; or

    +
  4. +
  5. +

    withdraw the standard.

    +
  6. +
+

The decided action shall be initiated within five (5) years of the last +approval date.

+

NOTE  The four (4) years review period provides a one (1) year +timeframe for which a review decision can be made, in accordance with +ISO 1 (all parts) and CC/DIR 10001 where a maximum of five (5) years is +allowed between reviews.

+

E.3.  Participation

E.3.1.  Agree to jointly maintain

When both the ISO TC and CalConnect agree to jointly revise the +standard, a joint maintenance group (JMG) is established consisting of +nominated experts from the relevant CalConnect and ISO TCs.

+

ISO and CalConnect mutually agree on a Convener for the MG.

+

E.3.2.  Non-participation of ISO TC

If CalConnect initiates revision to the document and the relevant ISO +TC decides not to participate in the revision process, ISO shall ensure +that the ISO/CalConnect Standard is not revised until CalConnect has +completed its revision.

+

Once the document has been revised, CalConnect may submit the document +to ISO as a potential new Standard for FDIS fast-track approval to +supercede the earlier ISO/CalConnect Standard.

+

Should the revised document not be submitted by CalConnect, or accepted +by the relevant ISO Committee, the original ISO FDIS fast track +Standard shall be withdrawn, unless otherwise agreed by both +organizations.

+

E.3.3.  Non-participation of CalConnect

If ISO initiates the revision and CalConnect decides not to participate +in the process, then ISO may continue to revise the Standard.

+

However, any material used from the original ISO/CalConnect Standard +will require a separate agreement with CalConnect.

+

E.4.  Comment distribution

+ +

When a party receives formal comments on the joint work item, it shall +share it with the other party within 2 weeks of receiving them, +documented and distributed through the JCG.

+
+

E.5.  Withdrawal

+ +

When a review determines that a joint published item should be +withdrawn, both parties agree that the item to be indicated as +withdrawn.

+
+

E.6.  Revision of deliverables

E.6.1.  Initiation of revision process

+ +

Revisions to joint publications can be proposed to the relevant +CalConnect or ISO TC at any time by members of CalConnect or the +ISO TC.

+
+

E.6.2.  Amendments and full revisions

+ +

Amendments and full revisions of a joint deliverable +are considered joint new work items, and shall be developed in +accordance with the procedures in Appendix C.

+
+

E.6.3.  Corrections

+ +

Corrections, such as technical corrigenda, of an ISO/CalConnect +standard, shall be jointly developed by the appropriate ISO TC +and CalConnect TC in accordance with each organizations’ internal +procedures.

+
+

E.7.  Maintenance agency and registration authority

+ +
+

E.8.  General

+ +

Both organizations recognize that a maintenance agency or +registration authority is required for the successful implementation of +certain standardization deliverables resulting from this agreement.

+
+

E.9.  Default volunteer role

For standards developed under this agreement, CalConnect volunteers +to serve as their maintenance agency or registration authority as +necessary.

+

CalConnect shall submit a suitable application to ISO once a NWIP +requiring establishment of a maintenance agency or registration +authority for a joint work item is approved.

+
+
+
+

Appendix F
(normative)
Deliverable requirements

+

F.1.  Document layout

+ +

CalConnect and ISO will establish a consistent layout, including +associated supporting information (e.g. foreword, introduction), for +joint publications.

+
+ +

F.3.  Patent statement

+ +

A suitable patent statement in accordance with the ISO patent policy +and the CalConnect patent policy shall be stated in the foreword +of the document.

+
+

F.4.  Publication dates

+ +

The edition year and the year of publishing of a joint deliverable +shall be identical in the ISO and CalConnect deliverables.

+
+

F.5.  Cover page

In ISO and CalConnect publications of the joint publication, +as well as any further adoptions, shall retain the logographic marks +of both organizations.

+

The joint publication shall also provide a single document identifier +on the cover page.

+

F.6.  Introduction part

+ +

The introduction shall state that it is a joint work product +between ISO and CalConnect.

+
+

F.7.  Document identifier and references

ISO publications published through joint publication under this +agreement will be referenced with the following prefixes:

+
    +
  • +

    “ISO/CC” in ISO documents

    +
  • +
  • +

    “CC/ISO” in CalConnect documents

    +
  • +
+

In case that a joint publication is performed under ISO/IEC JTC 1, +the resulting prefixes are:

+
    +
  • +

    “ISO/IEC/CC” in ISO and IEC documents;

    +
  • +
  • +

    “CC/ISO/IEC” in CalConnect documents

    +
  • +
+

References shall contain sufficient information for those wishing +to obtain the equivalent documents of the other party to be +able to do so.

+

EXAMPLE 1

+

In the document identifier “ISO/CC 18001:2018”, “ISO/CC” is the prefix, +“18001” the project code, and “2018” the edition date.

+
+

EXAMPLE 2

+

In the document identifier “ISO/IEC/CC 28001:2018”, “ISO/IEC/CC” is the +prefix, “28001” the project code, and “2018” the edition date.

+
+

F.8.  Project code

A mutually acceptable number will be used for the project code, with +the goal of achieving identical deliverable numbers in ISO and +CalConnect to prevent potential ambiguity.

+

ISO and CalConnect shall also give consideration to any previous numbering +used by ISO or CalConnect to determine the number designation for the +Standards developed in accordance with this agreement.

+

F.9.  Editorial work

ISO and CalConnect will perform final editorial/production work on the +joint work item with approval of the final proof by both parties prior +to ISO publication.

+

CalConnect and ISO will not charge each other for any editing or +production work undertaken in development of the final +ISO/CalConnect Standard.

+
+
+

Bibliography

+

[1]  WTO TBT Agreements, World Trade Organization, The WTO Agreements Series Technical Barriers to Trade

+ +
+
+ + + + + + + + + + + + + diff --git a/documents/cc-10010.pdf b/documents/cc-10010.pdf new file mode 100644 index 0000000..3d08685 Binary files /dev/null and b/documents/cc-10010.pdf differ diff --git a/documents/cc-10010.rxl b/documents/cc-10010.rxl new file mode 100644 index 0000000..e95ad38 --- /dev/null +++ b/documents/cc-10010.rxl @@ -0,0 +1,44 @@ + +ISO/CalConnect Partner Standards Development Organization (PSDO) Cooperation Agreement +CC/FDS 10010:2019 +10010 + +2019-01-18 + + + + +CalConnect + + + + + +CalConnect + + +1 + +2019-01-18 + + +en + + +final-draft + + +2019 + + +CalConnect + + + + +standard + +PUBLISH + + + \ No newline at end of file diff --git a/documents/cc-10010.xml b/documents/cc-10010.xml new file mode 100644 index 0000000..a831b7c --- /dev/null +++ b/documents/cc-10010.xml @@ -0,0 +1,1006 @@ + + + +ISO/CalConnect Partner Standards Development Organization (PSDO) Cooperation Agreement +CC/FDS 10010:2019 +10010 + +2019-01-18 + + + + +CalConnect + + + + + +CalConnect + + +1 + +2019-01-18 + + +en + + +final-draft + + +2019 + + +CalConnect + + + + +standard + +PUBLISH + + + + + + +

© 2019 The Calendaring and Scheduling Consortium, Inc.

+
+
+ + + + + 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. +

+
+
+ + + + +

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
+
+ copyright@calconnect.org
+ www.calconnect.org +

+
+
+
+ +Foreword

The Calendaring and Scheduling Consortium (“CalConnect”) is a global +non-profit organization that pursues the wide availability of truly +interoperable collaboration systems and applications through the use of +open standards. +CalConnect works closely with liaison partners and international +standard organizations including ISO, OASIS and M3AAWG.

+

ISO (the International Organization for Standardization) +is a worldwide federation of national standards bodies (ISO member +bodies). The work of preparing International Standards is normally +carried out through ISO technical committees. Each member body +interested in a subject for which a technical committee has been +established has the right to be represented on that committee. +International organizations, governmental and non-governmental, in +liaison with ISO, also take part in the work. ISO collaborates closely +with the International Electrotechnical Commission (IEC) on all matters +of electrotechnical standardization.

+

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 the Joint Coordination Group of +ISO and CalConnect.

+

This is the first edition of this document.

IntroductionPurpose

The purpose of this document is to establish an understanding between +ISO and CalConnect on cooperation on standards +development.

+

This document formalizes the process of collaboration of +ISO and CalConnect to cooperate and to +enable the collaborative development of standards.

+

The resulting standards are to be jointly published by +ISO and CalConnect as “ISO/CalConnect Standards”, +according to processes described in this document.

+Background

One of the objectives of ISO is to facilitate the international +exchange of goods and services through the development of International +Standards.

+

The ISO Council has adopted a policy of inclusiveness +and encourages cooperation between ISO and other standardizing bodies, +where such cooperation would serve to ensure effective and efficient +use of resources available for standardization activities.

+

CalConnect aims to facilitate interoperability of collaborative +technologies with open standards, in particular on calendar, scheduling, +and contacts; its standards are globally recognized and widely applied.

+ +Intention +

ISO and CalConnect agree to the principles of cooperation described in +this document, in all fields subject to approval by the ISO TMB and the +CalConnect TC PUBLISH and TCC.

+
+Process cooperation

ISO and CalConnect wish to avoid duplication of efforts by their +respective committees.

+

ISO produces International Standards in accordance with processes +described in and , with the standard documents +drafted in accordance with the editorial rules of .

+

CalConnect creates publicly available CalConnect Standards through +a consensus-based standardization process described in , and +standard documents created in accordance with .

+

Both ISO and CalConnect believe that cooperation at +the standards development process level provides the following benefits:

+
    +
  • +

    maximizes the deliverable expertise of their experts; and

    +
  • +
  • +

    maximizes the quality of the resulting International Standard.

    +
  • +
+

This agreement facilitates a collaborative development process +for the creation of joint publications (ISO/CalConnect Standards) +between ISO and CalConnect.

+ +Scope

This document describes the agreement between CalConnect and ISO for +the cooperation of standards development and publication.

+

Specifically, it provides the principles and necessary processes for these +collaborative cases between ISO and CalConnect (“Parties”):

+
    +
  • +

    co-development of a standardization work item, proposed by either party

    +
  • +
  • +

    submission of a CalConnect document to ISO for its +standardization process

    +
  • +
+

Standardization processes in this document is intended to align +with , , and .

+ +Terms and definitions

For the purposes of this document, the terms and definitions + given in and the following apply.

+Terms and definitions +ISO members +

ISO member bodies and correspondent members

+
+ +CalConnect members +

CalConnect member bodies

+
+ISO committee +ISO TC + +

ISO Technical Committee (including ISO/IEC JTC1) or Subcommittee

+CalConnect technical committee +CalConnect TC + +

internal committee of CalConnect tasked with a scope of work it +is responsible for

+ +standardization project +

an organized process with one or more standardization work items that +contributes towards a defined scope of work

+
+ +standardization work item +

publishable work item that creates output that relates +to standardization within a standardization project ()

+
+ +project owner +

entity with authority in charge of a standardization project +()

+
+ +document +

written output of a work item

+
+CalConnect deliverable

document () produced by a CalConnect TC +() as described in

+ +

According to , CalConnect deliverables include the +following types: CalConnect Standard, Guide, Specification, Report and +Directives. Directives are not considered a standardization work item.

+
+ISO TC deliverable

document () produced by an ISO TC +() as described in

+ +

According to , ISO TC deliverables include the +following types: International Standards, Technical Specifications, +Publicly Available Specifications and Technical Reports.

+
+ +document stage +

stage of document as specified in the ISO harmonized stages (as defined +in )

+
+standardization project output

output of a standardization project ()

+ +

In this document, it explicitly means any documents and IP rights +produced by the standardization project.

+
+ +proposal for standardization +

proposal for a new work item for standardization

+
+ +co-develop +

act of developing a work item by multiple parties from the proposal stage

+
+ +co-publish +

act of publishing documents () of identical content +by multiple parties

+
+ +joint work item +

work item co-developed () by both parties

+
+ +joint deliverable +

completed form of a joint work item that is designated to be +co-published () by ISO +and CalConnect

+
+joint publication

publication that is co-published () by +ISO and CalConnect

+ +

Different publishers of a joint publication may utilize a +different document layout.

+
+Joint Coordination Group +JCG + +

advisory group with representatives from ISO and CalConnect on +the execution and maintenance of this agreement

+joint project group +JPG + +

group created to be project owner () of a joint work item (), +composed of participants from ISO committees () and CalConnect TCs ()

+joint maintenance group +JMG + +

joint project group () for the sole +purpose of maintaining a +joint publication ()

+ +co-development document register +

document register of a list of co-developed () +documents () developed under this agreement, +held by the Joint Coordination Group ()

+
+ +Abbreviations +
IPR
+

Intellectual Property Rights

+
+
TCC
+

CalConnect Technical Coordination Committee

+
+
TMB
+

ISO Technical Management Board

+
+
+Principles of cooperationCollaborative development process

A collaborative development process is crucial to effective development +of work items between ISO and CalConnect.

+

Both organizations agree to align appropriate internal processes +and procedures in order to facilitate joint development of work items.

+

Three mechanisms are provided below for cooperative development of +joint publications between ISO and CalConnect, namely:

+
    +
  1. +

    CalConnect contributes content to ISO;

    +
  2. +
  3. +

    ISO and CalConnect co-develop a joint deliverable;

    +
  4. +
  5. +

    Adoption of an existing standard from either party.

    +
  6. +
+ +Central coordination group +

ISO and CalConnect agree to the establishment of a joint coordination group +(JCG) to coordinate matters relevant to the execution and maintenance +of this agreement.

+
+Across subject fields

ISO and CalConnect agree that this agreement applies to all subject fields +subject to approval by both parties.

+

Details of implementation are provided in .

+Normative referencing

ISO and CalConnect agree to the normative referencing of their +standards as appropriate in publications of the other organization in +compliance with each organization’s policies and directives relative to +normative references.

+

Implementation details are provided in .

+Patent policy

ISO and CalConnect agree that content of joint deliverables, +including the ISO published form of joint publications, +will remain free of IPR restrictions that would limit their application.

+

Patented content in a joint deliverable is governed by the +ISO patent policy and the CalConnect IPR policy.

+

Any patents involved knowingly in the document shall be made +transparent prior to the DIS stage of the joint deliverable.

+Contributions to ISO standards

ISO International Standards are normally developed within ISO +Committees. As part of this normal development process, an ISO +committee may determine that specific elements of an CalConnect +standard (e.g. figures, data, definitions), along with information from +other sources, would contribute to the development of an ISO Standard.

+

As specified in the , original material contributed to +become part of an ISO publication is normally copied and distributed +within the ISO system as part of the consensus-building process, this +being without prejudice to the rights of the original copyright owner +to exploit the original text.

+

It is also recognized that, where such material is already subject to +copyright, rights have to be granted to ISO to reproduce and circulate +the material.

+

As part of this agreement, CalConnect grants a licence to ISO described +in +for using elements of a CalConnect standard in the development of joint +publications.

+Co-development of standards

In cases where CalConnect has developed a standard, or where CalConnect +is proposing or developing a standard (yet unpublished), which +corresponds to a stated ISO TC need covered by this agreement.

+

In these instances, the relevant ISO TC and CalConnect TC +may agree that it would be mutually beneficial to develop work jointly.

+

ISO and CalConnect agree to a coordinated and specified process for the +co-development of joint publications.

+

The detailed process and procedures are provided in ; copyright of the +resulting deliverables is explained in .

+Adoption of existing standardsGeneral

ISO and CalConnect agree to a coordinated and specified process for the +adoption of either party’s standardization work items, where:

+
    +
  • +

    CalConnect may wish to formally adopt a published ISO +International Standard;

    +
  • +
  • +

    CalConnect may propose that an existing CalConnect standard be +submitted as a final draft International Standard (FDIS) at ISO.

    +
  • +
+

Copyright of joint publications created through adoption is +explained in .

+Adoption of an ISO Standard by CalConnect

CalConnect may wish to formally adopt a published ISO International +Standard.

+

In this case, the source party is ISO and the adopting party +is CalConnect.

+

The method of adoption is specified in .

+Adoption of a CalConnect Standard by ISO

A published CalConnect standard with global use and acceptance may be +proposed for adoption as an ISO International Standard, through the +FDIS fast-track procedure of submitting a CalConnect standard to ISO.

+

In this case, the source party is CalConnect and the adopting party +is ISO.

+

The method of adoption is detailed in .

+Maintenance of joint publications

Maintenance of joint publications shall be a joint responsibility under +a joint process.

+

Details of the implementation of this clause is described in .

+

In joint publications where a maintenance agency or registration authority +is necessary, CalConnect agrees to serve as the default volunteer, as +described in .

+Mutual recognition and joint deliverables requirements

ISO and CalConnect shall establish rules to ensure +the collaborative effort by both parties are mutually +recognized within joint deliverables.

+

The associated requirements are provided in .

+ +Promotional activities +

ISO and CalConnect agree to share and coordinate promotional activities +for the joint publication via the JCG.

+
+Joint Coordination GroupGeneral

ISO and CalConnect agrees to establish a standing body, +the Joint Coordination Group (“JCG”), for:

+
    +
  • +

    maintenance and execution of this agreement; and

    +
  • +
  • +

    coordination and maintenance of procedures between two organizations.

    +
  • +
+ +Mediator for coordination issues +

This group meets as necessary and serves as the forum for discussing +and resolving issues relating to coordination that may arise from time to time.

+
+Coordination role

The JCG will support the individual liaisons between +ISO Technical Committee working groups and project teams, +with CalConnect technical committees.

+

The presence of the JCG is not intended to affect +responsibilities of existing organizational structures +in ISO and CalConnect.

+ +Fields of collaboration +

The JCG is responsible with the determination of the subject fields +of which this agreement applies to, subject to approval by +the ISO Technical Management Board and the CalConnect TC PUBLISH and TCC.

+
+Members

The JCG is composed of an equal number of representatives from both parties:

+
    +
  • +

    Two representatives from ISO

    +
  • +
  • +

    Two representatives from CalConnect

    +
  • +
+ +Amendments to this agreement +

ISO and CalConnect agree that changes to this agreement shall be +first proposed through the JCG, and formalized by a resolution from one +party to the other.

+
+ + + + + + +
Publication, copyright and commercial arrangementsNormative referencing of standards

ISO and CalConnect acknowledge that all documents, +data or electronic files provided by each consisting of or relating to +joint publications are copyrighted property and data and will not be +supplied to any other party without the prior written consent of the +copyright owner, and will not be used, in whole or in part, as a basis +for a joint publication without following specific procedures established by the +respective copyright owner.

+

Each organization will promptly notify the +other if it becomes aware of infringements or imitations by others of +a joint publication.

+CalConnect content license for joint development

In the development, review and adoption process, ISO members are free to copy and +distribute the relevant CalConnect documents for standards development +purposes and in accordance with ISO policies for the circulation of +draft standards and working documents.

+

CalConnect grants ISO a world-wide, non-exclusive, non-sub-licensable +license (except for national body adoption), +to use contents of CalConnect submitted documents to ISO, +within the development, review and adoption process of the +deliverables under this agreement.

+Copyright and exploitation rightsOf adopted standards

The copyright in any resulting ISO/CalConnect International Standard(s) published according to +, including any future versions of such Standard(s), remain with +the source party.

+

The adopting party will neither acquire nor assert copyright ownership or any +other proprietary rights in these ISO/CalConnect International Standard(s).

+

The source party retains all copyrights in the CalConnect Product(s) and +ISO/CalConnect International Standard(s) not specifically granted +hereunder.

+

Subject to the exploitation rights granted above, development by the adopting party (or its members) +of any other work affecting the integrity of the source standard or the ISO/CalConnect International +Standard(s) would need a separate agreement with the source party.

+Of jointly developed standards

Joint deliverables developed through the joint development process according to +, +copyright ownership will be held jointly by ISO +and CalConnect with normal exploitation rights for CalConnect and for +ISO and its members, including for national adoption purposes.

+

ISO and CalConnect may each sell and distribute the jointly developed standard, +in accordance with their own rules, without any royalties to the other.

+

The resulting joint publication is common to both organizations.

+Re-publishing

ISO and CalConnect agree that any re-publishing of content +developed under this agreement, such as the national adoption +of a joint publication by an ISO member body, or the re-publishing +of a joint publication by another organization, +will adhere to this agreement.

+

Publishing arrangements between ISO and ISO member countries are +unchanged by this agreement.

+ +Statement indicating source +

ISO and CalConnect agree that the resulting publication created with +the joint deliverable will contain a suitable statement that describes +the base standard the joint deliverable was derived from.

+
+Notification of right infringement

Each party shall promptly inform the other party if it becomes aware of +any copyright infringement or potential infringement of a joint publication.

+

CalConnect and ISO shall consult with each other to decide the best +way to respond to such infringement.

Alignment of project timelineProject stage mapping

The following table provides a mapping between ISO project stages and +CalConnect project stages. This document identifies stages +according to the ISO project stage names.

+ +Alignment between ISO and CalConnect project stages + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Identification in this documentISO harmonized stage ()CalConnect stage
+Preliminary +00 Preliminary00 Preliminary
+Proposal +10 Proposal10 Proposal
+Preparatory +20 Preparatory20 Preparatory
+Committee +30 Committee30 Committee
+Enquiry +40 Enquiry40 Enquiry
+Approval +50 Approval50 Approval
+Publication +60 Publication60 Publication
+Review +90 Review90 Review
+Withdrawal +95 Withdrawal95 Withdrawal
+Track synchronization

ISO deliverables can be developed according to different tracks +and timelines detailed in and .

+

CalConnect deliverables are developed according to the +timelines detailed in .

+

For a project under this agreement, CalConnect agrees to adopt +a developmental track not slower than the track selected in +ISO to ensure the synchronicity between +development outcome and publication.

Co-development processGeneral

In joint development, technical level support for the development of +these standards is provided through the associated CalConnect TC as +well as the ISO member bodies and their duly appointed technical +experts through the relevant ISO TC.

+

Experts in ISO are encouraged to participate in the +technical work on CalConnect technologies by participating in +CalConnect technical committees.

+First draft

A first draft of the standardization deliverable may be created +for proposal submission, or may be created in the Committee stage. +The draft shall be created through a collaboration process between +experts from both organizations, or at least, the proposing +organization should have received input from the other organization.

+

CalConnect agrees that any draft submitted to ISO +shall adhere to the requirements detailed in , and +applicable internal guidelines of ISO.

+Disapproval and continuance

If the project proposal is rejected by the JCG, its output may still be +developed by the project proposer if appropriate, and its output may +still be proposed to the JCG for co-development in later stages.

+

At any time, if a ballot to approve the development of a joint work item +is disapproved by ISO or CalConnect, each organization may proceed +to develop the joint work item independently of each other.

+Proposal development: Preliminary stageGeneral

At the first instance where either party wishes to co-develop +a project with the other party, it should be raised to the JCG.

+

The JCG shall consult the stakeholders to determine appropriateness +of the project and advise the proposer.

+ +Initiation by CalConnect +

CalConnect may propose to the appropriate ISO TC(s) to +jointly develop a new or existing CalConnect standard +to gain recognition as an ISO/CalConnect Standard.

+
+ +Initiation by ISO TC +

If an ISO TC wishes to initiate the joint development of a +standard, the ISO TC secretariat shall contact the appropriate +CalConnect TC to gauge mutual interest.

+
+Proposal submission: Proposal stage +General +

When the JCG determines interest within ISO to co-develop the +proposed project, the project proposer should submit a proposal +indicating its wish to co-develop the proposed project, +to be approved by the relevant ISO and CalConnect TCs via ballot.

+
+Initiation by CalConnect

CalConnect shall provide a NWIP in accordance with for the +proposal of new work items.

+

In addition, the NWIP shall include:

+
    +
  • +

    rationale for using this process; and

    +
  • +
  • +

    justification of the need for an ISO/CalConnect International +Standard.

    +
  • +
+Initiation by ISO TC

An ISO member shall submit a NWIP to the ISO TC for approval +in accordance with .

+

Concurrently, the corresponding CalConnect TC will submit a +project proposal to the CalConnect TCC, providing the relevant +information for the project and a statement that the project +is to be developed jointly with the relevant ISO TC.

+Fast-track proposal at ISO

When the ISO NWIP is accompanied by an existing CalConnect standard, +members of the ISO TC will be invited to approve its submission as a DIS.

+ +

A two-thirds (2/3) majority vote of participating ISO P-members +is required for approval ().

+
+Approval of co-development

If both organizations approve the proposal for joint development, +the project shall be adopted on both sides by a CalConnect +TC and an ISO TC.

+

The JCG shall then create a joint project group to be the project +owner of the proposed joint work item through the CalConnect TCC and the +secretariat of the ISO TC, consisting of nominated experts from the +relevant CalConnect and ISO TCs.

+

ISO and CalConnect will mutually agree on a Convener for the JPG.

+

This approved project shall be listed in the JCG register of +co-developed projects.

+Content development: Preparatory, Committee, Enquiry stagesGeneral

The goal of these stages are to create an approved, balloted +draft of the joint deliverable by both parties.

+

In these stages, members of the joint project group shall +collaborate closely to ensure efficient and effective +development of the deliverable of the respective stages. +The deliverable shall be developed jointly by experts of +both organizations.

+Stage synchronization

The approval process at CalConnect and ISO shall be adhered to. +CalConnect agrees to synchronize its project stage with +the corresponding ISO project stage.

+

Specifically:

+
    +
  • +

    If a deliverable is approved by ballot at both ISO and CalConnect, +CalConnect will advance the project stage at its +project group accordingly.

    +
  • +
  • +

    If a deliverable is rejected by ballot at either party, +CalConnect will not advance project stage at its +project group, unless a re-ballot at ISO approves +advancement of the deliverable.

    +
  • +
  • +

    In cases where a development stage is optional and skipped +in accordance with and , CalConnect +shall set the stage of its project at the corresponding +stage.

    +
  • +
+Approval of a committee draft

Once consensus is reached within the JPG, the draft is circulated to +the relevant ISO and CalConnect TCs for three-month comment.

+

The JPG prepares a compilation of comments received from both +organizations and develops a revised draft.

+Approval of a draft standard

Once consensus within the JPG is achieved, the draft is provided to ISO +for DIS ballot and CalConnect for DS ballot.

+

Once balloting and approval at that stage, from both organizations, is +completed, the JPG prepares the document for circulation by ISO for a +two-month FDIS vote (according to , unanimous approval in +ISO during DIS ballot implies that a further FDIS ballot is not +necessary).

+

In parallel, CalConnect submits the draft to the CalConnect TCC for FS +ballot.

+Approval for publication

The document is considered approved when:

+
    +
  • +

    ISO achieves the requisite FDIS approval (or unanimous DIS approval), +in accordance with , and;

    +
  • +
  • +

    CalConnect TCC has provided its requisite approval, in accordance +with .

    +
  • +
+

Once the document has been approved by both ISO and CalConnect, the +document is published as a joint ISO/CalConnect standard.

+Pre-publication: Public review

A public review period of 60 days is required for the compliance +to rules, for which both ISO and CalConnect adhere to.

+

A 60-day public review shall be held in the DIS stage of the ISO deliverable.

+

Comments to ISO shall be performed according to and ; +comments to CalConnect shall be performed through CalConnect’s public review procedure.

+

The parties agree to synchronize the dates of review periods for the +maximum benefit to the joint work item.

+Publication +As a CalConnect Standard +

After an ISO ballot on the acceptance of a joint work item as +DIS, FDIS or IS, the joint work item will be published +as a CalConnect Standard.

+
+ +As an ISO/CalConnect Standard +

After an ISO ballot on the acceptance of a joint work item’s status +to proceed to IS from FDIS, the joint work item will be published by +ISO and CalConnect as an ISO/CalConnect Standard.

+
+Abandonment

A joint work item may be abandoned by one of the two parties if it sees +it being inappropriate or is no longer interested or able to contribute +to the joint work item. Each party is allowed to abandon the joint +work, which at that point will become sole work of the other party.

+

A notice of such must be sent by the abandoning party to the JCG and +distributed by both parties to its members.

+

The abandoning party, if the abandoned work is carried on by the other +party, is required to explicitly agree that the copyright of such work +is to be waived to the continuing party to allow publication of the document.

+

The rejoining an abandoned work item prior to publication, by the abandoning party, +is explicitly allowed by this agreement, given a notice is filed at +the JCG, unless in exceptional circumstances.

+ +Additional collaborators +

Parties may bring in additional collaborators under this agreement, +given it is approved by the JCG, that the provisions of this agreement +are fully satisfied by agreements present between all collaborators.

+
+ +Notification +

Notification of availability of new documents within CalConnect +will be announced to the appropriate ISO TCs and CalConnect TCs.

+
+ +Availability of working documents +

Drafts and working documents are available according to +each party’s normal practices.

+
Adoption processGeneral

ISO and CalConnect agree to a coordinated and specified process for the +adoption of either party’s standardization work items, where:

+
    +
  • +

    CalConnect may wish to formally adopt a published ISO International Standard;

    +
  • +
  • +

    CalConnect may propose that an existing CalConnect standard be +submitted as a final draft International Standard (FDIS) at ISO.

    +
  • +
+Adoption of an ISO Standard by CalConnect

CalConnect may wish to formally adopt a published ISO International +Standard as described in ,

+

Such adoption shall be subject to an agreement between CalConnect and +the ISO member body in the country where CalConnect has its legal seat +(ANSI).

+Adoption of a CalConnect Standard by ISOGeneral

As described in , a CalConnect +standard may be adopted by ISO.

+

The adoption of a CalConnect standard at ISO is through FDIS fast-track +as described in this clause.

+

Adoption by ISO FDIS approval is intended to validate an existing +CalConnect standard through ISO’s established member body approval +mechanism.

+Initiation by CalConnect

CalConnect may propose an existing CalConnect standard to be submitted +as a final draft International Standard (FDIS) at ISO.

+

Such requests shall be submitted to the Secretary-General of ISO for +acceptance.

+

The ISO Secretary-General shall then submit a proposal to the relevant +ISO committee for a 30-day ballot which shall decide, by simple majority +vote, on:

+
    +
  1. +

    the need for an ISO International Standard on the subject; and

    +
  2. +
  3. +

    submission of the proposal for FDIS ballot.

    +
  4. +
+Initiation by ISO

Any ISO TC may decide to invite, by simple majority vote, CalConnect to +offer a particular CalConnect standard for adoption under this +agreement, provided agreement has been obtained from CalConnect.

+

Where an ISO TC confirms the need for an ISO International Standard, +but determines that the proposed CalConnect standard should not be +submitted for FDIS ballot, CalConnect shall be consulted on its +interest to proceed with the project jointly.

+Approval

Requirements for acceptance shall be those pertaining to the FDIS +approval stage in .

+

Upon acceptance by CalConnect and the relevant ISO TC, the CalConnect +standard shall be circulated to ISO members for a five-month approval +vote (to also allow for national public review and, where necessary, +translation).

+

The adoption is considered approved once the FDIS ballot is approved.

+

The process described in also applies.

Maintenance of joint deliverablesGeneral

The project groups in both organizations responsible for +the published deliverable shall work in collaboration to +address any corrections or necessary amendments.

+

The intention is to coordinate the initiation of revisions and to +maintain, to the greatest extent possible, one common ISO/CalConnect +Standard on a given subject.

+

When a joint deliverable is deemed to be updated, both parties agree that each +other has the first right of refusal.

+

The revisions shall be published jointly as described +in .

+Systematic review and outcome

Joint publications that have been published for four (4) years since +their last approval date shall be reviewed in their entirety by the +responsible JMG, as determined by the JCG.

+

A decision shall be made by both parties at the end of the review +period, on whether to:

+
    +
  1. +

    confirm the standard, for which no change is necessary;

    +
  2. +
  3. +

    revise, as a new joint work item; or

    +
  4. +
  5. +

    withdraw the standard.

    +
  6. +
+

The decided action shall be initiated within five (5) years of the last +approval date.

+ +

The four (4) years review period provides a one (1) year +timeframe for which a review decision can be made, in accordance with + and where a maximum of five (5) years is +allowed between reviews.

+
+ParticipationAgree to jointly maintain

When both the ISO TC and CalConnect agree to jointly revise the +standard, a joint maintenance group (JMG) is established consisting of +nominated experts from the relevant CalConnect and ISO TCs.

+

ISO and CalConnect mutually agree on a Convener for the MG.

+Non-participation of ISO TC

If CalConnect initiates revision to the document and the relevant ISO +TC decides not to participate in the revision process, ISO shall ensure +that the ISO/CalConnect Standard is not revised until CalConnect has +completed its revision.

+

Once the document has been revised, CalConnect may submit the document +to ISO as a potential new Standard for FDIS fast-track approval to +supercede the earlier ISO/CalConnect Standard.

+

Should the revised document not be submitted by CalConnect, or accepted +by the relevant ISO Committee, the original ISO FDIS fast track +Standard shall be withdrawn, unless otherwise agreed by both +organizations.

+Non-participation of CalConnect

If ISO initiates the revision and CalConnect decides not to participate +in the process, then ISO may continue to revise the Standard.

+

However, any material used from the original ISO/CalConnect Standard +will require a separate agreement with CalConnect.

+ +Comment distribution +

When a party receives formal comments on the joint work item, it shall +share it with the other party within 2 weeks of receiving them, +documented and distributed through the JCG.

+
+ +Withdrawal +

When a review determines that a joint published item should be +withdrawn, both parties agree that the item to be indicated as +withdrawn.

+
+Revision of deliverables +Initiation of revision process +

Revisions to joint publications can be proposed to the relevant +CalConnect or ISO TC at any time by members of CalConnect or the +ISO TC.

+
+ +Amendments and full revisions +

Amendments and full revisions of a joint deliverable +are considered joint new work items, and shall be developed in +accordance with the procedures in .

+
+ +Corrections +

Corrections, such as technical corrigenda, of an ISO/CalConnect +standard, shall be jointly developed by the appropriate ISO TC +and CalConnect TC in accordance with each organizations’ internal +procedures.

+
+ +Maintenance agency and registration authority + + +General +

Both organizations recognize that a maintenance agency or +registration authority is required for the successful implementation of +certain standardization deliverables resulting from this agreement.

+
+Default volunteer role

For standards developed under this agreement, CalConnect volunteers +to serve as their maintenance agency or registration authority as +necessary.

+

CalConnect shall submit a suitable application to ISO once a NWIP +requiring establishment of a maintenance agency or registration +authority for a joint work item is approved.

Deliverable requirements +Document layout +

CalConnect and ISO will establish a consistent layout, including +associated supporting information (e.g. foreword, introduction), for +joint publications.

+
+ +Trademark and copyright statements +

Similar to the process applied on national adoption +of an ISO deliverable, trademarks and copyright statements +of both organizations shall appear on the document cover page as +well as in the foreword.

+
+ +Patent statement +

A suitable patent statement in accordance with the ISO patent policy +and the CalConnect patent policy shall be stated in the foreword +of the document.

+
+ +Publication dates +

The edition year and the year of publishing of a joint deliverable +shall be identical in the ISO and CalConnect deliverables.

+
+Cover page

In ISO and CalConnect publications of the joint publication, +as well as any further adoptions, shall retain the logographic marks +of both organizations.

+

The joint publication shall also provide a single document identifier +on the cover page.

+ +Introduction part +

The introduction shall state that it is a joint work product +between ISO and CalConnect.

+
+Document identifier and references

ISO publications published through joint publication under this +agreement will be referenced with the following prefixes:

+
    +
  • +

    “ISO/CC” in ISO documents

    +
  • +
  • +

    “CC/ISO” in CalConnect documents

    +
  • +
+

In case that a joint publication is performed under ISO/IEC JTC 1, +the resulting prefixes are:

+
    +
  • +

    “ISO/IEC/CC” in ISO and IEC documents;

    +
  • +
  • +

    “CC/ISO/IEC” in CalConnect documents

    +
  • +
+

References shall contain sufficient information for those wishing +to obtain the equivalent documents of the other party to be +able to do so.

+ +

In the document identifier “ISO/CC 18001:2018”, “ISO/CC” is the prefix, +“18001” the project code, and “2018” the edition date.

+
+ +

In the document identifier “ISO/IEC/CC 28001:2018”, “ISO/IEC/CC” is the +prefix, “28001” the project code, and “2018” the edition date.

+
+Project code

A mutually acceptable number will be used for the project code, with +the goal of achieving identical deliverable numbers in ISO and +CalConnect to prevent potential ambiguity.

+

ISO and CalConnect shall also give consideration to any previous numbering +used by ISO or CalConnect to determine the number designation for the +Standards developed in accordance with this agreement.

+Editorial work

ISO and CalConnect will perform final editorial/production work on the +joint work item with approval of the final proof by both parties prior +to ISO publication.

+

CalConnect and ISO will not charge each other for any editing or +production work undertaken in development of the final +ISO/CalConnect Standard.

Normative References

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.

CalConnect Directive: Standardization and publicationCC/DIR 1000110001CalConnect Directive: Standard document requirementsCC/DIR 1000210002 2020-06-16 Geometrical product specifications (GPS) Standard reference temperature for the specification of geometrical and dimensional properties Geometrical product specifications (GPS) – Standard reference temperature for the specification of geometrical and dimensional properties Spécification géométrique des produits (GPS) Température normale de référence pour la spécification des propriétés géométriques et dimensionnelles Spécification géométrique des produits (GPS) – Température normale de référence pour la spécification des propriétés géométriques et dimensionnelles https://www.iso.org/standard/67630.html https://www.iso.org/obp/ui/#!iso:std:67630:en https://www.iso.org/contents/data/standard/06/76/67630.detail.rss ISO 1 (all parts) 1 2016 International Organization for Standardization ISO www.iso.org 3 en fr 60 60 2016 ISO ISO 1:2002 2020-06-16 Geometrical product specifications (GPS) Standard reference temperature for the specification of geometrical and dimensional properties Geometrical product specifications (GPS) – Standard reference temperature for the specification of geometrical and dimensional properties Spécification géométrique des produits (GPS) Température normale de référence pour la spécification des propriétés géométriques et dimensionnelles Spécification géométrique des produits (GPS) – Température normale de référence pour la spécification des propriétés géométriques et dimensionnelles https://www.iso.org/standard/67630.html https://www.iso.org/obp/ui/#!iso:std:67630:en https://www.iso.org/contents/data/standard/06/76/67630.detail.rss ISO 1:2016 1 2016 International Organization for Standardization ISO www.iso.org 3 en fr ISO 1:2016 defines the concepts of a reference temperature and of the standard reference temperature, and specifies the standard reference temperature value for the specification of geometrical and dimensional properties of an object. Some examples of geometrical and dimensional properties include size, location, orientation (including angle), form and surface texture of a workpiece.ISO 1:2016 Standard is also applicable to the definition of the measurand used in verification or calibration. ISO 1:2016 définit les concepts de température de référence et de température normale de référence, et spécifie la valeur de la température normale de référence pour la spécification des propriétés géométriques et dimensionnelles d’un objet. Certains exemples de propriétés géométriques et dimensionnelles incluent la taille, la position, l’orientation (y compris l’angle), la forme et l’état de surface d’une pièce.ISO 1:2016 s’applique aussi à la définition du mesurande utilisé en vérification ou en étalonnage. 60 60 2016 ISO ISO 1:2002 Geneva IWA 1:2005 ISO 1:2002 IWA 1:2001 ISO/TTA 1:1994 ISO/DATA 1:1978 ISO 1:1975 ISO Guide 1:1972 Geneva 2020-06-16 Geometrical product specifications (GPS) Standard reference temperature for the specification of geometrical and dimensional properties Geometrical product specifications (GPS) – Standard reference temperature for the specification of geometrical and dimensional properties Spécification géométrique des produits (GPS) Température normale de référence pour la spécification des propriétés géométriques et dimensionnelles Spécification géométrique des produits (GPS) – Température normale de référence pour la spécification des propriétés géométriques et dimensionnelles https://www.iso.org/standard/67630.html https://www.iso.org/obp/ui/#!iso:std:67630:en https://www.iso.org/contents/data/standard/06/76/67630.detail.rss ISO 1 (all parts) 1 2016 International Organization for Standardization ISO www.iso.org 3 en fr 60 60 2016 ISO ISO 1:2002 2020-06-16 Geometrical product specifications (GPS) Standard reference temperature for the specification of geometrical and dimensional properties Geometrical product specifications (GPS) – Standard reference temperature for the specification of geometrical and dimensional properties Spécification géométrique des produits (GPS) Température normale de référence pour la spécification des propriétés géométriques et dimensionnelles Spécification géométrique des produits (GPS) – Température normale de référence pour la spécification des propriétés géométriques et dimensionnelles https://www.iso.org/standard/67630.html https://www.iso.org/obp/ui/#!iso:std:67630:en https://www.iso.org/contents/data/standard/06/76/67630.detail.rss ISO 1:2016 1 2016 International Organization for Standardization ISO www.iso.org 3 en fr ISO 1:2016 defines the concepts of a reference temperature and of the standard reference temperature, and specifies the standard reference temperature value for the specification of geometrical and dimensional properties of an object. Some examples of geometrical and dimensional properties include size, location, orientation (including angle), form and surface texture of a workpiece.ISO 1:2016 Standard is also applicable to the definition of the measurand used in verification or calibration. ISO 1:2016 définit les concepts de température de référence et de température normale de référence, et spécifie la valeur de la température normale de référence pour la spécification des propriétés géométriques et dimensionnelles d’un objet. Certains exemples de propriétés géométriques et dimensionnelles incluent la taille, la position, l’orientation (y compris l’angle), la forme et l’état de surface d’une pièce.ISO 1:2016 s’applique aussi à la définition du mesurande utilisé en vérification ou en étalonnage. 60 60 2016 ISO ISO 1:2002 Geneva IWA 1:2005 ISO 1:2002 IWA 1:2001 ISO/TTA 1:1994 ISO/DATA 1:1978 ISO 1:1975 ISO Guide 1:1972 Geneva 2020-06-16 Standardization and related activities General vocabulary Standardization and related activities – General vocabulary Normalisation et activités connexes Vocabulaire général Normalisation et activités connexes – Vocabulaire général https://www.iso.org/standard/39976.html https://www.iso.org/obp/ui/#!iso:std:39976:en https://www.iso.org/contents/data/standard/03/99/39976.detail.rss ISO/IEC Guide 2 (all parts) 2 2004 International Organization for Standardization ISO www.iso.org International Electrotechnical Commission IEC www.iec.ch 8 en fr 90 93 2004 ISO/IEC ISO/IEC Guide 2:1996 2020-06-16 Standardization and related activities General vocabulary Standardization and related activities – General vocabulary Normalisation et activités connexes Vocabulaire général Normalisation et activités connexes – Vocabulaire général https://www.iso.org/standard/39976.html https://www.iso.org/obp/ui/#!iso:std:39976:en https://www.iso.org/contents/data/standard/03/99/39976.detail.rss ISO/IEC Guide 2:2004 2 2004 International Organization for Standardization ISO www.iso.org International Electrotechnical Commission IEC www.iec.ch 8 en fr ISO/IEC Guide 2:2004 provides general terms and definitions concerning standardization and related activities. It is intended to contribute fundamentally towards mutual understanding amongst the members of ISO and IEC and the various governmental and non-governmental agencies involved in standardization at international, regional and national levels. It is intended also to provide a suitable source for teaching and for reference, briefly covering basic theoretical and practical principles of standardization, certification and laboratory accreditation.It is not the aim of ISO/IEC Guide 2:2004 to duplicate definitions of terms adequately defined for general purposes in other authoritative international vocabularies.NOTE 1 From this point of view, particular attention is drawn to the International vocabulary of basic and general terms in metrology (VIM) jointly prepared by ISO, IEC, BIPM, IFCC, IUPAC, IUPAP and OIML, and published in 1993 (second edition).NOTE 2 In addition to the terms given in the official languages of ISO and IEC (English, French and Russian), equivalent terms provided by the relevant member bodies are given in the following languages: Le Guide ISO/CEI 2 fournit des termes généraux et leurs définitions concernant la normalisation et les activités connexes. Il est prévu pour contribuer, de manière fondamentale, à la compréhension mutuelle entre les membres de l’ISO, de la CEI et des diverses institutions gouvernementales et non gouvernementales engagées dans la normalisation aux niveaux international, régional et national. Il est prévu également pour constituer un instrument de formation ou de référence couvrant brièvement les principes de base, théoriques et pratiques, de la normalisation, de la certification et de l’accréditation des laboratoires d’essais.L’objet du Guide ISO/CEI 2 n’est pas de redonner les définitions de termes déjà définis de façon satisfaisante dans leur sens général par d’autres vocabulaires internationaux faisant autorité.NOTE 1 Une attention particulière doit être portée, à cet égard, au Vocabulaire international des termes fondamentaux et généraux de métrologie (VIM) préparé conjointement par l’ISO, la CEI, le BIPM, la FICC, l’OIML, l’UICPA et l’UIPPA et qui a été publié en 1993 (deuxième édition).NOTE 2 En plus des termes donnés dans les langues officielles de l’ISO et de la CEI (anglais, français et russe), les termes équivalents fournis par les comités membres responsables sont donnés dans les langues suivantes : 90 93 2004 ISO/IEC ISO/IEC Guide 2:1996 Geneva ISO/TTA 2:1997 ISO 2:1973 IWA 2:2007 IWA 2:2003 ISO/IEC Guide 2:1996 ISO/IEC Guide 2:1991 Geneva 2020-06-16 Standardization and related activities General vocabulary Standardization and related activities – General vocabulary Normalisation et activités connexes Vocabulaire général Normalisation et activités connexes – Vocabulaire général https://www.iso.org/standard/39976.html https://www.iso.org/obp/ui/#!iso:std:39976:en https://www.iso.org/contents/data/standard/03/99/39976.detail.rss ISO/IEC Guide 2:2004 2 2004 International Organization for Standardization ISO www.iso.org International Electrotechnical Commission IEC www.iec.ch 8 en fr ISO/IEC Guide 2:2004 provides general terms and definitions concerning standardization and related activities. It is intended to contribute fundamentally towards mutual understanding amongst the members of ISO and IEC and the various governmental and non-governmental agencies involved in standardization at international, regional and national levels. It is intended also to provide a suitable source for teaching and for reference, briefly covering basic theoretical and practical principles of standardization, certification and laboratory accreditation.It is not the aim of ISO/IEC Guide 2:2004 to duplicate definitions of terms adequately defined for general purposes in other authoritative international vocabularies.NOTE 1 From this point of view, particular attention is drawn to the International vocabulary of basic and general terms in metrology (VIM) jointly prepared by ISO, IEC, BIPM, IFCC, IUPAC, IUPAP and OIML, and published in 1993 (second edition).NOTE 2 In addition to the terms given in the official languages of ISO and IEC (English, French and Russian), equivalent terms provided by the relevant member bodies are given in the following languages: Le Guide ISO/CEI 2 fournit des termes généraux et leurs définitions concernant la normalisation et les activités connexes. Il est prévu pour contribuer, de manière fondamentale, à la compréhension mutuelle entre les membres de l’ISO, de la CEI et des diverses institutions gouvernementales et non gouvernementales engagées dans la normalisation aux niveaux international, régional et national. Il est prévu également pour constituer un instrument de formation ou de référence couvrant brièvement les principes de base, théoriques et pratiques, de la normalisation, de la certification et de l’accréditation des laboratoires d’essais.L’objet du Guide ISO/CEI 2 n’est pas de redonner les définitions de termes déjà définis de façon satisfaisante dans leur sens général par d’autres vocabulaires internationaux faisant autorité.NOTE 1 Une attention particulière doit être portée, à cet égard, au Vocabulaire international des termes fondamentaux et généraux de métrologie (VIM) préparé conjointement par l’ISO, la CEI, le BIPM, la FICC, l’OIML, l’UICPA et l’UIPPA et qui a été publié en 1993 (deuxième édition).NOTE 2 En plus des termes donnés dans les langues officielles de l’ISO et de la CEI (anglais, français et russe), les termes équivalents fournis par les comités membres responsables sont donnés dans les langues suivantes : 90 93 2004 ISO/IEC ISO/IEC Guide 2:1996 Geneva
+Bibliography +World Trade Organization, The WTO Agreements Series Technical Barriers to Trade +WTO TBT Agreements + + + +
+
diff --git a/metanorma.release.yml b/metanorma.release.yml new file mode 100644 index 0000000..037b743 --- /dev/null +++ b/metanorma.release.yml @@ -0,0 +1,2 @@ +documents: + - source: sources/cc-10010.adoc diff --git a/metanorma.yml b/metanorma.yml index 78921be..ca191f3 100644 --- a/metanorma.yml +++ b/metanorma.yml @@ -1,7 +1,9 @@ ---- metanorma: deploy: - email: "ci@metanorma.org" + email: ci@metanorma.org + source: + files: + - sources/cc-10010.adoc relaton: collection: name: TC-PUBLISH diff --git a/relaton/cache/cc/cc_dir_10001_2018.notfound b/relaton/cache/cc/cc_dir_10001_2018.notfound new file mode 100644 index 0000000..b21f5d3 --- /dev/null +++ b/relaton/cache/cc/cc_dir_10001_2018.notfound @@ -0,0 +1 @@ +not_found 2020-06-16 \ No newline at end of file diff --git a/relaton/cache/cc/cc_dir_10002_2018.notfound b/relaton/cache/cc/cc_dir_10002_2018.notfound new file mode 100644 index 0000000..b21f5d3 --- /dev/null +++ b/relaton/cache/cc/cc_dir_10002_2018.notfound @@ -0,0 +1 @@ +not_found 2020-06-16 \ No newline at end of file diff --git a/relaton/cache/cc/version b/relaton/cache/cc/version new file mode 100644 index 0000000..6319412 --- /dev/null +++ b/relaton/cache/cc/version @@ -0,0 +1 @@ +04426f4ff489596ce7bc1d65293c7d8b \ No newline at end of file diff --git a/relaton/cache/iso/iso_1_all_parts.xml b/relaton/cache/iso/iso_1_all_parts.xml new file mode 100644 index 0000000..1d6b918 --- /dev/null +++ b/relaton/cache/iso/iso_1_all_parts.xml @@ -0,0 +1,146 @@ + + 2020-06-16 + Geometrical product specifications (GPS) + Standard reference temperature for the specification of geometrical and dimensional properties + Geometrical product specifications (GPS) – Standard reference temperature for the specification of geometrical and dimensional properties + Spécification géométrique des produits (GPS) + Température normale de référence pour la spécification des propriétés géométriques et dimensionnelles + Spécification géométrique des produits (GPS) – Température normale de référence pour la spécification des propriétés géométriques et dimensionnelles + https://www.iso.org/standard/67630.html + https://www.iso.org/obp/ui/#!iso:std:67630:en + https://www.iso.org/contents/data/standard/06/76/67630.detail.rss + ISO 1 (all parts) + 1 + + 2016 + + + + + International Organization for Standardization + ISO + www.iso.org + + + 3 + en + fr + + + 60 + 60 + + + 2016 + + + ISO + + + + + + ISO 1:2002 + + + + + 2020-06-16 + Geometrical product specifications (GPS) + Standard reference temperature for the specification of geometrical and dimensional properties + Geometrical product specifications (GPS) – Standard reference temperature for the specification of geometrical and dimensional properties + Spécification géométrique des produits (GPS) + Température normale de référence pour la spécification des propriétés géométriques et dimensionnelles + Spécification géométrique des produits (GPS) – Température normale de référence pour la spécification des propriétés géométriques et dimensionnelles + https://www.iso.org/standard/67630.html + https://www.iso.org/obp/ui/#!iso:std:67630:en + https://www.iso.org/contents/data/standard/06/76/67630.detail.rss + ISO 1:2016 + 1 + + 2016 + + + + + International Organization for Standardization + ISO + www.iso.org + + + 3 + en + fr + + ISO 1:2016 defines the concepts of a reference temperature and of the standard reference temperature, and specifies the standard reference temperature value for the specification of geometrical and dimensional properties of an object. Some examples of geometrical and dimensional properties include size, location, orientation (including angle), form and surface texture of a workpiece.ISO 1:2016 Standard is also applicable to the definition of the measurand used in verification or calibration. + ISO 1:2016 définit les concepts de température de référence et de température normale de référence, et spécifie la valeur de la température normale de référence pour la spécification des propriétés géométriques et dimensionnelles d'un objet. Certains exemples de propriétés géométriques et dimensionnelles incluent la taille, la position, l'orientation (y compris l'angle), la forme et l'état de surface d'une pièce.ISO 1:2016 s'applique aussi à la définition du mesurande utilisé en vérification ou en étalonnage. + + 60 + 60 + + + 2016 + + + ISO + + + + + + ISO 1:2002 + + + Geneva + + + + + IWA 1:2005 + + + + + ISO 1:2002 + + + + + IWA 1:2001 + + + + + ISO/TTA 1:1994 + + + + + ISO/DATA 1:1978 + + + + + ISO 1:1975 + + + + + ISO Guide 1:1972 + + + Geneva + + international-standard + + ISO/TC 213Dimensional and geometrical product specifications and verification + + + 17.040.01 + Linear and angular measurements in general + + + ISO 1 (all parts) + + + \ No newline at end of file diff --git a/relaton/cache/iso/iso_iec_directives_part_1,_consolidated_iso_supplement.redirect b/relaton/cache/iso/iso_iec_directives_part_1,_consolidated_iso_supplement.redirect new file mode 100644 index 0000000..303ba50 --- /dev/null +++ b/relaton/cache/iso/iso_iec_directives_part_1,_consolidated_iso_supplement.redirect @@ -0,0 +1 @@ +redirection ISO(ISO 1 (all parts)) \ No newline at end of file diff --git a/relaton/cache/iso/iso_iec_directives_part_1.redirect b/relaton/cache/iso/iso_iec_directives_part_1.redirect new file mode 100644 index 0000000..303ba50 --- /dev/null +++ b/relaton/cache/iso/iso_iec_directives_part_1.redirect @@ -0,0 +1 @@ +redirection ISO(ISO 1 (all parts)) \ No newline at end of file diff --git a/relaton/cache/iso/iso_iec_directives_part_2.redirect b/relaton/cache/iso/iso_iec_directives_part_2.redirect new file mode 100644 index 0000000..a237096 --- /dev/null +++ b/relaton/cache/iso/iso_iec_directives_part_2.redirect @@ -0,0 +1 @@ +redirection ISO(ISO/IEC Guide 2 (all parts)) \ No newline at end of file diff --git a/relaton/cache/iso/iso_iec_guide_2_2004.xml b/relaton/cache/iso/iso_iec_guide_2_2004.xml new file mode 100644 index 0000000..d4a06a6 --- /dev/null +++ b/relaton/cache/iso/iso_iec_guide_2_2004.xml @@ -0,0 +1,74 @@ + + 2020-06-16 + Standardization and related activities + General vocabulary + Standardization and related activities – General vocabulary + Normalisation et activités connexes + Vocabulaire général + Normalisation et activités connexes – Vocabulaire général + https://www.iso.org/standard/39976.html + https://www.iso.org/obp/ui/#!iso:std:39976:en + https://www.iso.org/contents/data/standard/03/99/39976.detail.rss + ISO/IEC Guide 2:2004 + 2 + + 2004 + + + + + International Organization for Standardization + ISO + www.iso.org + + + + + + International Electrotechnical Commission + IEC + www.iec.ch + + + 8 + en + fr + + ISO/IEC Guide 2:2004 provides general terms and definitions concerning standardization and related activities. It is intended to contribute fundamentally towards mutual understanding amongst the members of ISO and IEC and the various governmental and non-governmental agencies involved in standardization at international, regional and national levels. It is intended also to provide a suitable source for teaching and for reference, briefly covering basic theoretical and practical principles of standardization, certification and laboratory accreditation.It is not the aim of ISO/IEC Guide 2:2004 to duplicate definitions of terms adequately defined for general purposes in other authoritative international vocabularies.NOTE 1 From this point of view, particular attention is drawn to the International vocabulary of basic and general terms in metrology (VIM) jointly prepared by ISO, IEC, BIPM, IFCC, IUPAC, IUPAP and OIML, and published in 1993 (second edition).NOTE 2 In addition to the terms given in the official languages of ISO and IEC (English, French and Russian), equivalent terms provided by the relevant member bodies are given in the following languages: + Le Guide ISO/CEI 2 fournit des termes généraux et leurs définitions concernant la normalisation et les activités connexes. Il est prévu pour contribuer, de manière fondamentale, à la compréhension mutuelle entre les membres de l'ISO, de la CEI et des diverses institutions gouvernementales et non gouvernementales engagées dans la normalisation aux niveaux international, régional et national. Il est prévu également pour constituer un instrument de formation ou de référence couvrant brièvement les principes de base, théoriques et pratiques, de la normalisation, de la certification et de l'accréditation des laboratoires d'essais.L'objet du Guide ISO/CEI 2 n'est pas de redonner les définitions de termes déjà définis de façon satisfaisante dans leur sens général par d'autres vocabulaires internationaux faisant autorité.NOTE 1 Une attention particulière doit être portée, à cet égard, au Vocabulaire international des termes fondamentaux et généraux de métrologie (VIM) préparé conjointement par l'ISO, la CEI, le BIPM, la FICC, l'OIML, l'UICPA et l'UIPPA et qui a été publié en 1993 (deuxième édition).NOTE 2 En plus des termes donnés dans les langues officielles de l'ISO et de la CEI (anglais, français et russe), les termes équivalents fournis par les comités membres responsables sont donnés dans les langues suivantes : + + 90 + 93 + + + 2004 + + + ISO/IEC + + + + + + ISO/IEC Guide 2:1996 + + + Geneva + + guide + + ISO/TMBGTechnical Management Board - groups + + + 01.120 + Standardization. General rules + + + 01.040.01 + Generalities. Terminology. Standardization. Documentation (Vocabularies) + + + ISO/IEC Guide 2 + + + \ No newline at end of file diff --git a/relaton/cache/iso/iso_iec_guide_2_all_parts.xml b/relaton/cache/iso/iso_iec_guide_2_all_parts.xml new file mode 100644 index 0000000..f8f17f1 --- /dev/null +++ b/relaton/cache/iso/iso_iec_guide_2_all_parts.xml @@ -0,0 +1,161 @@ + + 2020-06-16 + Standardization and related activities + General vocabulary + Standardization and related activities – General vocabulary + Normalisation et activités connexes + Vocabulaire général + Normalisation et activités connexes – Vocabulaire général + https://www.iso.org/standard/39976.html + https://www.iso.org/obp/ui/#!iso:std:39976:en + https://www.iso.org/contents/data/standard/03/99/39976.detail.rss + ISO/IEC Guide 2 (all parts) + 2 + + 2004 + + + + + International Organization for Standardization + ISO + www.iso.org + + + + + + International Electrotechnical Commission + IEC + www.iec.ch + + + 8 + en + fr + + + 90 + 93 + + + 2004 + + + ISO/IEC + + + + + + ISO/IEC Guide 2:1996 + + + + + 2020-06-16 + Standardization and related activities + General vocabulary + Standardization and related activities – General vocabulary + Normalisation et activités connexes + Vocabulaire général + Normalisation et activités connexes – Vocabulaire général + https://www.iso.org/standard/39976.html + https://www.iso.org/obp/ui/#!iso:std:39976:en + https://www.iso.org/contents/data/standard/03/99/39976.detail.rss + ISO/IEC Guide 2:2004 + 2 + + 2004 + + + + + International Organization for Standardization + ISO + www.iso.org + + + + + + International Electrotechnical Commission + IEC + www.iec.ch + + + 8 + en + fr + + ISO/IEC Guide 2:2004 provides general terms and definitions concerning standardization and related activities. It is intended to contribute fundamentally towards mutual understanding amongst the members of ISO and IEC and the various governmental and non-governmental agencies involved in standardization at international, regional and national levels. It is intended also to provide a suitable source for teaching and for reference, briefly covering basic theoretical and practical principles of standardization, certification and laboratory accreditation.It is not the aim of ISO/IEC Guide 2:2004 to duplicate definitions of terms adequately defined for general purposes in other authoritative international vocabularies.NOTE 1 From this point of view, particular attention is drawn to the International vocabulary of basic and general terms in metrology (VIM) jointly prepared by ISO, IEC, BIPM, IFCC, IUPAC, IUPAP and OIML, and published in 1993 (second edition).NOTE 2 In addition to the terms given in the official languages of ISO and IEC (English, French and Russian), equivalent terms provided by the relevant member bodies are given in the following languages: + Le Guide ISO/CEI 2 fournit des termes généraux et leurs définitions concernant la normalisation et les activités connexes. Il est prévu pour contribuer, de manière fondamentale, à la compréhension mutuelle entre les membres de l'ISO, de la CEI et des diverses institutions gouvernementales et non gouvernementales engagées dans la normalisation aux niveaux international, régional et national. Il est prévu également pour constituer un instrument de formation ou de référence couvrant brièvement les principes de base, théoriques et pratiques, de la normalisation, de la certification et de l'accréditation des laboratoires d'essais.L'objet du Guide ISO/CEI 2 n'est pas de redonner les définitions de termes déjà définis de façon satisfaisante dans leur sens général par d'autres vocabulaires internationaux faisant autorité.NOTE 1 Une attention particulière doit être portée, à cet égard, au Vocabulaire international des termes fondamentaux et généraux de métrologie (VIM) préparé conjointement par l'ISO, la CEI, le BIPM, la FICC, l'OIML, l'UICPA et l'UIPPA et qui a été publié en 1993 (deuxième édition).NOTE 2 En plus des termes donnés dans les langues officielles de l'ISO et de la CEI (anglais, français et russe), les termes équivalents fournis par les comités membres responsables sont donnés dans les langues suivantes : + + 90 + 93 + + + 2004 + + + ISO/IEC + + + + + + ISO/IEC Guide 2:1996 + + + Geneva + + + + + ISO/TTA 2:1997 + + + + + ISO 2:1973 + + + + + IWA 2:2007 + + + + + IWA 2:2003 + + + + + ISO/IEC Guide 2:1996 + + + + + ISO/IEC Guide 2:1991 + + + Geneva + + guide + + ISO/TMBGTechnical Management Board - groups + + + 01.120 + Standardization. General rules + + + 01.040.01 + Generalities. Terminology. Standardization. Documentation (Vocabularies) + + + ISO/IEC Guide 2 (all parts) + + + \ No newline at end of file diff --git a/relaton/cache/iso/version b/relaton/cache/iso/version new file mode 100644 index 0000000..efef980 --- /dev/null +++ b/relaton/cache/iso/version @@ -0,0 +1 @@ +d2ce9db481f8308dc568639910be49aa \ No newline at end of file diff --git a/sources/cc-10010.adoc b/sources/cc-10010.adoc index a97d30b..5a49a19 100644 --- a/sources/cc-10010.adoc +++ b/sources/cc-10010.adoc @@ -1,5 +1,5 @@ -= ISO/CalConnect Partner Standards Development Organization (PSDO) Cooperation Agreement -:title: ISO/CalConnect Partner Standards Development Organization (PSDO) Cooperation Agreement += CalConnect Partner Standards Cooperation Agreement +:title: CalConnect Partner Standards Cooperation Agreement :docnumber: 10010 :copyright-year: 2019 :language: en @@ -11,7 +11,7 @@ :published-date: 2019-01-18 :language: en :technical-committee: PUBLISH -:collaboration-party: ISO +:collaboration-party: Collaboration Party :draft: :toc: :stem: diff --git a/sources/cc-10010.err b/sources/cc-10010.err new file mode 100644 index 0000000..dd99233 --- /dev/null +++ b/sources/cc-10010.err @@ -0,0 +1,29 @@ +sources/cc-10010.err errors + + +== Style + +(XML Line 000068): Hanging paragraph in clause +(XML Line 000241): Symbols and Abbreviated Terms can only contain a definition list +(XML Line 000258): Hanging paragraph in clause +(XML Line 000322): Hanging paragraph in clause +(XML Line 000362): Hanging paragraph in clause +(XML Line 000404): Hanging paragraph in clause +(XML Line 000423): Hanging paragraph in clause +(XML Line 000459): Hanging paragraph in clause +(XML Line 000545): Hanging paragraph in clause +(XML Line 000566): Hanging paragraph in clause +(XML Line 000582): Hanging paragraph in clause +(XML Line 000623): Hanging paragraph in clause +(XML Line 000686): Hanging paragraph in clause +(XML Line 000726): Hanging paragraph in clause +(XML Line 000742): Hanging paragraph in clause +(XML Line 000779): Hanging paragraph in clause +(XML Line 000813): Hanging paragraph in clause +(XML Line 000844): Hanging paragraph in clause +(XML Line 000878): Hanging paragraph in clause + + +== Syntax + +(XML Line 000177:41): element "eref" missing required attributes "citeas" and "type" diff --git a/sources/sections/00-intro.adoc b/sources/sections/00-intro.adoc index 46da7df..2031e68 100644 --- a/sources/sections/00-intro.adoc +++ b/sources/sections/00-intro.adoc @@ -12,12 +12,14 @@ This document formalizes the process of collaboration of enable the collaborative development of standards. The resulting standards are to be jointly published by -{collaboration-party} and CalConnect as "`ISO/CalConnect Standards`", +{collaboration-party} and CalConnect as +"`{collaboration-party}/CalConnect Standards`", according to processes described in this document. === Background +//// One of the objectives of ISO is to facilitate the international exchange of goods and services through the development of International Standards. @@ -30,13 +32,20 @@ use of resources available for standardization activities. CalConnect aims to facilitate interoperability of collaborative technologies with open standards, in particular on calendar, scheduling, and contacts; its standards are globally recognized and widely applied. +//// +CalConnect and {collaboration-party} support a policy of inclusiveness and +encourages cooperation with other standardizing bodies, +in order to ensure effective and efficient use of resources +available for standardization activities. === Intention -ISO and CalConnect agree to the principles of cooperation described in -this document, in all fields subject to approval by the ISO TMB and the -CalConnect TC PUBLISH and TCC. +{collaboration-party} and CalConnect agree to the principles of cooperation described in +this document, in all fields subject to approval by the governing bodies of +{collaboration-party} and CalConnect TC PUBLISH and TCC + +// ISO TMB === Process cooperation diff --git a/submissions/20180824/20180824-csd-iso-collaboration.docx b/submissions/20180824/20180824-csd-iso-collaboration.docx new file mode 100644 index 0000000..d13b9a2 Binary files /dev/null and b/submissions/20180824/20180824-csd-iso-collaboration.docx differ diff --git a/submissions/20180824/20180824-csd-iso-collaboration.html.zip b/submissions/20180824/20180824-csd-iso-collaboration.html.zip new file mode 100644 index 0000000..19b36b7 Binary files /dev/null and b/submissions/20180824/20180824-csd-iso-collaboration.html.zip differ diff --git a/submissions/20180824/20180824-csd-iso-collaboration.pdf b/submissions/20180824/20180824-csd-iso-collaboration.pdf new file mode 100644 index 0000000..b47671c Binary files /dev/null and b/submissions/20180824/20180824-csd-iso-collaboration.pdf differ diff --git a/submissions/20180912-iso-calconnect-psdo.zip b/submissions/20180912-iso-calconnect-psdo.zip new file mode 100644 index 0000000..8198bc3 Binary files /dev/null and b/submissions/20180912-iso-calconnect-psdo.zip differ