diff --git a/LICENSE b/LICENSE new file mode 100644 index 0000000..da6ab6c --- /dev/null +++ b/LICENSE @@ -0,0 +1,396 @@ +Attribution 4.0 International + +======================================================================= + +Creative Commons Corporation ("Creative Commons") is not a law firm and +does not provide legal services or legal advice. Distribution of +Creative Commons public licenses does not create a lawyer-client or +other relationship. Creative Commons makes its licenses and related +information available on an "as-is" basis. Creative Commons gives no +warranties regarding its licenses, any material licensed under their +terms and conditions, or any related information. Creative Commons +disclaims all liability for damages resulting from their use to the +fullest extent possible. + +Using Creative Commons Public Licenses + +Creative Commons public licenses provide a standard set of terms and +conditions that creators and other rights holders may use to share +original works of authorship and other material subject to copyright +and certain other rights specified in the public license below. The +following considerations are for informational purposes only, are not +exhaustive, and do not form part of our licenses. + + Considerations for licensors: Our public licenses are + intended for use by those authorized to give the public + permission to use material in ways otherwise restricted by + copyright and certain other rights. Our licenses are + irrevocable. Licensors should read and understand the terms + and conditions of the license they choose before applying it. + Licensors should also secure all rights necessary before + applying our licenses so that the public can reuse the + material as expected. Licensors should clearly mark any + material not subject to the license. This includes other CC- + licensed material, or material used under an exception or + limitation to copyright. More considerations for licensors: + wiki.creativecommons.org/Considerations_for_licensors + + Considerations for the public: By using one of our public + licenses, a licensor grants the public permission to use the + licensed material under specified terms and conditions. If + the licensor's permission is not necessary for any reason--for + example, because of any applicable exception or limitation to + copyright--then that use is not regulated by the license. Our + licenses grant only permissions under copyright and certain + other rights that a licensor has authority to grant. Use of + the licensed material may still be restricted for other + reasons, including because others have copyright or other + rights in the material. A licensor may make special requests, + such as asking that all changes be marked or described. + Although not required by our licenses, you are encouraged to + respect those requests where reasonable. More considerations + for the public: + wiki.creativecommons.org/Considerations_for_licensees + +======================================================================= + +Creative Commons Attribution 4.0 International Public License + +By exercising the Licensed Rights (defined below), You accept and agree +to be bound by the terms and conditions of this Creative Commons +Attribution 4.0 International Public License ("Public License"). To the +extent this Public License may be interpreted as a contract, You are +granted the Licensed Rights in consideration of Your acceptance of +these terms and conditions, and the Licensor grants You such rights in +consideration of benefits the Licensor receives from making the +Licensed Material available under these terms and conditions. + + +Section 1 -- Definitions. + + a. Adapted Material means material subject to Copyright and Similar + Rights that is derived from or based upon the Licensed Material + and in which the Licensed Material is translated, altered, + arranged, transformed, or otherwise modified in a manner requiring + permission under the Copyright and Similar Rights held by the + Licensor. For purposes of this Public License, where the Licensed + Material is a musical work, performance, or sound recording, + Adapted Material is always produced where the Licensed Material is + synched in timed relation with a moving image. + + b. Adapter's License means the license You apply to Your Copyright + and Similar Rights in Your contributions to Adapted Material in + accordance with the terms and conditions of this Public License. + + c. Copyright and Similar Rights means copyright and/or similar rights + closely related to copyright including, without limitation, + performance, broadcast, sound recording, and Sui Generis Database + Rights, without regard to how the rights are labeled or + categorized. For purposes of this Public License, the rights + specified in Section 2(b)(1)-(2) are not Copyright and Similar + Rights. + + d. Effective Technological Measures means those measures that, in the + absence of proper authority, may not be circumvented under laws + fulfilling obligations under Article 11 of the WIPO Copyright + Treaty adopted on December 20, 1996, and/or similar international + agreements. + + e. Exceptions and Limitations means fair use, fair dealing, and/or + any other exception or limitation to Copyright and Similar Rights + that applies to Your use of the Licensed Material. + + f. Licensed Material means the artistic or literary work, database, + or other material to which the Licensor applied this Public + License. + + g. Licensed Rights means the rights granted to You subject to the + terms and conditions of this Public License, which are limited to + all Copyright and Similar Rights that apply to Your use of the + Licensed Material and that the Licensor has authority to license. + + h. Licensor means the individual(s) or entity(ies) granting rights + under this Public License. + + i. Share means to provide material to the public by any means or + process that requires permission under the Licensed Rights, such + as reproduction, public display, public performance, distribution, + dissemination, communication, or importation, and to make material + available to the public including in ways that members of the + public may access the material from a place and at a time + individually chosen by them. + + j. Sui Generis Database Rights means rights other than copyright + resulting from Directive 96/9/EC of the European Parliament and of + the Council of 11 March 1996 on the legal protection of databases, + as amended and/or succeeded, as well as other essentially + equivalent rights anywhere in the world. + + k. You means the individual or entity exercising the Licensed Rights + under this Public License. Your has a corresponding meaning. + + +Section 2 -- Scope. + + a. License grant. + + 1. Subject to the terms and conditions of this Public License, + the Licensor hereby grants You a worldwide, royalty-free, + non-sublicensable, non-exclusive, irrevocable license to + exercise the Licensed Rights in the Licensed Material to: + + a. reproduce and Share the Licensed Material, in whole or + in part; and + + b. produce, reproduce, and Share Adapted Material. + + 2. Exceptions and Limitations. For the avoidance of doubt, where + Exceptions and Limitations apply to Your use, this Public + License does not apply, and You do not need to comply with + its terms and conditions. + + 3. Term. The term of this Public License is specified in Section + 6(a). + + 4. Media and formats; technical modifications allowed. The + Licensor authorizes You to exercise the Licensed Rights in + all media and formats whether now known or hereafter created, + and to make technical modifications necessary to do so. The + Licensor waives and/or agrees not to assert any right or + authority to forbid You from making technical modifications + necessary to exercise the Licensed Rights, including + technical modifications necessary to circumvent Effective + Technological Measures. For purposes of this Public License, + simply making modifications authorized by this Section 2(a) + (4) never produces Adapted Material. + + 5. Downstream recipients. + + a. Offer from the Licensor -- Licensed Material. Every + recipient of the Licensed Material automatically + receives an offer from the Licensor to exercise the + Licensed Rights under the terms and conditions of this + Public License. + + b. No downstream restrictions. You may not offer or impose + any additional or different terms or conditions on, or + apply any Effective Technological Measures to, the + Licensed Material if doing so restricts exercise of the + Licensed Rights by any recipient of the Licensed + Material. + + 6. No endorsement. Nothing in this Public License constitutes or + may be construed as permission to assert or imply that You + are, or that Your use of the Licensed Material is, connected + with, or sponsored, endorsed, or granted official status by, + the Licensor or others designated to receive attribution as + provided in Section 3(a)(1)(A)(i). + + b. Other rights. + + 1. Moral rights, such as the right of integrity, are not + licensed under this Public License, nor are publicity, + privacy, and/or other similar personality rights; however, to + the extent possible, the Licensor waives and/or agrees not to + assert any such rights held by the Licensor to the limited + extent necessary to allow You to exercise the Licensed + Rights, but not otherwise. + + 2. Patent and trademark rights are not licensed under this + Public License. + + 3. To the extent possible, the Licensor waives any right to + collect royalties from You for the exercise of the Licensed + Rights, whether directly or through a collecting society + under any voluntary or waivable statutory or compulsory + licensing scheme. In all other cases the Licensor expressly + reserves any right to collect such royalties. + + +Section 3 -- License Conditions. + +Your exercise of the Licensed Rights is expressly made subject to the +following conditions. + + a. Attribution. + + 1. If You Share the Licensed Material (including in modified + form), You must: + + a. retain the following if it is supplied by the Licensor + with the Licensed Material: + + i. identification of the creator(s) of the Licensed + Material and any others designated to receive + attribution, in any reasonable manner requested by + the Licensor (including by pseudonym if + designated); + + ii. a copyright notice; + + iii. a notice that refers to this Public License; + + iv. a notice that refers to the disclaimer of + warranties; + + v. a URI or hyperlink to the Licensed Material to the + extent reasonably practicable; + + b. indicate if You modified the Licensed Material and + retain an indication of any previous modifications; and + + c. indicate the Licensed Material is licensed under this + Public License, and include the text of, or the URI or + hyperlink to, this Public License. + + 2. You may satisfy the conditions in Section 3(a)(1) in any + reasonable manner based on the medium, means, and context in + which You Share the Licensed Material. For example, it may be + reasonable to satisfy the conditions by providing a URI or + hyperlink to a resource that includes the required + information. + + 3. If requested by the Licensor, You must remove any of the + information required by Section 3(a)(1)(A) to the extent + reasonably practicable. + + 4. If You Share Adapted Material You produce, the Adapter's + License You apply must not prevent recipients of the Adapted + Material from complying with this Public License. + + +Section 4 -- Sui Generis Database Rights. + +Where the Licensed Rights include Sui Generis Database Rights that +apply to Your use of the Licensed Material: + + a. for the avoidance of doubt, Section 2(a)(1) grants You the right + to extract, reuse, reproduce, and Share all or a substantial + portion of the contents of the database; + + b. if You include all or a substantial portion of the database + contents in a database in which You have Sui Generis Database + Rights, then the database in which You have Sui Generis Database + Rights (but not its individual contents) is Adapted Material; and + + c. You must comply with the conditions in Section 3(a) if You Share + all or a substantial portion of the contents of the database. + +For the avoidance of doubt, this Section 4 supplements and does not +replace Your obligations under this Public License where the Licensed +Rights include other Copyright and Similar Rights. + + +Section 5 -- Disclaimer of Warranties and Limitation of Liability. + + a. UNLESS OTHERWISE SEPARATELY UNDERTAKEN BY THE LICENSOR, TO THE + EXTENT POSSIBLE, THE LICENSOR OFFERS THE LICENSED MATERIAL AS-IS + AND AS-AVAILABLE, AND MAKES NO REPRESENTATIONS OR WARRANTIES OF + ANY KIND CONCERNING THE LICENSED MATERIAL, WHETHER EXPRESS, + IMPLIED, STATUTORY, OR OTHER. THIS INCLUDES, WITHOUT LIMITATION, + WARRANTIES OF TITLE, MERCHANTABILITY, FITNESS FOR A PARTICULAR + PURPOSE, NON-INFRINGEMENT, ABSENCE OF LATENT OR OTHER DEFECTS, + ACCURACY, OR THE PRESENCE OR ABSENCE OF ERRORS, WHETHER OR NOT + KNOWN OR DISCOVERABLE. WHERE DISCLAIMERS OF WARRANTIES ARE NOT + ALLOWED IN FULL OR IN PART, THIS DISCLAIMER MAY NOT APPLY TO YOU. + + b. TO THE EXTENT POSSIBLE, IN NO EVENT WILL THE LICENSOR BE LIABLE + TO YOU ON ANY LEGAL THEORY (INCLUDING, WITHOUT LIMITATION, + NEGLIGENCE) OR OTHERWISE FOR ANY DIRECT, SPECIAL, INDIRECT, + INCIDENTAL, CONSEQUENTIAL, PUNITIVE, EXEMPLARY, OR OTHER LOSSES, + COSTS, EXPENSES, OR DAMAGES ARISING OUT OF THIS PUBLIC LICENSE OR + USE OF THE LICENSED MATERIAL, EVEN IF THE LICENSOR HAS BEEN + ADVISED OF THE POSSIBILITY OF SUCH LOSSES, COSTS, EXPENSES, OR + DAMAGES. WHERE A LIMITATION OF LIABILITY IS NOT ALLOWED IN FULL OR + IN PART, THIS LIMITATION MAY NOT APPLY TO YOU. + + c. The disclaimer of warranties and limitation of liability provided + above shall be interpreted in a manner that, to the extent + possible, most closely approximates an absolute disclaimer and + waiver of all liability. + + +Section 6 -- Term and Termination. + + a. This Public License applies for the term of the Copyright and + Similar Rights licensed here. However, if You fail to comply with + this Public License, then Your rights under this Public License + terminate automatically. + + b. Where Your right to use the Licensed Material has terminated under + Section 6(a), it reinstates: + + 1. automatically as of the date the violation is cured, provided + it is cured within 30 days of Your discovery of the + violation; or + + 2. upon express reinstatement by the Licensor. + + For the avoidance of doubt, this Section 6(b) does not affect any + right the Licensor may have to seek remedies for Your violations + of this Public License. + + c. For the avoidance of doubt, the Licensor may also offer the + Licensed Material under separate terms or conditions or stop + distributing the Licensed Material at any time; however, doing so + will not terminate this Public License. + + d. Sections 1, 5, 6, 7, and 8 survive termination of this Public + License. + + +Section 7 -- Other Terms and Conditions. + + a. The Licensor shall not be bound by any additional or different + terms or conditions communicated by You unless expressly agreed. + + b. Any arrangements, understandings, or agreements regarding the + Licensed Material not stated herein are separate from and + independent of the terms and conditions of this Public License. + + +Section 8 -- Interpretation. + + a. For the avoidance of doubt, this Public License does not, and + shall not be interpreted to, reduce, limit, restrict, or impose + conditions on any use of the Licensed Material that could lawfully + be made without permission under this Public License. + + b. To the extent possible, if any provision of this Public License is + deemed unenforceable, it shall be automatically reformed to the + minimum extent necessary to make it enforceable. If the provision + cannot be reformed, it shall be severed from this Public License + without affecting the enforceability of the remaining terms and + conditions. + + c. No term or condition of this Public License will be waived and no + failure to comply consented to unless expressly agreed to by the + Licensor. + + d. Nothing in this Public License constitutes or may be interpreted + as a limitation upon, or waiver of, any privileges and immunities + that apply to the Licensor or You, including from the legal + processes of any jurisdiction or authority. + + +======================================================================= + +Creative Commons is not a party to its public +licenses. Notwithstanding, Creative Commons may elect to apply one of +its public licenses to material it publishes and in those instances +will be considered the “Licensor.” The text of the Creative Commons +public licenses is dedicated to the public domain under the CC0 Public +Domain Dedication. Except for the limited purpose of indicating that +material is shared under a Creative Commons public license or as +otherwise permitted by the Creative Commons policies published at +creativecommons.org/policies, Creative Commons does not authorize the +use of the trademark "Creative Commons" or any other trademark or logo +of Creative Commons without its prior written consent including, +without limitation, in connection with any unauthorized modifications +to any of its public licenses or any other arrangements, +understandings, or agreements concerning use of licensed material. For +the avoidance of doubt, this paragraph does not form part of the +public licenses. + +Creative Commons may be contacted at creativecommons.org. + diff --git a/README.adoc b/README.adoc index e7d6eb0..6975982 100644 --- a/README.adoc +++ b/README.adoc @@ -8,8 +8,8 @@ This document is available in its rendered forms here: == Introduction -This repository contains official specifications maintained by the EXPRESS -Language Foundation (ELF). The EXPRESS Language Foundation facilitates the +This repository contains official specifications and directives maintained by the +EXPRESS Language Foundation (ELF). The EXPRESS Language Foundation facilitates the education, standardization, research, promotion, definition, and usage of information modelling and programming languages, with a focus on the EXPRESS language family. @@ -21,13 +21,22 @@ The specifications include: 5003:: *EXPRESS documentation migration* -- Specification for migrating EXPRESS documentation to the new format 5004:: *EXPRESS schema manifest* -- Specification for creating a manifest of EXPRESS schemas 5005:: *EXPRESS changes* -- Specification for documenting changes to the EXPRESS language and its specifications +5006:: *EXPRESS mapping language* -- Specification for expressing reference paths amongst a set of EXPRESS schemas -These specifications are written in Metanorma to generate standardized +The directives include: + +101:: *Standardization and publication* -- Directive on the ELF standardization and publication processes +102:: *Standard document requirements* -- Directive on requirements for ELF standard documents +103:: *Patent policy* -- Directive on the ELF patent policy +104:: *Guidelines for the implementation of the patent policy* -- Directive providing guidelines for the implementation of the ELF patent policy +105:: *Intellectual property rights policy* -- Directive on the ELF intellectual property rights policy + +The specifications and directives are written in Metanorma to generate standardized documentation in multiple formats. == Structure -`sources/`:: source files for EXPRESS specifications in Metanorma format. +`sources/`:: source files for EXPRESS specifications and ELF directives in Metanorma format. `sources/annotated-express/`::: Annotated EXPRESS specification @@ -44,6 +53,24 @@ EXPRESS schema manifest specification `sources/express-changes/`::: EXPRESS changes specification +`sources/express-mapping/`::: +EXPRESS mapping language specification + +`sources/directive-standardization/`::: +ELF Directive 101: Standardization and publication + +`sources/directive-document-requirements/`::: +ELF Directive 102: Standard document requirements + +`sources/directive-patent-policy/`::: +ELF Directive 103: Patent policy + +`sources/directive-ipr-guidelines/`::: +ELF Directive 104: Guidelines for the implementation of the patent policy + +`sources/directive-ipr-policy/`::: +ELF Directive 105: Intellectual property rights policy + == Building documentation This repository uses Metanorma to build standardized documentation. @@ -64,7 +91,7 @@ metanorma site generate === Building with Docker -If you prefer using Docker, run: +If you prefer to use Docker, run: [source,sh] ---- @@ -83,3 +110,7 @@ The build process generates documentation in multiple formats: == License Copyright EXPRESS Language Foundation. + +ELF documents are made available under the Creative Commons Attribution +4.0 International (CC BY 4.0) license. The full license text is available +in the LICENSE file. diff --git a/metanorma.yml b/metanorma.yml index c368938..c693a86 100644 --- a/metanorma.yml +++ b/metanorma.yml @@ -8,6 +8,11 @@ metanorma: - sources/express-schema-manifest/document.adoc - sources/express-changes/document.adoc - sources/express-mapping/document.adoc + - sources/directive-standardization/document.adoc + - sources/directive-document-requirements/document.adoc + - sources/directive-patent-policy/document.adoc + - sources/directive-ipr-guidelines/document.adoc + - sources/directive-ipr-policy/document.adoc collection: organization: "EXPRESS Language Foundation" diff --git a/sources/directive-document-requirements/document.adoc b/sources/directive-document-requirements/document.adoc new file mode 100644 index 0000000..cfa33d0 --- /dev/null +++ b/sources/directive-document-requirements/document.adoc @@ -0,0 +1,26 @@ += ELF Directive: Standard document requirements +:title-main-en: ELF Directive: Standard document requirements +:docnumber: 102 +:edition: 1 +:copyright-year: 2026 +:revdate: 2026-08-30 +:language: en +:doctype: standard +:technical-committee: TCB +:imagesdir: images +:mn-document-class: elf +:mn-output-extensions: xml,html,doc,pdf,rxl +:docidentifier: ELF 102:2026 +:data-uri-image: +:local-cache-only: + +include::sections/00-foreword.adoc[] +include::sections/00-intro.adoc[] + +include::sections/01-scope.adoc[] +include::sections/02-normrefs.adoc[] +include::sections/03-terms.adoc[] +include::sections/04-requirements.adoc[] +include::sections/05-structure.adoc[] + +include::sections/99-bibliography.adoc[] diff --git a/sources/directive-document-requirements/sections/00-foreword.adoc b/sources/directive-document-requirements/sections/00-foreword.adoc new file mode 100644 index 0000000..b3dc799 --- /dev/null +++ b/sources/directive-document-requirements/sections/00-foreword.adoc @@ -0,0 +1,27 @@ +.Foreword +The EXPRESS Language Foundation ("`ELF`") is a registered public charity in the +US that facilitates the education, standardization, research, promotion, +definition, and usage of information modelling and programming languages, with a +focus on the EXPRESS language family. + +ELF works with international partners and experts across the globe, reflecting +the international nature of its mission. More information about ELF is available +on the official website (https://www.expresslang.org). + +The procedures used to develop this document and those intended for its further +maintenance are described in the ELF Directives. + +In particular the different approval criteria needed for the different types of +ELF documents should be noted. This document was drafted in accordance with the +editorial rules of the ELF Directives. + +Attention is drawn to the possibility that some of the elements of this +document may be the subject of patent rights. ELF shall not be held responsible +for identifying any or all such patent rights. Details of any patent rights +identified during the development of the document will be provided in the +Introduction. + +Any trade name used in this document is information given for the convenience of +users and does not constitute an endorsement. + +This document was prepared by the Technical Coordination Board (TCB). diff --git a/sources/directive-document-requirements/sections/00-intro.adoc b/sources/directive-document-requirements/sections/00-intro.adoc new file mode 100644 index 0000000..52e7816 --- /dev/null +++ b/sources/directive-document-requirements/sections/00-intro.adoc @@ -0,0 +1,16 @@ +== Introduction + +ELF is committed to expanding the realm of standards for information +modelling and programming languages, with a focus on the EXPRESS +language family and interoperability across the globe and communities +of practice. + +To facilitate its mission, the ELF Board of Directors has decided +to align standardization and publication processes with international +best practices, such as the ISO standardization process +(<>, <>, <>) +and the <>. + +This document aims to achieve the said intention. + +The document describes requirements for ELF standard documents. diff --git a/sources/directive-document-requirements/sections/01-scope.adoc b/sources/directive-document-requirements/sections/01-scope.adoc new file mode 100644 index 0000000..dceba16 --- /dev/null +++ b/sources/directive-document-requirements/sections/01-scope.adoc @@ -0,0 +1,27 @@ +== Scope + +This document provides requirements on document structure of the following types of ELF publication: + +* Directive + +* Standard + +* Guide + +* Specification + +* Amendment + +* Technical corrigendum + +* Report + +These publication types are described in <>. + +This document does not apply to the following types of documents +produced by ELF, although processes described in this document +can be optionally used as guidance: + +* policy statements; +* internal administrative documents; and +* how-to guides. diff --git a/sources/directive-document-requirements/sections/02-normrefs.adoc b/sources/directive-document-requirements/sections/02-normrefs.adoc new file mode 100644 index 0000000..d5c7b49 --- /dev/null +++ b/sources/directive-document-requirements/sections/02-normrefs.adoc @@ -0,0 +1,4 @@ +[bibliography] +== Normative References + +* [[[DIR101,ELF 101:2026]]], _ELF Directive: Standardization and publication_ diff --git a/sources/directive-document-requirements/sections/03-terms.adoc b/sources/directive-document-requirements/sections/03-terms.adoc new file mode 100644 index 0000000..5bcbb7e --- /dev/null +++ b/sources/directive-document-requirements/sections/03-terms.adoc @@ -0,0 +1,111 @@ +[source="ISODIR1,ISODIR1C,ISODIR2,DIR101"] + +[[terms]] +== Terms, definitions and abbreviations + +=== Terms and definitions + +[[term-std-work-item]] +==== standardization work item + +publishable work item that creates output that relates +to standardization + + +[[term-std-project]] +==== standardization project + +organized process with one or more +_standardization work items_ (<>) that +contributes towards a defined scope of work + + +[[term-project-owner]] +==== project owner + +entity with authority in charge of a _standardization project_ +(<>) + +[[term-document]] +==== document + +written output of a _standardization work item_ (<>) + +[[term-cc-deliverable]] +==== ELF deliverable + +_document_ (<>) that could be an ELF Standard, +Guide, Specification, Report + +[[term-iso-deliverable]] +==== ISO TC deliverable + +_document_ (<>) of an ISO TC as described in <> + +NOTE: According to <>, ISO TC deliverables include the following types: International Standards, Technical Specifications, Publicly Available Specifications and Technical Reports. + +[[term-cc-tc]] +==== ELF technical committee +alt:[ELF TC] + +internal committee of ELF tasked with a scope of work it +is responsible for + +[[term-document-stage]] +==== document stage + +stage of _document_ (<>) as specified in the ELF stages (as defined in <>) + +[[term-std-project-output]] +==== standardization project output + +output of a _standardization project_ (<>) + +NOTE: In this document, this explicitly means any documents and IP rights +produced by the standardization project. + +[[term-sdo]] +==== standardization body +alt:[standards-developing organization] +alt:[SDO] + +entity that publishes _standardization work items_ (<>) + + +[[term-std-proposal]] +==== proposal for standardization + +proposal for a new _work item_ (<>) for standardization + +[[term-co-develop]] +==== co-develop +alt:[collaborative development] + +act of developing a _standardization work item_ (<>) by multiple parties from the proposal +_document stage_ (<>) + +[[term-co-publish]] +==== co-publish +alt:[collaborative publishing] + +act of publishing _documents_ (<>) of identical content +by multiple parties + +==== joint work item + +_standardization work item_ (<>) _co-developed_ (<>) by both parties + + +==== joint publication + +publication that is _co-published_ (<>) by ELF with +an external _standardization body_ (<>) + +NOTE: Both parties may jointly hold copyright of the joint publication. + + +=== Abbreviations + +IPR:: Intellectual Property Rights + +TCB:: Technical Coordination Board diff --git a/sources/directive-document-requirements/sections/04-requirements.adoc b/sources/directive-document-requirements/sections/04-requirements.adoc new file mode 100644 index 0000000..b3b6516 --- /dev/null +++ b/sources/directive-document-requirements/sections/04-requirements.adoc @@ -0,0 +1,113 @@ + +[[numbering]] +== Project/document identifier + +=== General + +ELF implements a numbering system for projects/documents. + +=== Project index + +A project/document index shall be maintained on the ELF +website with documents listed by number, name, and type. + +[[project-code]] +=== Project code + +. The project code shall be of the form `[n]`, where `[n]` is any +selected positive integer of five (5) or less digits. + +. The numbering system applies across all project types. +Different project types shall not share an identical project code. + +. The project code shall be assigned on proposal acceptance +of the project. + +. Co-published documents shall attempt to use an identical project +code in both ELF and at the collaborative publisher to prevent +potential ambiguity, if possible. + + +=== Document identifier + +==== Representation + +The document identifier takes the form of `[type][stage] [code][:][y]`, where: + +* `[type]` is the document identifier prefix; +* `[stage]` is the document stage; +* `[code]` is the project code of the project that created the document; and +* `[y]` is the 4-digit edition year. + + +==== Edition year + +The edition year is the calendar year in which the document is published. +On updates, a document will retain the same project code but may be +assigned a different edition year in which the update is published. + + +==== Co-publishing + +Co-published documents shall incorporate codes from all collaborative +publishing parties in the document identifier, joined together via a +"`solidus`" sign ("```/```"). + +[example] +ELF deliverables co-published with ISO are referenced as "`ELF/ISO`", +with IETF as "`ELF/IETF`". + + +[[document-type]] +==== Document types + +Document types shall be represented in the "`type`" as follows: + +. Standard, "`ELF`" + +. Directive, "`ELF/DIR`" + +. Guide, "`ELF/Guide`" + +. Specification, "`ELF/S`" + +. Report, "`ELF/R`" + +. Amendment, "`ELF/Amd`" + +. Technical corrigendum, "`ELF/Cor`" + +. Administrative, "`ELF/A`" + +[example] +"`ELF/Guide/DS 38002:2018`" is an ELF Guide at DS stage with +project number 38002, published in 2018. + + +[[document-stage]] +==== Document stages + +Document stages shall be represented in the "`stage`" as follows: + +. Published, "``` ```" (blank) + +. Final draft standard, "```/FDS```" + +. Draft standard, "```/DS```" + +. Technical committee draft, "```/CD```" + +. Project group draft / Working draft, "```/WD```" + + +[example] +"`ELF/FDS 10668:2018`" is an ELF standard document at FDS stage +with project number 10668, published in 2018. + +[example] +"`ELF/Guide/DS 20080:2018`" is an ELF guide at DS stage with +project number 20080, published in 2018. + + +NOTE: Existing documents can be retrofitted to the scheme as practical. + diff --git a/sources/directive-document-requirements/sections/05-structure.adoc b/sources/directive-document-requirements/sections/05-structure.adoc new file mode 100644 index 0000000..d90c922 --- /dev/null +++ b/sources/directive-document-requirements/sections/05-structure.adoc @@ -0,0 +1,278 @@ + +[[document-structure]] +== Document structure + +=== General + +This section describes the document structure and element +requirements of a ELF standard document. + +=== Cover page + +The cover page will contain: + +. ELF logo + +. Document number (<>) + +. Document type (<>) + +. Document title + +. Document status (<>) + +. Date of publication + +. Responsible technical committee + +. Document authors and their affiliations, if any (<>) + +. Incorporation by reference and hyperlink of the appropriate +statements of Intellectual Property Rights, Appropriate Usage, +Trademarks, and Disclaimer of Warranty + +In co-published deliverables, as well as any further adoptions, +the document shall retain the logographic marks of the +publishing organizations. + + +=== Draft warning + +This warning must be shown on the cover page for all draft documents. + +[quote] +____ +WARNING FOR DRAFTS + +This document is not an ELF 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. +____ + +=== Public review note + +Certain ELF documents are intended for public review, as +specified in <>. + +The following note must be shown on the cover page for all documents +intended for public review. + +[quote] +____ +INSTRUCTIONS FOR REVIEW + +This draft is intended for public review. Comments shall be submitted to the issue tracker of the corresponding ELF document repository. +____ + + +=== Technical committee + +The responsible technical committee shall be shown on the cover page. + + +[[document-authors]] +=== Authors, editors and their affiliations + +Authors and editors of ELF published documents shall be shown on the +cover page. + +Each individual author or editor shall be shown on the cover page with: + +* their role (author or editor) in the creation of the document; + +* an affiliation, if the author participated through a ELF organizational membership, + where the affiliation must be a current ELF member + at the time of participation as an author or editor. + Otherwise, in the case an author is an individual member, + it should be clearly marked as so. + +When a document is attributable to a TC in its entirety, or to +ELF as an organization, no individual authorship shall be +shown on the cover page. + + +=== Contributor acknowledgement + +Contributors other than authors and editors of the document as well as +other contributing parties, shall be provided if appropriate within the Foreword. + + +=== Table of contents + +A table of contents shall be provided in any user consumable +format, including HTML, PDF and Word. + +This does not apply to standard definition files (ELF XML) +intended for machine consumption. + +The table of contents may be omitted if the document is +to be provided on paper medium with less than five (5) pages. + + +=== Sections and subsections + +The body of the document shall have section and subsection identifiers +to make it easy to refer clearly to specific items in the document. + + +=== Referable document elements + +Document elements including numbered list items, examples, and notes shall be numbered +uniquely within a clause. +Such elements shall be cited within the document by their number and containing clause. + +[example] +"Clause 3 a)" + +[example] +"6.3.3 a)" + +[example] +"8.2 Note 3" + +[example] +"2.6 Example 9" + + +Tables, figures, formulas shall be numbered uniquely within +the document. +Such elements shall be cited within the document by their type and number. + + +[example] +"Table 2" + +[example] +"Figure 5" + +[example] +"Formula 12" + + + +[[spec-foreword]] +=== Foreword + +The foreword shall be the first section of the document, unnumbered. +It is a mandatory section. + +The foreword shall contain a description of the ELF organization +and provide the necessary copyright and trademark statements. + +It is also the place to provide acknowledgements to contributors. + +In a revised ELF standard, the foreword shall also describe +a summary of changes from the previous edition. + + +=== Introduction + +The introduction shall be the second section of the document, unnumbered. +It is a mandatory section. + +It shall describe the purpose and intent of the document, as well as +potential use cases. The document's relationship with existing ELF +or external standards, if appropriate to be explained, +shall also be described here. + + +=== Scope + +The scope shall always be provided as Section 1. + + +=== Normative and informative references + +The section for normative references should be placed at Section 2 of the document. + +Informative references shall be placed at the Bibliography section +at the end of the document, unnumbered. + +References in these sections shall be fully cited. + + +[[spec-terms-definitions]] +=== Terms and definitions + +The terms and definitions sections shall be placed beginning at Section 3. + + +//// +=== Glossary + +A glossary may be provided if appropriate. + +// TODO: Where? Suggest they be considered part of Terms & Definitions. +//// + +=== Annexes and appendices + +Annexes are numbered sections provided after the main body text. +An annex may be considered informative or normative. + +Each annex is given a clause identifier of capital Latin letters starting from +the A to Z (English order). +The first annex shall be stated as (and referred to) "Annex A", +the second "Annex B", and so forth. + +Clauses within annexes shall start with the annex identifier, for example, +the first subclause in Annex A is "A.1". + +Appendixes are "annexes of annexes", and are given a clause identifier +that incorporate the annex it belongs to, followed by a capital Latin +letter starting from A to Z (English order). + +For example, the first appendix of Annex A will be "Appendix AA", +the second appendix of Annex C will be "Annex CB". + +Clauses within appendix shall start with the appendix identifier, for example, +the first subclause in Annex SA is "SA.1". + + +=== Change summary + +Changes to a document from a previous edition shall be described +in summarized, bullet-point form at the end of the Foreword (<>). + + +=== Page numbers + +For documents rendered on paper medium for user consumption, +page numbers shall be provided on all pages. + +// This is ISO practice +Page numbers shall use Roman numbers of unnumbered initial sections, +and Arabic numerals for the main body of text (including appendices). + + +=== Trademark and copyright statement + +A trademark and copyright statement of the form shown below must +appear on the cover page and the foreword. + +Note that "```yyyy```" is the 4-digit year, such as "```2009```". + +//(TODO: add trademark statement) + +[quote] +____ +(c) yyyy EXPRESS Language Foundation. + +All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on the internet or an intranet, without prior written permission. Permission can be requested from the address below. +____ + +=== Draft documents + +Draft documents should clearly indicate on the title page and +every page of the document that they are a draft document. + + +=== Canonical representation + +An ELF document shall be digitally represented in canonical form +using the ELF XML syntax, in accordance +with its defined grammar. This allows the ELF document to be +digitally rendered into any kind of supported format, including HTML, +PDF and Word. + +ELF XML is an adopted form of Metanorma XML of the Metanorma +standard document model. + diff --git a/sources/directive-document-requirements/sections/99-bibliography.adoc b/sources/directive-document-requirements/sections/99-bibliography.adoc new file mode 100644 index 0000000..c45fe28 --- /dev/null +++ b/sources/directive-document-requirements/sections/99-bibliography.adoc @@ -0,0 +1,10 @@ +[bibliography] +== Bibliography + +* [[[WTOTBT,WTO Technical Barriers To Trade Agreements]]], World Trade Organization, _The WTO Agreements Series Technical Barriers to Trade_ + +* [[[ISODIR1,ISO/IEC Directives, Part 1]]], _ISO/IEC Directives, Part 1, Procedures for the technical work_ + +* [[[ISODIR2,ISO/IEC Directives, Part 2]]], _ISO/IEC Directives, Part 2, Principles and rules for the structure and drafting of ISO and IEC documents_ + +* [[[ISODIR1C,ISO/IEC Directives, Part 1, Consolidated ISO Supplement]]], _ISO/IEC Directives, Part 1, Consolidated ISO Supplement, Procedures specific to ISO_ diff --git a/sources/directive-ipr-guidelines/document.adoc b/sources/directive-ipr-guidelines/document.adoc new file mode 100644 index 0000000..ead4ec8 --- /dev/null +++ b/sources/directive-ipr-guidelines/document.adoc @@ -0,0 +1,28 @@ += ELF Directive: Guidelines for the implementation of the ELF patent policy +:title-main-en: ELF Directive: Guidelines for the implementation of the ELF patent policy +:docnumber: 104 +:edition: 1 +:copyright-year: 2026 +:revdate: 2026-08-30 +:language: en +:doctype: standard +:technical-committee: TCB +:imagesdir: images +:mn-document-class: elf +:mn-output-extensions: xml,html,doc,pdf,rxl +:docidentifier: ELF 104:2026 +:data-uri-image: +:local-cache-only: + +include::sections/00-foreword.adoc[] + +include::sections/00-intro.adoc[] + +include::sections/01-scope.adoc[] +include::sections/02-normrefs.adoc[] +include::sections/03-terms.adoc[] +include::sections/04-disclosure.adoc[] +include::sections/05-statement.adoc[] +include::sections/06-documents.adoc[] +include::sections/90-form.adoc[] +include::sections/99-bibliography.adoc[] diff --git a/sources/directive-ipr-guidelines/reference-docs/iso-cpp-guidelines.adoc b/sources/directive-ipr-guidelines/reference-docs/iso-cpp-guidelines.adoc new file mode 100644 index 0000000..57dc861 --- /dev/null +++ b/sources/directive-ipr-guidelines/reference-docs/iso-cpp-guidelines.adoc @@ -0,0 +1,514 @@ += Guidelines for Implementation of the Common Patent Policy for ITU-T/ITU-R/ISO/IEC +:title-main-en: Guidelines for Implementation of the Common Patent Policy for ITU-T/ITU-R/ISO/IEC +:docnumber: 99999 +:copyright-year: 2018 +:ref-docnumber: 99999:2018 +:language: en +:docstage: 60 +:docsubstage: 60 +:edition: 4 +:status: published +:revdate: 2018-11-02 +:script: Latn +:technical-committee-type: IEC/ITU +:technical-committee: PUBLISH +:local-cache-only: +:data-uri-image: +:toc: + +.Summary + +The Guidelines for Implementation of the Common Patent Policy for ITU-T/ITU-R/ISO/IEC are intended to clarify and facilitate implementation of the Patent Policy, a copy of which can be found in Annex 1 and also on the web site of each Organization. + +The Patent Policy encourages the early disclosure and identification of Patents that may relate to Recommendations | Deliverables under development. In doing so, greater efficiency in standards development is possible and potential patent rights problems can be avoided. + +.History + +Edition + +* 1.0 Published initial version 1 March 2007 +* 2.0 Published first revision 23 April 2012 +* 3.0 Published second revision 26 June 2015 +* 4.0 Published third revision 2 November 2018 + + +== Part I – Common guidelines + +=== Purpose + +ITU, in its Telecommunication Standardization Sector (ITU-T) and its Radiocommunication Sector (ITU-R), ISO and IEC have had patent policies for many years, the purpose being to provide in simple words practical guidance to the participants in their Technical Bodies in case patent rights matters arise. + +Considering that the technical experts are normally not familiar with the complex issue of patent law, the Common Patent Policy for ITU-T/ITU-R/ISO/IEC (hereafter referred to as the "Patent Policy") was drafted in its operative part as a checklist, covering the three different cases which may arise if a Recommendation | Deliverable requires licences for Patents to be practiced or implemented, fully or partly. + +The Guidelines for Implementation of the Common Patent Policy for ITU-T/ITU-R/ISO/IEC (hereafter referred to as the "Guidelines") are intended to clarify and facilitate implementation of the Patent Policy, a copy of which can be found in Annex 1 and also on the web site of each Organization. + +The Patent Policy encourages the early disclosure and identification of Patents that may relate to Recommendations | Deliverables under development. In doing so, greater efficiency in standards development is possible and potential patent rights problems can be avoided. + +The Organizations should not be involved in evaluating patent relevance or essentiality with regards to Recommendations | Deliverables, interfere with licensing negotiations, or engage in settling disputes on Patents; this should be left - as in the past - to the parties concerned. + +Organization-specific provisions are contained in Part II of this document. However, it is understood that those Organization-specific provisions shall contradict neither the Patent Policy nor the Guidelines. + +=== Explanation of terms + +Contribution:: Any document submitted for consideration by a Technical Body. + +Free of Charge:: The words "Free of Charge" do not mean that the Patent Holder is waiving all of its rights with respect to the Patent. Rather, "Free of Charge" refers to the issue of monetary compensation; i.e., that the Patent Holder will not seek any monetary compensation as part of the licensing arrangement (whether such compensation is called a royalty, a one-time licensing fee, etc.). However, while the Patent Holder in this situation is committing to not charging any monetary amount, the Patent Holder is still entitled to require that the implementer of the relevant Recommendation | Deliverable sign a license agreement that contains other reasonable terms and conditions such as those relating to governing law, field of use, warranties, etc. + +Organizations:: ITU, ISO and IEC. + +Patent:: The word "Patent" means those claims contained in and identified by patents, utility models and other similar statutory rights based on inventions (including applications for any of these) solely to the extent that any such claims are essential to the implementation of a Recommendation | Deliverable. Essential patents are patents that would be required to implement a specific Recommendation | Deliverable. + +Patent Holder:: Person or entity that owns, controls and/or has the ability to license Patents. + +Reciprocity:: The word "Reciprocity" means that the Patent Holder shall only be required to license any prospective licensee if such prospective licensee will commit to license its Patent(s) for implementation of the same relevant Recommendation | Deliverable Free of Charge or under reasonable terms and conditions. + +Recommendations | Deliverables:: ITU-T and ITU-R Recommendations are referred to as "Recommendations", ISO deliverables and IEC deliverables are referred to as "Deliverables". The various types of Recommendation(s) | Deliverable(s) are referred to as "Document types" in the Patent Statement and Licensing Declaration Form (hereafter referred to as "Declaration Form") attached as Annex 2. + +Technical Bodies:: Study Groups, any subordinate groups and other groups of ITU-T and ITU-R and technical committees, subcommittees and working groups in ISO and IEC. + +=== Patent disclosure + +As mandated by the Patent Policy in its paragraph 1, any party participating footnote:[In the case of ISO and IEC, this includes any recipient of a draft standard at any stage in the standards development process.] in the work of the Organizations should, from the outset, draw their attention to any known Patent or to any known pending Patent application, either its own or that of other organizations. + +In this context, the words "from the outset" imply that such information should be disclosed as early as possible during the development of the Recommendation | Deliverable. This might not be possible when the first draft text appears since at this time, the text might be still too vague or subject to subsequent major modifications. Moreover, that information should be provided in good faith and on a best effort basis, but there is no requirement for patent searches. + +In addition to the above, any party not participating in Technical Bodies may draw the attention of the Organizations to any known Patent, either their own and/or of any third-party. + +When disclosing their own Patents, Patent Holders have to use the Patent Statement and Licensing Declaration Form (referred to as the "Declaration Form") as stated in Section 4 of these Guidelines. + + +Any communication drawing the attention to any third-party Patent should be addressed to the concerned Organization(s) in writing. The potential Patent Holder will then be requested by the Director/CEO of the relevant Organization(s) to submit a Declaration Form, if applicable. + +The Patent Policy and these Guidelines also apply to any Patent disclosed or drawn to the attention of the Organizations subsequent to the approval of a Recommendation | Deliverable. + +Whether the identification of the Patent took place before or after the approval of the Recommendation | Deliverable, if the Patent Holder is unwilling to license under paragraph 2.1 or 2.2 of the Patent Policy, the Organizations will promptly advise the Technical Bodies responsible for the affected Recommendation | Deliverable so that appropriate action can be taken. Such action will include, but may not be limited to, a review of the Recommendation | Deliverable or its draft in order to remove the potential conflict or to further examine and clarify the technical considerations causing the conflict. + +=== Patent Statement and Licensing Declaration Form + +==== The purpose of the Declaration Form + +To provide clear information in the Patent Information databases of each Organization, Patent Holders have to use the Declaration Form, which is available on the web site of each Organization (the Declaration Form is included in Annex 2 for information purposes). They must be sent to the Organizations for the attention, for ITU, of the Directors of the TSB or the BR or, for ISO or IEC, of the CEOs. The purpose of the Declaration Form is to ensure a standardized submission to the respective Organizations of the declarations being made by Patent Holders. + +The Declaration Form gives Patent Holders the means of making a licensing declaration relative to rights in Patents required for implementation of a specific Recommendation | Deliverable. Specifically, by submitting this Declaration Form the submitting party declares its willingness to license (by selecting option 1 or 2 on the Form) /or its unwillingness to license (by selecting option 3 on the Form), according to the Patent Policy, Patents held by it and whose licence would be required to practice or implement part(s) or all of a specific Recommendation | Deliverable. + +If a Patent Holder has selected the licensing option 3 on the Declaration Form, then, for the referenced relevant ITU Recommendation and ISO or IEC Deliverable, the ITU, ISO and IEC require the Patent Holder to provide certain additional information permitting patent identification. + +Multiple Declaration Forms are appropriate if the Patent Holder wishes to identify several Patents and classifies them in different options of the Declaration Form for the same Recommendation | Deliverable or if the Patent Holder classifies different claims of a complex patent in different options of the Declaration Form. + +Information contained in a Declaration Form may be corrected in case of obvious errors, such as a typographical mistake in a standard or patent reference number. The licensing declaration contained in the Declaration Form remains in force unless it is superseded by another Declaration Form containing more favourable licensing terms and conditions from a licensee's perspective reflecting (a) a change in commitment from option 3 to either option 1 or option 2, (b) a change in commitment from option 2 to option 1 or (c) un-checking one or more sub-options contained within option 1 or 2. + +==== Contact information + +In completing Declaration Forms, attention should be given to supplying contact information that will remain valid over time. Where possible, the "Name and Department" and e-mail address should be generic. Also it is preferable, where possible, that parties, particularly multinational organizations, indicate the same contact point on all Declaration Forms submitted. + +With a view to maintaining up-to-date information in the Patent Information database of each Organization, it is requested that the Organizations be informed of any change or corrections to the Declaration Form submitted in the past, especially with regard to the contact person. + +=== Conduct of meetings + +Early disclosure of Patents contributes to the efficiency of the process by which Recommendations | Deliverables are established. Therefore, each Technical Body, in the course of the development of a proposed Recommendation | Deliverable, will request the disclosure of any known Patents essential to the proposed Recommendation | Deliverable. + +Chairmen of Technical Bodies will, if appropriate, ask, at an appropriate time in each meeting, whether anyone has knowledge of patents, the use of which may be required to practice or implement the Recommendation | Deliverable being considered. The fact that the question was asked shall be recorded in the meeting report, along with any affirmative responses. + +As long as the Organization concerned has received no indication of a Patent Holder selecting paragraph 2.3 of the Patent Policy, the Recommendation | Deliverable may be approved using the appropriate and respective rules of the Organization concerned. It is expected that discussions in Technical Bodies will include consideration of including patented material in a Recommendation | Deliverable, however the Technical Bodies may not take position regarding the essentiality, scope, validity or specific licensing terms of any claimed Patents. + +=== Patent Information database + +In order to facilitate both the standards-making process and the application of Recommendations | Deliverables, each Organization makes available to the public a Patent Information database composed of information that was communicated to the Organizations by the means of Declaration Forms. The Patent Information database may contain information on specific patents, or may contain no such information but rather a statement about compliance with the Patent Policy for a particular Recommendation | Deliverable. + +The Patent Information databases are not certified to be either accurate or complete, but only reflect the information that has been communicated to the Organizations. As such, the Patent Information databases may be viewed as simply raising a flag to alert users that they may wish to contact the entities who have communicated Declaration Forms to the Organizations in order to determine if patent licenses must be obtained for use or implementation of a particular Recommendation | Deliverable. + +=== Assignment or Transfer of Patent Rights + +The rules governing the assignment or transfer of Patent rights are contained in the patent statement and licensing declaration forms (see Annexes 2 and 3). By complying with these rules, the Patent Holder has discharged in full all of its obligations and liability with regards to the licensing commitments after the transfer or assignment. These rules are not intended to place any duty on the Patent Holder to compel compliance with the licensing commitment by the assignee or transferee after the transfer occurs. + + +== Part II – Organization-specific provisions + +=== Specific provisions for ITU + +==== ITU-1 General Patent Statement and Licensing Declaration Form + +Anyone may submit a General Patent Statement and Licensing Declaration Form which is available on the web sites of ITU-T and ITU-R (the form in Annex 3 is included for information purposes). The purpose of this form is to give Patent Holders the voluntary option of making a general licensing declaration relative to material protected by Patents contained in any of their Contributions. Specifically, by submitting its form, the Patent Holder declares its willingness to license its Patents owned by it in case part(s) or all of any proposals contained in its Contributions submitted to the Organization are included in Recommendation(s) and the included part(s) contain items for which Patents have been filed and whose licence would be required to practice or implement Recommendation(s). + +The General Patent Statement and Licensing Declaration Form is not a replacement for the "individual" (see clause 4 of Part I) Declaration Form, which is made per Recommendation, but is expected to improve responsiveness and early disclosure of the Patent Holder's compliance with the Patent Policy. Therefore, in addition to its existing General Patent Statement and Licensing Declaration in respect of its Contributions, the Patent Holder should, when appropriate (e.g. if it becomes aware that it has a Patent for a specific Recommendation), also submit an "individual" Patent Statement and Licensing Declaration Form: + +-- +* for the Patents contained in any of its Contributions submitted to the Organization which are included in a Recommendation, any such "individual" Patent Statement and Licensing Declarations may contain either the same licensing terms and conditions as in the General Patent Statement and Licensing Declaration Form, or more favourable licensing terms and conditions from a licensee's perspective as defined in the "individual" (see clause 4.1 of Part I) Declaration Form; and + +* for the Patents that the Patent Holder did not contribute to the Organization which are included in a Recommendation, any such "individual" Patent Statement and Licensing Declarations may contain any of the three options available on the Form (see clause 4.1 of Part I), regardless of the commitment in its existing General Patent Statement and Licensing Declaration. +-- + +The General Patent Statement and Licensing Declaration remains in force unless it is superseded by another General Patent Statement and Licensing Declaration form containing more favourable licensing terms and conditions from a licensee's perspective reflecting (a) a change in commitment from option 2 to option 1 or (b) un-checking one or more sub- options contained within option 1 or 2. + +The ITU Patent Information database also contains a record of General Patent Statement and Licensing Declarations. + + +==== ITU-2 Notification + +Text shall be added to the cover sheets of all new and revised ITU-T and ITU-R Recommendations, where appropriate, urging users to consult the ITU Patent Information database. The wording is: + +____ +"ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU [had/had not] received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the ITU Patent Information database." +____ + + +=== Specific provisions for ISO and IEC + +==== ISO/IEC-1 Consultations on draft Deliverables + +All drafts submitted for comment shall include on the cover page the following text: + +____ +"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." +____ + +==== ISO/IEC-2 Notification + +A published document for which no patent rights are identified during the preparation thereof shall contain the following notice in the foreword: + +____ +"Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. ISO [and/or] IEC shall not be held responsible for identifying any or all such patent rights." +____ + +A published document for which patent rights have been identified during the preparation thereof shall include the following notice in the introduction: + +____ +"The International Organization for Standardization (ISO) [and/or] International Electrotechnical Commission (IEC) draws attention to the fact that it is claimed that compliance with this document may involve the use of a patent concerning (... subject matter ...) given in (... subclause ...). + +ISO [and/or] IEC take[s] no position concerning the evidence, validity and scope of this patent right. + +The holder of this patent right has assured the ISO [and/or] IEC that he/she is willing to negotiate licences under reasonable and non-discriminatory terms and conditions with applicants throughout the world. In this respect, the statement of the holder of this patent right is registered with ISO [and/or] IEC. Information may be obtained from: + +name of holder of patent right ... + +address ... + +Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights other than those identified above. ISO [and/or] IEC shall not be held responsible for identifying any or all such patent rights." +____ + +==== ISO/IEC-3 National Adoptions + +Patent Declarations in ISO, IEC and ISO/IEC Deliverables apply only to the ISO and/or IEC documents indicated in the Declaration Forms. Declarations do not apply to documents that are altered (such as through national or regional adoption). However, implementations that conform to identical national and regional adoptions and the respective ISO and/or IEC Deliverables, may rely on Declarations submitted to ISO and/or IEC for such Deliverables. + + +[appendix,obligation="normative"] +== Common patent policy for ITU-T/ITU-R/ISO/IEC + +The following is a "code of practice" regarding patents covering, in varying degrees, the subject matters of ITU-T Recommendations, ITU-R Recommendations, ISO deliverables and IEC deliverables (for the purpose of this document, ITU-T and ITU-R Recommendations are referred to as "Recommendations", ISO deliverables and IEC deliverables are referred to as "Deliverables"). The rules of the "code of practice" are simple and straightforward. Recommendations | Deliverables are drawn up by technical and not patent experts; thus, they may not necessarily be very familiar with the complex international legal situation of intellectual property rights such as patents, etc. + +Recommendations | Deliverables are non-binding; their objective is to ensure compatibility of technologies and systems on a worldwide basis. To meet this objective, which is in the common interests of all those participating, it must be ensured that Recommendations | Deliverables, their applications, use, etc. are accessible to everybody. + +It follows, therefore, that a patent embodied fully or partly in a Recommendation | Deliverable must be accessible to everybody without undue constraints. To meet this requirement in general is the sole objective of the code of practice. The detailed arrangements arising from patents (licensing, royalties, etc.) are left to the parties concerned, as these arrangements might differ from case to case. + +This code of practice may be summarized as follows: + +. The ITU Telecommunication Standardization Bureau (TSB), the ITU Radio-communication Bureau (BR) and the offices of the CEOs of ISO and IEC are not in a position to give authoritative or comprehensive information about evidence, validity or scope of patents or similar rights, but it is desirable that the fullest available information should be disclosed. Therefore, any party participating in the work of ITU, ISO or IEC should, from the outset, draw the attention of the Director of ITU-TSB, the Director of ITU-BR, or the offices of the CEOs of ISO or IEC, respectively, to any known patent or to any known pending patent application, either their own or of other organizations, although ITU, ISO or IEC are unable to verify the validity of any such information. + +. If a Recommendation | Deliverable is developed and such information as referred to in paragraph 1 has been disclosed, three different situations may arise: + +.. The patent holder is willing to negotiate licences free of charge with other parties on a non-discriminatory basis on reasonable terms and conditions. Such negotiations are left to the parties concerned and are performed outside ITU-T/ITU-R/ISO/IEC. + +.. The patent holder is willing to negotiate licences with other parties on a non- discriminatory basis on reasonable terms and conditions. Such negotiations are left to the parties concerned and are performed outside ITU-T/ITU-R/ISO/IEC. + +.. The patent holder is not willing to comply with the provisions of either paragraph 2.1 or paragraph 2.2; in such case, the Recommendation | Deliverable shall not include provisions depending on the patent. + +. Whatever case applies (2.1, 2.2 or 2.3), the patent holder has to provide a written statement to be filed at ITU-TSB, ITU-BR or the offices of the CEOs of ISO or IEC, respectively, using the appropriate "Patent Statement and Licensing Declaration" Form. This statement must not include additional provisions, conditions, or any other exclusion clauses in excess of what is provided for each case in the corresponding boxes of the form. +10 + +[appendix,obligation="normative"] +== Patent Statement and Licensing Declaration Form for ITU-T or ITU-R Recommendation | ISO or IEC Deliverable + +Patent Statement and Licensing Declaration for ITU-T or ITU-R Recommendation | ISO or IEC Deliverable + +_This declaration does not represent an actual grant of a license_ + +Please return to the relevant organization(s) as instructed below per document type: + +[cols="a,a,a,a"] +|=== + +| +Director + +Telecommunication Standardization Bureau + +International Telecommunication Union + +Place des Nations + +CH-1211 Geneva 20, Switzerland + +Fax: +41 22 730 5853 + +Email: tsbdir@itu.int + +| +Director + +Radiocommunication Bureau + +International Telecommunication Union + +Place des Nations + +CH-1211 Geneva 20, Switzerland + +Fax: +41 22 730 5785 + +Email: brmail@itu.int + + +| + +Secretary-General + +International Organization for Standardization + +8 Chemin de Blandonnet + +CP 401 + +1214 Vernier, Geneva Switzerland + +Fax: +41 22 733 3430 + +Email: patent.statements@iso.org + + +| +General Secretary + +International Electrotechnical Commission + +3 rue de Varembé + +CH-1211 Geneva 20 Switzerland + +Fax: +41 22 919 0300 + +Email: inmail@iec.ch + + +|=== + + + + +=== Patent Holder + +* Legal Name: pass:[__________________________] + + +=== Contact for license application + +* Name & Department pass:[__________________________] +* Address pass:[__________________________] +* Tel. pass:[__________________________] +* Fax pass:[__________________________] +* E-mail pass:[__________________________] +* URL (optional) pass:[__________________________] + + +=== Document type + +(please return the form to the relevant Organization) + +* [ ] ITU-T Rec. +* [ ] ITU-R Rec. +* [ ] ISO Deliverable +* [ ] IEC Deliverable + +* [ ] Common text or twin text (ITU-T Rec. | ISO/IEC Deliverable) (for common text or twin text, +please return the form to each of the three Organizations: ITU-T, ISO, IEC) + +* [ ] ISO/IEC Deliverable +(for ISO/IEC Deliverables, please return the form to both ISO and IEC) + + +=== Common + +* Number pass:[__________________________] + +* Title pass:[__________________________] + + +=== Licensing declaration + +The Patent Holder believes that it holds granted and/or pending applications for Patents, the use of which would be required to implement the above document and hereby declares, in accordance with the Common Patent Policy for ITU-T/ITU-R/ISO/IEC, that (check one box only): + +[ ] 1. The Patent Holder is prepared to grant a Free of Charge license to an unrestricted number of applicants on a worldwide, non-discriminatory basis and under other reasonable terms and conditions to make, use, and sell implementations of the above document. + +Negotiations are left to the parties concerned and are performed outside the ITU-T, ITU-R, ISO or IEC. + +Also mark here __ if the Patent Holder's willingness to license is conditioned on Reciprocity for the above document. + +Also mark here __ if the Patent Holder reserves the right to license on reasonable terms and conditions (but not Free of Charge) to applicants who are only willing to license their Patent, whose use would be required to implement the above document, on reasonable terms and conditions (but not Free of Charge). + +[ ] 2. The Patent Holder is prepared to grant a license to an unrestricted number of applicants on a worldwide, non-discriminatory basis and on reasonable terms and conditions to make, use and sell implementations of the above document. + +Negotiations are left to the parties concerned and are performed outside the ITU-T, ITU-R, ISO, or IEC. + +Also mark here __ if the Patent Holder's willingness to license is conditioned on Reciprocity for the above document. + + +[ ] 3. The Patent Holder is unwilling to grant licenses in accordance with provisions of either 1 or 2 above. + +In this case, the following information must be provided to ITU, ISO and/or IEC as part of this declaration: + +- granted patent number or patent application number (if pending); +- an indication of which portions of the above document are affected; +- a description of the Patents covering the above document. + + +Free of Charge:: The words "Free of Charge" do not mean that the Patent Holder is waiving all of its rights with respect to the Patent. Rather, "Free of Charge" refers to the issue of monetary compensation; i.e., that the Patent Holder will not seek any monetary compensation as part of the licensing arrangement (whether such compensation is called a royalty, a one-time licensing fee, etc.). However, while the Patent Holder in this situation is committing to not charging any monetary amount, the Patent Holder is still entitled to require that the implementer of the same above document sign a license agreement that contains other reasonable terms and conditions such as those relating to governing law, field of use, warranties, etc. + +Reciprocity:: The word "Reciprocity" means that the Patent Holder shall only be required to license any prospective licensee if such prospective licensee will commit to license its Patent(s) for implementation of the same above document Free of Charge or under reasonable terms and conditions. + +Patent:: The word "Patent" means those claims contained in and identified by patents, utility models and other similar statutory rights based on inventions (including applications for any of these) solely to the extent that any such claims are essential to the implementation of the same above document. Essential patents are patents that would be required to implement a specific Recommendation | Deliverable. + +Assignment/transfer of Patent rights:: Licensing declarations made pursuant to Clause 2.1 or 2.2 of the Common Patent Policy for ITU-T/ITU-R/ISO/IEC shall be interpreted as encumbrances that bind all successors-in-interest as to the transferred Patents. Recognizing that this interpretation may not apply in all jurisdictions, any Patent Holder who has submitted a licensing declaration according to the Common Patent Policy - be it selected as option 1 or 2 on the Patent Declaration form - who transfers ownership of a Patent that is subject to such licensing declaration shall include appropriate provisions in the relevant transfer documents to ensure that, as to such transferred Patent, the licensing declaration is binding on the transferee and that the transferee will similarly include appropriate provisions in the event of future transfers with the goal of binding all successors-in-interest. + +=== Patent Information + +(desired but not required for options 1 and 2; required in ITU, ISO and IEC for option 3 (NOTE)) + +[cols="1,1,1,1,1",options="header"] +|=== +|No. +|Status [granted/ pending] +|Country +|Granted Patent Number or Application Number (if pending) +|Title + +|1|||| +|2|||| +|3|||| +|4|||| +|5|||| +|6|||| +|7|||| +|8|||| +|9|||| +|10|||| + +|=== + +[ ] Check here if additional patent information is provided on additional pages. + +NOTE: For option 3, the additional minimum information that shall also be provided is listed in the option 3 box above. + +=== Signature (include on final page only) + +* Patent Holder pass:[__________________________] +* Name of authorized person pass:[__________________________] +* Title of authorized person pass:[__________________________] +* Signature, Place, Date pass:[__________________________] + + +FORM: 2 November 2018 + +[appendix,obligation="normative"] +== General Patent Statement and Licensing Declaration Form for ITU-T or ITU-R Recommendation + +_This declaration does not represent an actual grant of a license_ + +Please return to the relevant bureau: + + +[cols="a,a"] +|=== + +| +Director + +Telecommunication Standardization Bureau + +International Telecommunication Union + +Place des Nations + +CH-1211 Geneva 20, Switzerland + +Fax: +41 22 730 5853 + +Email: tsbdir@itu.int + +| +Director + +Radiocommunication Bureau + +International Telecommunication Union + +Place des Nations + +CH-1211 Geneva 20, Switzerland + +Fax: +41 22 730 5785 + +Email: brmail@itu.int + +|=== + + + +=== Patent Holder + +* Legal Name pass:[__________________________] + + +=== Contact for license application + +* Name & Department pass:[__________________________] +* Address pass:[__________________________] +* Tel. pass:[__________________________] +* Fax pass:[__________________________] +* E-mail pass:[__________________________] +* URL (optional) pass:[__________________________] + + +=== Licensing declaration + +In case part(s) or all of any proposals contained in Contributions submitted by the Patent Holder above are included in ITU-T/ITU-R Recommendation(s) and the included part(s) contain items for which Patents have been filed and whose use would be required to implement ITU-T/ITU-R Recommendation(s), the above Patent Holder hereby declares, in accordance with the Common Patent Policy for ITU-T/ITU-R/ISO/IEC (check one box only): + + +[ ] 1. The Patent Holder is prepared to grant a Free of Charge license to an unrestricted number of applicants on a worldwide, non-discriminatory basis and under other reasonable terms and conditions to make, use, and sell implementations of the relevant ITU-T/ITU-R Recommendation. + +Negotiations are left to the parties concerned and are performed outside the ITU-T/ITU-R. + +Also mark here __ if the Patent Holder's willingness to license is conditioned on Reciprocity for the above ITU-T/ITU-R Recommendation. + +Also mark here __ if the Patent Holder reserves the right to license on reasonable terms and conditions (but not Free of Charge) to applicants who are only willing to license their patent claims, whose use would be required to implement the above ITU-T/ITU-R Recommendation, on reasonable terms and conditions (but not Free of Charge). + + +[ ] 2. The Patent Holder is prepared to grant a license to an unrestricted number of applicants on a worldwide, non-discriminatory basis and on reasonable terms and conditions to make, use and sell implementations of the relevant ITU-T/ITU-R Recommendation. + +Negotiations are left to the parties concerned and are performed outside the ITU-T/ITU-R. + +Also mark here __ if the Patent Holder's willingness to license is conditioned on Reciprocity for the above ITU-T/ITU-R Recommendation. + + +Free of Charge:: The words "Free of Charge" do not mean that the Patent Holder is waiving all of its rights with respect to the Patent. Rather, "Free of Charge" refers to the issue of monetary compensation; i.e., that the Patent Holder will not seek any monetary compensation as part of the licensing arrangement (whether such compensation is called a royalty, a one-time licensing fee, etc.). However, while the Patent Holder in this situation is committing to not charging any monetary amount, the Patent Holder is still entitled to require that the implementer of the relevant ITU-T/ITU-R Recommendation sign a license agreement that contains other reasonable terms and conditions such as those relating to governing law, field of use, warranties, etc. + + +Reciprocity:: The word "Reciprocity" means that the Patent Holder shall only be required to license any prospective licensee if such prospective licensee will commit to license its Patent(s) for implementation of the relevant ITU-T/ITU-R Recommendation Free of Charge or under reasonable terms and conditions. + +Patent:: The word "Patent" means those claims contained in and identified by patents, utility models and other similar statutory rights based on inventions (including applications for any of these) solely to the extent that any such claims are essential to the implementation of the relevant Recommendation | Deliverable. Essential patents are patents that would be required to implement a specific Recommendation | Deliverable. + +Assignment/transfer of Patent rights:: Licensing declarations made pursuant to Clause 2.1 or 2.2 of the Common Patent Policy for ITU-T/ITU-R/ISO/IEC shall be interpreted as encumbrances that bind all successors-in-interest as to the transferred Patents. Recognizing that this interpretation may not apply in all jurisdictions, any Patent Holder who has submitted a licensing declaration according to the Common Patent Policy - be it selected as option 1 or 2 on the Patent Declaration form - who transfers ownership of a Patent that is subject to such licensing declaration shall include appropriate provisions in the relevant transfer documents to ensure that, as to such transferred Patent, the licensing declaration is binding on the transferee and that the transferee will similarly include appropriate provisions in the event of future transfers with the goal of binding all successors-in-interest. + + +=== Signature + +* Patent Holder pass:[__________________________] +* Name of authorized person pass:[__________________________] +* Title of authorized person pass:[__________________________] +* Signature, Place, Date pass:[__________________________] + + + +Published in Switzerland + +GENEVA, 2018 + diff --git a/sources/directive-ipr-guidelines/sections/00-foreword.adoc b/sources/directive-ipr-guidelines/sections/00-foreword.adoc new file mode 100644 index 0000000..21c8d43 --- /dev/null +++ b/sources/directive-ipr-guidelines/sections/00-foreword.adoc @@ -0,0 +1,33 @@ +.Foreword +The EXPRESS Language Foundation ("`ELF`") is a registered public charity in the +US that facilitates the education, standardization, research, promotion, +definition, and usage of information modelling and programming languages, with a +focus on the EXPRESS language family. + +ELF works with international partners and experts across the globe, reflecting +the international nature of its mission. More information about ELF is available +on the official website (https://www.expresslang.org). + +The procedures used to develop this document and those intended for its further +maintenance are described in the ELF Directives. + +In particular the different approval criteria needed for the different types of +ELF documents should be noted. This document was drafted in accordance with the +editorial rules of the ELF Directives. + +Attention is drawn to the possibility that some of the elements of this +document may be the subject of patent rights. ELF shall not be held responsible +for identifying any or all such patent rights. Details of any patent rights +identified during the development of the document will be provided in the +Introduction. + +Any trade name used in this document is information given for the convenience of +users and does not constitute an endorsement. + +This document was prepared by the Technical Coordination Board (TCB). + +This document provides guidance on the implementation of the +ELF patent policy (<>) as applicable +to internal process and procedures, especially in relation +to the standardization and publication processes described in +<>. diff --git a/sources/directive-ipr-guidelines/sections/00-intro.adoc b/sources/directive-ipr-guidelines/sections/00-intro.adoc new file mode 100644 index 0000000..c7f493f --- /dev/null +++ b/sources/directive-ipr-guidelines/sections/00-intro.adoc @@ -0,0 +1,44 @@ +== Introduction + +=== General + +ELF is committed to expanding the realm of standards for information +modelling and programming languages, with a focus on the EXPRESS +language family and interoperability across the globe and communities +of practice. + +As a proponent of open standards, ELF has adopted a patent policy +in <> to align IPR practice with major international +standardization bodies including ISO, IEC and ITU. + +=== Purpose + +This document describes guidelines for the implementation of the +ELF patent policy specified in <> +in the standardization and publication processes described +in <>. + +The intent of this document is to: + +* encourage the early disclosure and identification of patents during the +standardization and publication processes; + +* resolve potential patent concerns and rights problems relevant to +the standardization and publication processes. + + +//// + + +ITU, in its Telecommunication Standardization Sector (ITU-T) and its Radiocommunication Sector (ITU-R), ISO and IEC have had patent policies for many years, the purpose being to provide in simple words practical guidance to the participants in their Technical Bodies in case patent rights matters arise. + +Considering that the technical experts are normally not familiar with the complex issue of patent law, the Common Patent Policy for ITU-T/ITU-R/ISO/IEC (hereafter referred to as the "Patent Policy") was drafted in its operative part as a checklist, covering the three different cases which may arise if a Recommendation | Deliverable requires licences for Patents to be practiced or implemented, fully or partly. + +The Guidelines for Implementation of the Common Patent Policy for ITU-T/ITU-R/ISO/IEC (hereafter referred to as the "Guidelines") are intended to clarify and facilitate implementation of the Patent Policy, a copy of which can be found in Annex 1 and also on the web site of each Organization. + +The Patent Policy encourages the early disclosure and identification of Patents that may relate to Recommendations | Deliverables under development. In doing so, greater efficiency in standards development is possible and potential patent rights problems can be avoided. + +The Organizations should not be involved in evaluating patent relevance or essentiality with regards to Recommendations | Deliverables, interfere with licensing negotiations, or engage in settling disputes on Patents; this should be left - as in the past - to the parties concerned. + +Organization-specific provisions are contained in Part II of this document. However, it is understood that those Organization-specific provisions shall contradict neither the Patent Policy nor the Guidelines. +//// diff --git a/sources/directive-ipr-guidelines/sections/01-scope.adoc b/sources/directive-ipr-guidelines/sections/01-scope.adoc new file mode 100644 index 0000000..8f9d991 --- /dev/null +++ b/sources/directive-ipr-guidelines/sections/01-scope.adoc @@ -0,0 +1,12 @@ +== Scope + +This document provides guidelines on the application of +the ELF patent policy (<>) towards the following +areas of ELF: + +* standardization and publication process (described in <>); +* document requirements (described in <>). + +This document does not cover the implementation of requirements +in ELF standards which involve intellectual property rights +(such as patents). diff --git a/sources/directive-ipr-guidelines/sections/02-normrefs.adoc b/sources/directive-ipr-guidelines/sections/02-normrefs.adoc new file mode 100644 index 0000000..e089cee --- /dev/null +++ b/sources/directive-ipr-guidelines/sections/02-normrefs.adoc @@ -0,0 +1,8 @@ +[bibliography] +== Normative References + +* [[[DIR101,ELF 101:2026]]], _ELF Directive: Standardization and publication_ + +* [[[DIR102,ELF 102:2026]]], _ELF Directive: Standard document requirements_ + +* [[[DIR103,ELF 103:2026]]], _ELF Directive: Patent policy_ diff --git a/sources/directive-ipr-guidelines/sections/03-terms.adoc b/sources/directive-ipr-guidelines/sections/03-terms.adoc new file mode 100644 index 0000000..19c5443 --- /dev/null +++ b/sources/directive-ipr-guidelines/sections/03-terms.adoc @@ -0,0 +1,94 @@ + +[source="DIR101,DIR102,DIR103"] + +[[terms]] +== Terms and definitions + + +=== declaration form + +"`Patent Statement and Licensing Declaration Form`" as stated in <> + + +[[term-contribution]] +=== contribution + +content submitted to ELF for consideration as part of a ELF +standardization deliverable + +//// +Contribution:: Any document submitted for consideration by a Technical Body. +//// + +[[term-free-of-charge]] +=== free of charge + +_patent holder_ (<>) will not seek any monetary compensation as part of the licensing arrangement (whether such compensation is called a royalty, a one-time licensing fee, etc.); patent holder is still entitled to require that the implementer of the relevant ELF standardization deliverable sign a license agreement that contains other reasonable terms and conditions (such as those relating to governing law, field of use, warranties, etc.); does not indicate that the patent holder is waiving all of its rights with respect to a patent, but only on the issue of monetary compensation + +//// +Free of Charge:: The words "Free of Charge" do not mean that the Patent Holder is waiving all of its rights with respect to the Patent. Rather, "Free of Charge" refers to the issue of monetary compensation; i.e., that the Patent Holder will not seek any monetary compensation as part of the licensing arrangement (whether such compensation is called a royalty, a one-time licensing fee, etc.). However, while the Patent Holder in this situation is committing to not charging any monetary amount, the Patent Holder is still entitled to require that the implementer of the relevant deliverable sign a license agreement that contains other reasonable terms and conditions such as those relating to governing law, field of use, warranties, etc. +//// + + +[[term-patent]] +=== patent + +claims contained in and identified by patents, utility models and other similar statutory rights based on inventions (including applications for any of these) solely to the extent that any such claims are essential to the implementation of an ELF standardization deliverable + +[[term-essential-patent]] +=== essential patent + +_patent_ (<>) is essential to implement a specific ELF standardization deliverable + +//// +Patent:: The word "Patent" means those claims contained in and identified by patents, utility models and other similar statutory rights based on inventions (including applications for any of these) solely to the extent that any such claims are essential to the implementation of a deliverable. Essential patents are patents that would be required to implement a specific deliverable. +//// + +[[term-patent-holder]] +=== patent holder + +person or entity that owns, controls and/or has the ability to license _patents_ (<>) + +//// +Patent Holder:: Person or entity that owns, controls and/or has the ability to license Patents. +//// + + +[[term-reciprocity]] +=== reciprocity + +_patent holder_ (<>) shall only be required to license any prospective licensee if such prospective licensee will commit to license its patent(s) for implementation of the same relevant ELF standardization deliverable _free of charge_ (<>) or under reasonable terms and conditions + +//// +Reciprocity:: The word "Reciprocity" means that the Patent Holder shall only be required to license any prospective licensee if such prospective licensee will commit to license its Patent(s) for implementation of the same relevant deliverable Free of Charge or under reasonable terms and conditions. +//// + +[[term-declaration]] +=== patent declaration + +notice or acknowledgement that a patent may cover the use of an ELF standardization deliverable + +NOTE: The patent statement and licensing declaration form provided in <> shall be used for all patent declarations for an ELF standardization deliverable (see <>). + + +[[term-patent-information-database]] +=== patent information database + +database containing patent information relating to +ELF standardization deliverables +based on information provided to ELF in the patent statement and licensing declaration + +//// +TODO: define licensee +TODO: define reasonable terms and conditions +//// + +[[term-technical-body]] +=== technical body + +technical committees and any other groups that manage +development of ELF standardization deliverables + +//// +Technical Bodies:: Study Groups, any subordinate groups and other groups of ITU-T and ITU-R and technical committees, subcommittees and working groups in ISO and IEC. +//// diff --git a/sources/directive-ipr-guidelines/sections/04-disclosure.adoc b/sources/directive-ipr-guidelines/sections/04-disclosure.adoc new file mode 100644 index 0000000..22aab4a --- /dev/null +++ b/sources/directive-ipr-guidelines/sections/04-disclosure.adoc @@ -0,0 +1,73 @@ + +[[patent-disclosure]] +== Patent disclosure + + +=== General + +This clause describes the principles of disclosure of patents +that may affect ELF standardization deliverables produced +by ELF. + +This clause applies to any patent disclosed or drawn +to the attention of ELF during the development +of and subsequent to the approval of deliverables. + +=== Requirements + +==== Participation obligation + +All parties participating in the standardization activities of ELF +are obligated to inform ELF of +any known patent or to any known pending patent application, +either its own or that of other entities, +as mandated by <>, +where such parties include recipients of a draft ELF standardization deliverable at any stage. + +==== Early disclosure + +Patent information should be disclosed as early as possible during the development of the deliverable. + +Such patent information should be provided in good faith and on a best effort basis. There is no requirement for patent searches. +At times, this might not be possible when the first draft text appears, for example, because the text might be still too vague. + +//// +Lore Unt (Apple): +I suggest generally not breaking out the text from the ITU guidelines as “NOTES,” since the status of the notes is somewhat confusing. The deleted text of note 1 could be kept in the text, or ideally could be modified as follows “At times, this might not be possible when the first draft text appears, for example, because the text might be still too vague.” + +NOTE: This might not be possible when the first draft text appears since at this time, the text might be still too vague or subject to subsequent major modifications. +//// + +==== External-originating disclosure + +Parties not participating in the standardization activities of ELF may also inform ELF to any known patent, either their own and/or of any third-party, that may cover an ELF deliverable. + + +=== Method of disclosure + +==== Declaration form + +When disclosing their own patents, patent holders shall fill in the "`Patent Statement and Licensing Declaration Form`" (referred to as the "`declaration form`") as stated in <>. + +==== Third-party patent disclosure + +Any communication drawing the attention to any third-party patent +should be addressed to ELF in writing. + +The Executive Director of ELF will then request the potential +patent holder to submit a declaration form, if applicable. + + +=== Resolution to unwillingness to license + +Whether the identification of the patent took place before or after +the approval of a deliverable, +if a patent holder is unwilling to license under <> or <>, ELF will promptly advise the project owner(s) responsible for the affected deliverable so that appropriate action can be taken. + +Such action shall include, but may not be limited to: + +* a review of the ELF standardization deliverable or its draft in order to remove the potential conflict; or + +* to further examine and clarify the technical considerations causing the conflict. + +These guidelines also apply to any Patent disclosed or drawn to the attention of ELF subsequent to the approval of a deliverable. diff --git a/sources/directive-ipr-guidelines/sections/05-statement.adoc b/sources/directive-ipr-guidelines/sections/05-statement.adoc new file mode 100644 index 0000000..c767589 --- /dev/null +++ b/sources/directive-ipr-guidelines/sections/05-statement.adoc @@ -0,0 +1,86 @@ + +[[patent-statement]] +== Patent statement and licensing declaration form + +=== Purpose + +The patent statement and licensing declaration form (see <>) is provided +for entities with information on how essential patents affect +ELF deliverables (such as, patent holders) +to provide consistent, accurate information in the ELF patent +information database. + +=== Procedure + +Entities shall report patent information to ELF +using the ELF patent declaration form, which is +available on the ELF website (see <>). + +The completed declaration form should be directly submitted +to the designated contact provided on the form. + +The declaration form also allows patent holders to make a licensing declaration relative to rights in patents required for implementation of a specific deliverable. + + +=== Declaration of patent license + +Specifically, by submitting this declaration form, the submitting party declares, in accordance with the ELF patent policy, patents held by it and whose licence would be required to practice or implement part(s) or all of a specific deliverable: + +. its willingness to license (by selecting option 1 or 2 on the Form); or +. its unwillingness to license (by selecting option 3 on the Form). + + +=== Additional information required due to unwillingness to license + +If a patent holder has selected the licensing option 3 on the declaration form, then, for the referenced relevant ELF deliverable, ELF requires the patent holder to provide certain additional information permitting patent identification. + +Multiple declaration forms are appropriate if the patent holder wishes to identify several patents and classifies them in different options of the declaration form for the same deliverable or if the patent holder classifies different claims of a complex patent in different options of the declaration form. + +Information contained in a declaration form may be corrected in case of obvious errors, such as a typographical mistake in a standard or patent reference number. + +=== Superseding license declarations + +The licensing declaration contained in the declaration form remains in force unless it is superseded by another declaration form containing more favorable licensing terms and conditions from a licensee's perspective reflecting: + +. a change in commitment from option 3 to either option 1 or option 2; +. a change in commitment from option 2 to option 1; or +. un-checking one or more sub-options contained within option 1 or 2. + +==== Contact information + +In completing the declaration form, attention should be given to supplying contact information that will remain valid over time: + +* "`Name`", "`Department`" and "`E-mail addresses`" should be generic. + +* A single point of contact for a particular submitting party is preferred if multiple declaration forms are submitted (particularly for multinational organizations). + +For maintaining the currency of information in the ELF patent information database, the patent declarer is urged to directly contact ELF on any change or corrections to declaration forms submitted, +especially on the change of contact points. + +=== Conduct of meetings + +Early disclosure of patents contributes to the efficiency of the process by which deliverables are established. + +Therefore, each technical body, in the course of the development of a proposed deliverable, will request the disclosure of any known patents essential to the proposed deliverable. + +The leadership of technical body will, ask at an appropriate time in each meeting, whether anyone has knowledge of patents, the use of which may be required to practice or implement the deliverable being considered. The fact that the question was asked shall be recorded in the meeting report, along with any affirmative responses. + +As long as ELF has received no indication of a patent holder selecting <>, the deliverable may be approved with normal procedure. It is expected that discussions in technical bodies will include consideration of including patented material in a deliverable, however the technical bodies may not take position regarding the essentiality, scope, validity or specific licensing terms of any claimed patents. + +=== Patent information database + +In order to facilitate both the standards-making process and the application of deliverables, ELF makes available to the public a patent information database composed of information that was communicated to ELF by the means of declaration forms. + +The patent information databases may contain information on specific patents, or may contain no such information but rather a statement about compliance with the patent policy for a particular deliverable. + +The patent information databases are not certified to be either accurate or complete, but only reflect the information that has been communicated to ELF. + +As such, the patent information databases may be viewed as simply raising a flag to alert users that they may wish to contact the entities who have communicated declaration forms to ELF in order to determine if patent licenses must be obtained for use or implementation of a particular deliverable. + +=== Assignment or transfer of patent rights + +The rules governing the assignment or transfer of patent rights are contained in the patent statement and licensing declaration forms (see <>). + +By complying with these rules, the patent holder has discharged in full all of its obligations and liability with regards to the licensing commitments after the transfer or assignment. + +These rules are not intended to place any duty on the patent holder to compel compliance with the licensing commitment by the assignee or transferee after the transfer occurs. diff --git a/sources/directive-ipr-guidelines/sections/06-documents.adoc b/sources/directive-ipr-guidelines/sections/06-documents.adoc new file mode 100644 index 0000000..2431417 --- /dev/null +++ b/sources/directive-ipr-guidelines/sections/06-documents.adoc @@ -0,0 +1,44 @@ + +[[requirements]] +== Requirements on deliverables + +=== Draft deliverables + +All drafts submitted for comment shall include on the cover page the following text: + +____ +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. +____ + +=== Notification + +A published document for which no patent rights are identified during the preparation thereof shall contain the following notice in the foreword: + +____ +Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. ELF [and ISO] [and IEC] shall not be held responsible for identifying any or all such patent rights. +____ + + +A published document for which patent rights have been identified during the preparation thereof shall include the following notice in the introduction: + +____ +The EXPRESS Language Foundation (ELF) [and The International Organization for Standardization (ISO)] [and The International Electrotechnical Commission (IEC)] draws attention to the fact that it is claimed that compliance with this document may involve the use of a patent concerning (... subject matter ...) given in (... subclause ...). + +ELF [and ISO] [and IEC] take[s] no position concerning the evidence, validity and scope of this patent right. + +The holder of this patent right has assured ELF [and ISO] [and IEC] that he/she is willing to negotiate licences under reasonable and non-discriminatory terms and conditions with applicants throughout the world. In this respect, the statement of the holder of this patent right is registered with ELF [and ISO] [and IEC]. Information may be obtained from: + +name of holder of patent right ... + +address ... + +Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights other than those identified above. ELF [and ISO] [and IEC] shall not be held responsible for identifying any or all such patent rights. +____ + +=== Collaborative developed deliverables + +Patent declarations in joint deliverables between ELF and other organizations apply only to the specific documents indicated in the declaration forms. Declarations do not apply to documents that are altered (such as through adoption). + +//// +However, implementations that conform to identical national and regional adoptions and the respective ISO and/or IEC Deliverables, may rely on declarations submitted to ISO and/or IEC for such Deliverables. +//// diff --git a/sources/directive-ipr-guidelines/sections/90-form.adoc b/sources/directive-ipr-guidelines/sections/90-form.adoc new file mode 100644 index 0000000..8c059ae --- /dev/null +++ b/sources/directive-ipr-guidelines/sections/90-form.adoc @@ -0,0 +1,193 @@ + +[[patent-form]] +[appendix,obligation="normative"] +== Patent statement and licensing declaration for ELF deliverables + +_This declaration does not represent an actual grant of a license._ + +_Definitions of terms used in this declaration are in accordance with ELF {docnumber}._ + +Please submit this form to: + +Executive Director + +EXPRESS Language Foundation + +2093 Philadelphia Pike Ste 3311 + +Claymont, Delaware 19703 + +United States of America + +Email: patents@expresslang.org + +=== Terms and definitions + +free of charge:: +patent holder will not seek any monetary compensation as part of the licensing arrangement (whether such compensation is called a royalty, a one-time licensing fee, etc.); patent holder is still entitled to require that the implementer of the relevant ELF standardization deliverable sign a license agreement that contains other reasonable terms and conditions (such as those relating to governing law, field of use, warranties, etc.); does not indicate that the patent holder is waiving all of its rights with respect to a patent, but only on the issue of monetary compensation + +patent:: +claims contained in and identified by patents, utility models and other similar statutory rights based on inventions (including applications for any of these) solely to the extent that any such claims are essential to the implementation of an ELF standardization deliverable + +essential patent:: +patent is essential to implement a specific ELF standardization deliverable + +patent holder:: +person or entity that owns, controls and/or has the ability to license patents + +reciprocity:: +patent holder shall only be required to license any prospective licensee if such prospective licensee will commit to license its patent(s) for implementation of the same relevant ELF standardization deliverable free of charge or under reasonable terms and conditions + +assignment/transfer of patent rights:: +licensing declarations made pursuant to +<> or <> +shall be interpreted as encumbrances that bind all +successors-in-interest as to the transferred patents. +Recognizing that this interpretation may not apply in all +jurisdictions, any patent holder who has submitted a licensing +declaration according to <> -- +be it selected as <> or <> on the +"`Patent statement and licensing declaration for ELF deliverables`" -- +who transfers ownership of a patent that is subject to +such licensing declaration shall include appropriate +provisions in the relevant transfer documents to ensure +that, as to such transferred patent, the licensing +declaration is binding on the transferee and that the +transferee will similarly include appropriate provisions +in the event of future transfers with the goal of binding +all successors-in-interest + + +//// +Lore Unt (Apple): + +Highly suggest adding definitions from the ITU form to this form, since the form is the operative legal document. +//// + +=== Patent Holder + +Legal Name:: +pass:[__________________________] + + +=== Contact for license application + +Name & Department:: +pass:[__________________________] + +Address:: +pass:[__________________________] + +Tel.:: +pass:[__________________________] + +Fax:: +pass:[__________________________] + +E-mail:: +pass:[__________________________] + +URL (optional):: +pass:[__________________________] + + +=== Document type + +. [ ] ELF Standardization Deliverable + +. [ ] ELF co-published Standardization Deliverable +(please return this form to ELF and the appropriate +form to the co-publishing parties) + + +=== Patent information + +Number:: +pass:[__________________________] + +Title:: +pass:[__________________________] + + + +=== Licensing declaration + +The patent holder believes that it holds granted and/or pending applications for patents, the use of which would be required to implement the above document and hereby declares, in accordance with the ELF patent policy (see <>), that (check one option only): + +. [[option-1]] [ ] The patent holder is prepared to grant a free of charge license to an unrestricted number of applicants on a worldwide, non-discriminatory basis and under other reasonable terms and conditions to make, use, and sell implementations of the above document. + +.. [[option-1a]] [ ] Also mark here -- if the patent holder's willingness to license is conditioned on reciprocity for the above document. + +.. [[option-1b]] [ ] Also mark here -- if the patent holder reserves the right to license on reasonable terms and conditions (but not free of charge) to applicants who are only willing to license their patent, whose use would be required to implement the above document, on reasonable terms and conditions (but not free of charge). + + +. [[option-2]] [ ] The patent holder is prepared to grant a license to an unrestricted number of applicants on a worldwide, non-discriminatory basis and on reasonable terms and conditions to make, use and sell implementations of the above document. + +.. [[option-2a]] [ ] Also mark here -- if the patent holder's willingness to license is conditioned on reciprocity for the above document. + + +. [[option-3]] [ ] The patent holder is unwilling to grant licenses in accordance with provisions of either options <> or <> above. ++ +In this case, the following information must be provided to ELF as part of this declaration: + ++ +-- +* granted patent number or patent application number (if pending); +* an indication of which portions of the above document are affected; +* a description of the patents covering the above document. +-- +//// +Lore Unt (Apple): + +Suggest that the “licensing negotiations” text below be as it is in the ITU guidelines, rather than in the form. +//// + +//// +Free of Charge:: The words "Free of Charge" do not mean that the Patent Holder is waiving all of its rights with respect to the Patent. Rather, "Free of Charge" refers to the issue of monetary compensation; i.e., that the Patent Holder will not seek any monetary compensation as part of the licensing arrangement (whether such compensation is called a royalty, a one-time licensing fee, etc.). However, while the Patent Holder in this situation is committing to not charging any monetary amount, the Patent Holder is still entitled to require that the implementer of the same above document sign a license agreement that contains other reasonable terms and conditions such as those relating to governing law, field of use, warranties, etc. + +Reciprocity:: The word "Reciprocity" means that the Patent Holder shall only be required to license any prospective licensee if such prospective licensee will commit to license its Patent(s) for implementation of the same above document Free of Charge or under reasonable terms and conditions. + +Patent:: The word "Patent" means those claims contained in and identified by patents, utility models and other similar statutory rights based on inventions (including applications for any of these) solely to the extent that any such claims are essential to the implementation of the same above document. Essential patents are patents that would be required to implement a specific deliverable. + +Assignment/transfer of Patent rights:: Licensing declarations made pursuant to Clause 2.1 or 2.2 of the Common Patent Policy for ITU-T/ITU-R/ISO/IEC shall be interpreted as encumbrances that bind all successors-in-interest as to the transferred Patents. Recognizing that this interpretation may not apply in all jurisdictions, any Patent Holder who has submitted a licensing declaration according to the Common Patent Policy - be it selected as option 1 or 2 on the Patent Declaration form - who transfers ownership of a Patent that is subject to such licensing declaration shall include appropriate provisions in the relevant transfer documents to ensure that, as to such transferred Patent, the licensing declaration is binding on the transferee and that the transferee will similarly include appropriate provisions in the event of future transfers with the goal of binding all successors-in-interest. +//// + +=== Patent Information + +Preferred but not required for options <> and <>. Required for <>. + +.Patent information form +[cols="1,1,1,1,1",options="header"] +|=== +|No. +|Status [granted/ pending] +|Country +|Granted patent number or application number (if pending) +|Title + +|1|||| +|2|||| +|3|||| +|4|||| +|5|||| +|6|||| +|7|||| +|8|||| +|9|||| +|10|||| + +|=== + +[ ] Check here if additional patent information is provided on additional pages. + +NOTE: For option <>, the additional minimum information that shall also be provided is listed in that option. + +=== Signature (include on final page only) + +Patent Holder:: +pass:[__________________________] + +Name of authorized person:: +pass:[__________________________] + +Title of authorized person:: +pass:[__________________________] + +Signature, Place, Date:: +pass:[__________________________] + + diff --git a/sources/directive-ipr-guidelines/sections/99-bibliography.adoc b/sources/directive-ipr-guidelines/sections/99-bibliography.adoc new file mode 100644 index 0000000..0f3d801 --- /dev/null +++ b/sources/directive-ipr-guidelines/sections/99-bibliography.adoc @@ -0,0 +1,3 @@ + +[bibliography] +== Bibliography diff --git a/sources/directive-ipr-policy/document.adoc b/sources/directive-ipr-policy/document.adoc new file mode 100644 index 0000000..b54c46a --- /dev/null +++ b/sources/directive-ipr-policy/document.adoc @@ -0,0 +1,29 @@ += ELF Directive: Intellectual property rights policy +:title-main-en: ELF Directive: Intellectual property rights policy +:docnumber: 105 +:edition: 1 +:copyright-year: 2026 +:revdate: 2026-08-30 +:language: en +:doctype: standard +:technical-committee: TCB +:imagesdir: images +:mn-document-class: elf +:mn-output-extensions: xml,html,doc,pdf,rxl +:docidentifier: ELF 105:2026 +:data-uri-image: +:local-cache-only: + +include::sections/00-foreword.adoc[] + +include::sections/00-intro.adoc[] + +include::sections/01-scope.adoc[] +include::sections/02-normrefs.adoc[] +include::sections/03-terms.adoc[] +include::sections/04-activities.adoc[] +include::sections/05-contributions.adoc[] +include::sections/06-trademarks.adoc[] +include::sections/07-software.adoc[] + +include::sections/99-bibliography.adoc[] diff --git a/sources/directive-ipr-policy/reference-docs/ietf.txt b/sources/directive-ipr-policy/reference-docs/ietf.txt new file mode 100644 index 0000000..66c3a78 --- /dev/null +++ b/sources/directive-ipr-policy/reference-docs/ietf.txt @@ -0,0 +1,218 @@ +10. INTELLECTUAL PROPERTY RIGHTS + +10.1. General Policy + + In all matters of intellectual property rights and procedures, the + intention is to benefit the Internet community and the public at + large, while respecting the legitimate rights of others. + +10.2 Confidentiality Obligations + + No contribution that is subject to any requirement of confidentiality + or any restriction on its dissemination may be considered in any part + of the Internet Standards Process, and there must be no assumption of + any confidentiality obligation with respect to any such contribution. + +10.3. Rights and Permissions + + In the course of standards work, the IETF receives contributions in + various forms and from many persons. To best facilitate the + dissemination of these contributions, it is necessary to understand + any intellectual property rights (IPR) relating to the contributions. + +10.3.1. All Contributions + + By submission of a contribution, each person actually submitting the + contribution is deemed to agree to the following terms and conditions + on his own behalf, on behalf of the organization (if any) he + represents and on behalf of the owners of any propriety rights in the + contribution.. Where a submission identifies contributors in + addition to the contributor(s) who provide the actual submission, the + actual submitter(s) represent that each other named contributor was + made aware of and agreed to accept the same terms and conditions on + his own behalf, on behalf of any organization he may represent and + any known owner of any proprietary rights in the contribution. + + l. Some works (e.g. works of the U.S. Government) are not subject to + copyright. However, to the extent that the submission is or may + be subject to copyright, the contributor, the organization he + represents (if any) and the owners of any proprietary rights in + the contribution, grant an unlimited perpetual, non-exclusive, + royalty-free, world-wide right and license to the ISOC and the + IETF under any copyrights in the contribution. This license + includes the right to copy, publish and distribute the + contribution in any way, and to prepare derivative works that are + based on or incorporate all or part of the contribution, the + license to such derivative works to be of the same scope as the + license of the original contribution. + + 2. The contributor acknowledges that the ISOC and IETF have no duty + to publish or otherwise use or disseminate any contribution. + + 3. The contributor grants permission to reference the name(s) and + address(es) of the contributor(s) and of the organization(s) he + represents (if any). + + 4. The contributor represents that contribution properly acknowledge + major contributors. + + 5. The contribuitor, the organization (if any) he represents and the + owners of any proprietary rights in the contribution, agree that + no information in the contribution is confidential and that the + ISOC and its affiliated organizations may freely disclose any + information in the contribution. + + 6. The contributor represents that he has disclosed the existence of + any proprietary or intellectual property rights in the + contribution that are reasonably and personally known to the + contributor. The contributor does not represent that he + personally knows of all potentially pertinent proprietary and + intellectual property rights owned or claimed by the organization + he represents (if any) or third parties. + + 7. The contributor represents that there are no limits to the + contributor's ability to make the grants acknowledgments and + agreements above that are reasonably and personally known to the + contributor. + + By ratifying this description of the IETF process the Internet + Society warrants that it will not inhibit the traditional open and + free access to IETF documents for which license and right have + been assigned according to the procedures set forth in this + section, including Internet-Drafts and RFCs. This warrant is + perpetual and will not be revoked by the Internet Society or its + successors or assigns. + +10.3.2. Standards Track Documents + + (A) Where any patents, patent applications, or other proprietary + rights are known, or claimed, with respect to any specification on + the standards track, and brought to the attention of the IESG, the + IESG shall not advance the specification without including in the + document a note indicating the existence of such rights, or + claimed rights. Where implementations are required before + advancement of a specification, only implementations that have, by + statement of the implementors, taken adequate steps to comply with + any such rights, or claimed rights, shall be considered for the + purpose of showing the adequacy of the specification. + (B) The IESG disclaims any responsibility for identifying the + existence of or for evaluating the applicability of any claimed + copyrights, patents, patent applications, or other rights in the + fulfilling of the its obligations under (A), and will take no + position on the validity or scope of any such rights. + + + + +Bradner Best Current Practice [Page 30] + +RFC 2026 Internet Standards Process October 1996 + + + (C) Where the IESG knows of rights, or claimed rights under (A), the + IETF Executive Director shall attempt to obtain from the claimant + of such rights, a written assurance that upon approval by the IESG + of the relevant Internet standards track specification(s), any + party will be able to obtain the right to implement, use and + distribute the technology or works when implementing, using or + distributing technology based upon the specific specification(s) + under openly specified, reasonable, non-discriminatory terms. + The Working Group proposing the use of the technology with respect + to which the proprietary rights are claimed may assist the IETF + Executive Director in this effort. The results of this procedure + shall not affect advancement of a specification along the + standards track, except that the IESG may defer approval where a + delay may facilitate the obtaining of such assurances. The + results will, however, be recorded by the IETF Executive Director, + and made available. The IESG may also direct that a summary of + the results be included in any RFC published containing the + specification. + +10.3.3 Determination of Reasonable and Non-discriminatory Terms + + The IESG will not make any explicit determination that the assurance + of reasonable and non-discriminatory terms for the use of a + technology has been fulfilled in practice. It will instead use the + normal requirements for the advancement of Internet Standards to + verify that the terms for use are reasonable. If the two unrelated + implementations of the specification that are required to advance + from Proposed Standard to Draft Standard have been produced by + different organizations or individuals or if the "significant + implementation and successful operational experience" required to + advance from Draft Standard to Standard has been achieved the + assumption is that the terms must be reasonable and to some degree, + non-discriminatory. This assumption may be challenged during the + Last-Call period. + +10.4. Notices + + (A) Standards track documents shall include the following notice: + + "The IETF takes no position regarding the validity or scope of + any intellectual property or other rights that might be claimed + to pertain to the implementation or use of the technology + described in this document or the extent to which any license + under such rights might or might not be available; neither does + it represent that it has made any effort to identify any such + rights. Information on the IETF's procedures with respect to + rights in standards-track and standards-related documentation + can be found in BCP-11. Copies of claims of rights made + available for publication and any assurances of licenses to + be made available, or the result of an attempt made + to obtain a general license or permission for the use of such + proprietary rights by implementors or users of this + specification can be obtained from the IETF Secretariat." + + (B) The IETF encourages all interested parties to bring to its + attention, at the earliest possible time, the existence of any + intellectual property rights pertaining to Internet Standards. + For this purpose, each standards document shall include the + following invitation: + + "The IETF invites any interested party to bring to its + attention any copyrights, patents or patent applications, or + other proprietary rights which may cover technology that may be + required to practice this standard. Please address the + information to the IETF Executive Director." + + (C) The following copyright notice and disclaimer shall be included + in all ISOC standards-related documentation: + + "Copyright (C) The Internet Society (date). All Rights + Reserved. + + This document and translations of it may be copied and + furnished to others, and derivative works that comment on or + otherwise explain it or assist in its implmentation may be + prepared, copied, published and distributed, in whole or in + part, without restriction of any kind, provided that the above + copyright notice and this paragraph are included on all such + copies and derivative works. However, this document itself may + not be modified in any way, such as by removing the copyright + notice or references to the Internet Society or other Internet + organizations, except as needed for the purpose of developing + Internet standards in which case the procedures for copyrights + defined in the Internet Standards process must be followed, or + as required to translate it into languages other than English. + + The limited permissions granted above are perpetual and will + not be revoked by the Internet Society or its successors or + assigns. + + This document and the information contained herein is provided + on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET + ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR + IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE + OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY + IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A + PARTICULAR PURPOSE." + + (D) Where the IESG is aware at the time of publication of + proprietary rights claimed with respect to a standards track + document, or the technology described or referenced therein, such + document shall contain the following notice: + + "The IETF has been notified of intellectual property rights + claimed in regard to some or all of the specification contained + in this document. For more information consult the online list + of claimed rights." diff --git a/sources/directive-ipr-policy/reference-docs/itu-software-copyright-guidelines.pdf b/sources/directive-ipr-policy/reference-docs/itu-software-copyright-guidelines.pdf new file mode 100644 index 0000000..2ff0d4c Binary files /dev/null and b/sources/directive-ipr-policy/reference-docs/itu-software-copyright-guidelines.pdf differ diff --git a/sources/directive-ipr-policy/reference-docs/itu-trademark-guidelines.doc b/sources/directive-ipr-policy/reference-docs/itu-trademark-guidelines.doc new file mode 100644 index 0000000..55d0f7a Binary files /dev/null and b/sources/directive-ipr-policy/reference-docs/itu-trademark-guidelines.doc differ diff --git a/sources/directive-ipr-policy/sections/00-foreword.adoc b/sources/directive-ipr-policy/sections/00-foreword.adoc new file mode 100644 index 0000000..b3dc799 --- /dev/null +++ b/sources/directive-ipr-policy/sections/00-foreword.adoc @@ -0,0 +1,27 @@ +.Foreword +The EXPRESS Language Foundation ("`ELF`") is a registered public charity in the +US that facilitates the education, standardization, research, promotion, +definition, and usage of information modelling and programming languages, with a +focus on the EXPRESS language family. + +ELF works with international partners and experts across the globe, reflecting +the international nature of its mission. More information about ELF is available +on the official website (https://www.expresslang.org). + +The procedures used to develop this document and those intended for its further +maintenance are described in the ELF Directives. + +In particular the different approval criteria needed for the different types of +ELF documents should be noted. This document was drafted in accordance with the +editorial rules of the ELF Directives. + +Attention is drawn to the possibility that some of the elements of this +document may be the subject of patent rights. ELF shall not be held responsible +for identifying any or all such patent rights. Details of any patent rights +identified during the development of the document will be provided in the +Introduction. + +Any trade name used in this document is information given for the convenience of +users and does not constitute an endorsement. + +This document was prepared by the Technical Coordination Board (TCB). diff --git a/sources/directive-ipr-policy/sections/00-intro.adoc b/sources/directive-ipr-policy/sections/00-intro.adoc new file mode 100644 index 0000000..b1f7aeb --- /dev/null +++ b/sources/directive-ipr-policy/sections/00-intro.adoc @@ -0,0 +1,43 @@ +== Introduction + +=== General + +ELF is committed to expanding the realm of standards for information +modelling and programming languages, with a focus on the EXPRESS +language family and interoperability across the globe and communities +of practice. + +In the ELF standardization process described in <>, +contributions are received from various forms and parties. +As a proponent of open standards, ELF is required to +address any intellectual property rights in such contributions +to be able to publish standardization deliverables. + +This document details the IPR policy of ELF covering +all ELF standardization activities, covering +generally the following categories: + +* Copyright +* Trademarks +* Patents + + + + +=== Purpose + +This document describes the intellectual property rights policy of +ELF that aims to be simple and straightforward. + +ELF deliverables are drawn up by technical, not IPR, experts, +who may not be fully aware of all nuances in the complex +international legal situation of intellectual property rights. + +ELF deliverables are non-binding -- their objective is to ensure +compatibility of technologies and systems on a worldwide basis. + +To ensure the applicability and accessibility of ELF +deliverables, the implementation and continued usage of content within +the deliverables must be possible to the worldwide audience without +discrimination, including any intellectual property rights embodiment +in such deliverables. diff --git a/sources/directive-ipr-policy/sections/01-scope.adoc b/sources/directive-ipr-policy/sections/01-scope.adoc new file mode 100644 index 0000000..2f2a378 --- /dev/null +++ b/sources/directive-ipr-policy/sections/01-scope.adoc @@ -0,0 +1,6 @@ +== Scope + +This document provides the ELF intellectual property rights +policy, which governs all standardization activities at ELF. + +The ELF patent policy is described in <>. diff --git a/sources/directive-ipr-policy/sections/02-normrefs.adoc b/sources/directive-ipr-policy/sections/02-normrefs.adoc new file mode 100644 index 0000000..6686c15 --- /dev/null +++ b/sources/directive-ipr-policy/sections/02-normrefs.adoc @@ -0,0 +1,6 @@ +[bibliography] +== Normative References + +* [[[DIR101,ELF 101:2026]]], _ELF Directive: Standardization and publication_ + +* [[[DIR103,ELF 103:2026]]], _ELF Directive: Patent policy_ diff --git a/sources/directive-ipr-policy/sections/03-terms.adoc b/sources/directive-ipr-policy/sections/03-terms.adoc new file mode 100644 index 0000000..8f79280 --- /dev/null +++ b/sources/directive-ipr-policy/sections/03-terms.adoc @@ -0,0 +1,16 @@ +[source="DIR101"] + +[[terms]] +== Terms and definitions + +[[term-contribution]] +=== contribution + +material provided as input to an ELF standardization activity + +NOTE: a contribution can be provided by a member of ELF or an external party + + +=== contributor + +party that provides a _contribution_ (<>) diff --git a/sources/directive-ipr-policy/sections/04-activities.adoc b/sources/directive-ipr-policy/sections/04-activities.adoc new file mode 100644 index 0000000..e8d0f0e --- /dev/null +++ b/sources/directive-ipr-policy/sections/04-activities.adoc @@ -0,0 +1,18 @@ +[[standardization-activities]] +== Standardization activities + +[[confidentiality]] +=== No confidential material + +No confidential material is to be discussed at or during ELF standardization activities. + +All information provided or discussed in ELF activities is presumed to be public information and member participants are reminded that they should not discuss or reveal any confidential information of their respective organizations. + +While work in progress within ELF is not publicly available outside ELF, with minor exceptions, completed work products of ELF are intended to be publicly and freely available, and will be posted on the ELF web site. + + +=== Mandatory disclosure of intellectual property rights + +Discussions that relate to known or potential intellectual property rights during ELF standardization activities must be performed under full disclosure of such rights. + +Individuals participating in the activities of ELF are responsible for determining that such rights when known, must be disclosed in accordance with this provision. diff --git a/sources/directive-ipr-policy/sections/05-contributions.adoc b/sources/directive-ipr-policy/sections/05-contributions.adoc new file mode 100644 index 0000000..657cf12 --- /dev/null +++ b/sources/directive-ipr-policy/sections/05-contributions.adoc @@ -0,0 +1,119 @@ +[[contributions]] +== Contributions + + +=== No confidential material + +Participants in ELF standardization activities must avoid providing contributions containing confidential material, regardless whether provided in person or via electronic means. + + +=== Mandatory disclosure of intellectual property rights + +Contributions which contain intellectual property of an organization must be disclosed and are subject to the rules and guidance provided in this document. + +Such contributions shall be avoided unless such material can be shown to be, in the judgment of the participants in the activity and the ELF Board of Directors, essential to the work. + +No material which is subject to any terms of confidentiality or restriction of dissemination on the part of its contributor or the contributor's organization can be accepted for such use. + +Individuals participating in the activities of ELF are responsible for determining that material which they contribute is made available by their organizations in accordance with this provision. + + +=== Copyright provisions + +If any part of a contribution is or may be subject to copyright, the contributor and his or her organization, and any other owners of any proprietary rights in the contribution, grant ELF a world-wide, non-exclusive, non-sub-licensable license (except for the submission and adoption by other standardization bodies), to use contents of submitted documents to ELF, for the development and publishing of the deliverables. + +//// +Previous: +grant an unlimited perpetual, non-exclusive, royalty-free, world-wide right and license to The Calendaring and Scheduling Consortium under any copyrights in the contribution. +//// + +This license includes the right to copy, publish and distribute the contribution in any way, and to prepare derivative works that are based on or incorporate all or part of the contribution, the license to such derivative works to be of the same scope as the license of the original contribution. + +NOTE: This is in alignment with <>. + +//// +IETF RFC 2026 10.3.1.1 + + 1. Some works (e.g. works of the U.S. Government) are not subject to + copyright. However, to the extent that the submission is or may be + subject to copyright, the contributor, the organization he + represents (if any) and the owners of any proprietary rights in the + contribution, grant an unlimited perpetual, non-exclusive, + royalty-free, world-wide right and license to the ISOC and the + IETF under any copyrights in the contribution. This license + includes the right to copy, publish and distribute the + contribution in any way, and to prepare derivative works that are + based on or incorporate all or part of the contribution, the + license to such derivative works to be of the same scope as the + license of the original contribution. +//// + +=== Admission and usage + +ELF has no duty to admit, publish or otherwise use or disseminate any contribution. + +NOTE: This is in alignment with <>. + + +=== Reference + +The contributor grants permission to reference the names and +addresses of contributors of a contribution and of the organizations he or she +represents (if any). + +NOTE: This is in alignment with <>. + + +=== Source disclosure + +A contribution must properly acknowledge all major contributors of that contribution. + +NOTE: This is in alignment with <>. + + + +=== IPR disclosure + +The contributor when submitting a contribution, represents +that he or she has disclosed the existence of +any proprietary or intellectual property rights in the +contribution that are reasonably and personally known to the +contributor. + +The contributor does not represent that he or she +personally knows of all potentially pertinent proprietary and +intellectual property rights owned or claimed by the organization +he represents (if any) or third parties. + +For patents, please refer to the ELF Patent Policy at <>. + + +NOTE: This is in alignment with <> and <>. + + +=== Warranty + +The contributor is deemed to agree to the terms and conditions +set in this document when submitting a contribution. + +The contributor represents that there are no limits to the +contributor's ability to make the grants acknowledgments and +agreements detailed in this document that are reasonably and personally known to the +contributor. + +This agreement is made on his or her own behalf, on behalf of the organization (if any), +or on behalf of the owners of any propriety rights in the +contribution. + +Where a contribution identifies contributors in +addition to the contributor(s) who provided it, the +submitter(s) represent that each other named contributor was +made aware of and agreed to accept the same terms and conditions on +his own behalf, on behalf of any organization he may represent and +any known owner of any proprietary rights in the contribution. + +This warrant is perpetual and will not be revoked by ELF or its +successors or assigns. + + +NOTE: This is in alignment with <>. diff --git a/sources/directive-ipr-policy/sections/06-trademarks.adoc b/sources/directive-ipr-policy/sections/06-trademarks.adoc new file mode 100644 index 0000000..038b04c --- /dev/null +++ b/sources/directive-ipr-policy/sections/06-trademarks.adoc @@ -0,0 +1,73 @@ +== Trademarks + +=== General + +The requirements listed in this clause aligns with <>. + + +=== Impartiality of deliverables + +Proper names, trademarks, service marks or certification marks of specific companies/organizations, products or services should not be included in the text of an ELF standardization deliverable if it appears that they might cause any endorsement effect on a reader of the deliverable. + +NOTE: ELF standardization deliverables generally provide a description +of features from which interoperable implementations can be developed. +As such, the appearance of an endorsement of products, services and +companies/organizations are not acceptable. + +=== Non-endorsement usage + +Trademarks, service marks or certification marks may be included in an +ELF standardization deliverable in order to describe certain technologies or services pertaining to the relevant marks, given that the inclusion does not cause appearance of an endorsement. + +Here are some situations where this usage is acceptable. + +. The mark is used to refer to a particular facility that is widely recognized as a sole authorized source. + +[example] +A reference to a proprietary service with a trademark associated with a specific protocol identifier allocated by the ITU-T or IANA. + +. The mark is contained in the designation of a reference. + +[example] +Standards bodies often include their name as part of the identifier of their standards. A deliverable may reference "`ISO/IEC xxxx`", "`ITU-T xxxx`", where "`ISO`", "`IEC`" and "`ITU-T`" are protected marks. + +. The mark is a well-known reference to a standardized industry approach. + +[example] +"`WiFi`", "`Bluetooth`", "`GSM`". + + +=== Proper use references + +With justifiable reasons, it is permissible to make "`proper use`" +references to marks owned by an external party in an +ELF standardization deliverable, however the usage +shall adhere to the following guidelines set below in order to +avoid infringement of rights relating to such marks. + +A mark shall only be used as part of accurate, factual statements +as a means to identify (but not to endorse) a particular object (such as the designations of referenced standards in the text of a deliverable). + +Marks should be used in accordance with the following guidelines: + +. a mark should be used as a proper adjective followed by a generic name or noun; + ++ +NOTE: Marks are proper adjectives that indicate the source of goods, services or things, and not to be used as a verb or noun. + +. marks must not be combined in text; + +. marks must not be altered, shortened or abbreviated. + +//// +[example] +Example: Incorrect: “This protocol can be used for transport over WiMax and WiFi.” Correct: “This protocol can be used for transport over WiMax infrastructure and WiFi infrastructure.” +//// + + +//// +[example] +Example: Incorrect: “This protocol can be used for transport over WiMax/WiFi infrastructure.” Correct: “This protocol can be used for transport over WiMax infrastructure and WiFi infrastructure.” +//// + + +//// +[example] +Incorrect: “This specification supports the use of an AP Services Router.” Correct: “This specification supports the use of an Access Point Services Router.” +//// diff --git a/sources/directive-ipr-policy/sections/07-software.adoc b/sources/directive-ipr-policy/sections/07-software.adoc new file mode 100644 index 0000000..e3b6f84 --- /dev/null +++ b/sources/directive-ipr-policy/sections/07-software.adoc @@ -0,0 +1,23 @@ +[[software]] +== Software + +=== General + +In situations where software is included in ELF standardization deliverables, +the following rules must be adhered to. + +=== Source code contributions + +Software contributions included in a standardization deliverable must have +its source code made available free of charge and not require implementers to be +subject to a third-party license that does not meet the software licensing +requirements set forth in this clause. + +The license of a software contribution shall permit use, modification and +redistribution of the software for any purpose, including in derivative +works, without discrimination. + +The copyright notice and the applicable license of the software shall be +clearly identified in the deliverable. + +NOTE: This is in alignment with <>. diff --git a/sources/directive-ipr-policy/sections/99-bibliography.adoc b/sources/directive-ipr-policy/sections/99-bibliography.adoc new file mode 100644 index 0000000..b994524 --- /dev/null +++ b/sources/directive-ipr-policy/sections/99-bibliography.adoc @@ -0,0 +1,10 @@ +[bibliography] +== Bibliography + +* [[[DIR102,ELF 102:2026]]], _ELF Directive: Standard document requirements_ + +* [[[IETFRFC2026,IETF RFC 2026]]], _IETF RFC 2026: Internet Standards Process_ + +* [[[ITUMARKS,ITU-T Marks Guidelines 2.0]]], _ITU-T GUIDELINES RELATED TO THE INCLUSION OF MARKS IN ITU-T RECOMMENDATIONS, Issue 2.0_, November 2005. + +* [[[ITUSoftware,ITU Software Copyright Guidelines]]], _ITU Software Copyright Guidelines_, 7/12/2011 diff --git a/sources/directive-patent-policy/document.adoc b/sources/directive-patent-policy/document.adoc new file mode 100644 index 0000000..75dfc39 --- /dev/null +++ b/sources/directive-patent-policy/document.adoc @@ -0,0 +1,27 @@ += ELF Directive: Patent policy +:title-main-en: ELF Directive: Patent policy +:docnumber: 103 +:edition: 1 +:copyright-year: 2026 +:revdate: 2026-08-30 +:language: en +:doctype: standard +:technical-committee: TCB +:imagesdir: images +:mn-document-class: elf +:mn-output-extensions: xml,html,doc,pdf,rxl +:docidentifier: ELF 103:2026 +:data-uri-image: +:local-cache-only: + +include::sections/00-foreword.adoc[] +include::sections/00-intro.adoc[] + +include::sections/01-scope.adoc[] +include::sections/02-normrefs.adoc[] +include::sections/03-terms.adoc[] +include::sections/04-policy.adoc[] +include::sections/05-licensing.adoc[] +include::sections/06-declaration.adoc[] + +include::sections/99-bibliography.adoc[] diff --git a/sources/directive-patent-policy/reference-docs/ITU-T_ITU-R_ISO_IEC_Common_Guidelines_2015-06-26.pdf b/sources/directive-patent-policy/reference-docs/ITU-T_ITU-R_ISO_IEC_Common_Guidelines_2015-06-26.pdf new file mode 100644 index 0000000..900b9f4 Binary files /dev/null and b/sources/directive-patent-policy/reference-docs/ITU-T_ITU-R_ISO_IEC_Common_Guidelines_2015-06-26.pdf differ diff --git a/sources/directive-patent-policy/reference-docs/Patent-Policy-Common_Guidelines2012.pdf b/sources/directive-patent-policy/reference-docs/Patent-Policy-Common_Guidelines2012.pdf new file mode 100644 index 0000000..ddec3e8 Binary files /dev/null and b/sources/directive-patent-policy/reference-docs/Patent-Policy-Common_Guidelines2012.pdf differ diff --git a/sources/directive-patent-policy/reference-docs/iso-patent-form.adoc b/sources/directive-patent-policy/reference-docs/iso-patent-form.adoc new file mode 100644 index 0000000..8dd01eb --- /dev/null +++ b/sources/directive-patent-policy/reference-docs/iso-patent-form.adoc @@ -0,0 +1,43 @@ +Patent Holder: +Legal Name +Contact for license application: +Name & Department +Address + +Tel. +Fax +E mail +URL (optional) +Document type: ITU-T Rec. (*) ITU-R Rec. (*) ISO Deliverable (*) IEC Deliverable (*) +(please return the form to the relevant Organization) + +Common text or twin text (ITU-T Rec. | ISO/IEC Deliverable (*)) (for common text or twin text, please return the form to each of the three Organizations: ITU-T, ISO, IEC) +ISO/IEC Deliverable (*) (for ISO/IEC Deliverables, please return the form to both ISO and IEC) + +(*)Number + +(*)Title + +Licensing declaration: + +The Patent Holder believes that it holds granted and/or pending applications for Patents, the use of which would be required to implement the above document and hereby declares, in accordance with the Common Patent Policy for ITU-T/ITU-R/ISO/IEC, that (check one box only): + +1. The Patent Holder is prepared to grant a Free of Charge license to an unrestricted number of applicants on a worldwide, non-discriminatory basis and under other reasonable terms and conditions to make, use, and sell implementations of the above document. + +Negotiations are left to the parties concerned and are performed outside the ITU-T, ITU-R, ISO or IEC. + +Also mark here __ if the Patent Holder's willingness to license is conditioned on Reciprocity for the above document. + +Also mark here __ if the Patent Holder reserves the right to license on reasonable terms and conditions (but not Free of Charge) to applicants who are only willing to license their Patent, whose use would be required to implement the above document, on reasonable terms and conditions (but not Free of Charge). + + +2. The Patent Holder is prepared to grant a license to an unrestricted number of applicants on a worldwide, non-discriminatory basis and on reasonable terms and conditions to make, use and sell implementations of the above document. +Negotiations are left to the parties concerned and are performed outside the ITU-T, ITU-R, ISO, or IEC. + +Also mark here __ if the Patent Holder's willingness to license is conditioned on Reciprocity for the above document. + +3. The Patent Holder is unwilling to grant licenses in accordance with provisions of either 1 or 2 above. +In this case, the following information must be provided to ITU, and is strongly desired by ISO and IEC, as part of this declaration: +- granted patent number or patent application number (if pending); +- an indication of which portions of the above document are affected; +- a description of the Patents covering the above document. diff --git a/sources/directive-patent-policy/reference-docs/iso-patent-policy.adoc b/sources/directive-patent-policy/reference-docs/iso-patent-policy.adoc new file mode 100644 index 0000000..f40833f --- /dev/null +++ b/sources/directive-patent-policy/reference-docs/iso-patent-policy.adoc @@ -0,0 +1,34 @@ +== ISO/IEC/ITU common patent policy + +The following is a "code of practice" regarding patents covering, in varying degrees, the subject matters of ITU-T Recommendations, ITU-R Recommendations, ISO deliverables and IEC deliverables (for the purpose of this document, ITU-T and ITU-R Recommendations are referred to as “Recommendations”, ISO deliverables and IEC deliverables are referred to as “Deliverables”). +The rules of the "code of practice" are simple and straightforward. Recommendations | Deliverables are drawn up by technical and not patent experts; thus, they may not necessarily be very familiar with the complex international legal situation of intellectual property rights such as patents, etc. + +Recommendations | Deliverables are non-binding; their objective is to ensure compatibility of technologies and systems on a worldwide basis. To meet this objective, which is in the common interests of all those participating, it must be ensured that Recommendations | Deliverables, their applications, use, etc. are accessible to everybody. + +It follows, therefore, that a patent embodied fully or partly in a Recommendation | Deliverable must be accessible to everybody without undue constraints. To meet this requirement in general is the sole objective of the code of practice. The detailed arrangements arising from patents (licensing, royalties, etc.) are left to the parties concerned, as these arrangements might differ from case to case. + +This code of practice may be summarized as follows: + +=== {blank} + +The ITU Telecommunication Standardization Bureau (TSB), the ITU Radiocommunication Bureau (BR) and the offices of the CEOs of ISO and IEC are not in a position to give authoritative or comprehensive information about evidence, validity or scope of patents or similar rights, but it is desirable that the fullest available information should be disclosed. Therefore, any party participating in the work of ITU, ISO or IEC should, from the outset, draw the attention of the Director of ITU-TSB, the Director of ITU-BR, or the offices of the CEOs of ISO or IEC, respectively, to any known patent or to any known pending patent application, either their own or of other organizations, although ITU, ISO or IEC are unable to verify the validity of any such information. + +=== {blank} + +If a Recommendation | Deliverable is developed and such information as referred to in paragraph 1 has been disclosed, three different situations may arise: + +==== {blank} + +The patent holder is willing to negotiate licences free of charge with other parties on a nondiscriminatory basis on reasonable terms and conditions. Such negotiations are left to the parties concerned and are performed outside ITU-T/ITU-R/ISO/IEC. + +==== {blank} + +The patent holder is willing to negotiate licences with other parties on a non-discriminatory basis on reasonable terms and conditions. Such negotiations are left to the parties concerned and are performed outside ITU-T/ITU-R/ISO/IEC. + +==== {blank} + +The patent holder is not willing to comply with the provisions of either paragraph 2.1 or paragraph 2.2; in such case, the Recommendation | Deliverable shall not include provisions depending on the patent. + +=== {blank} + +Whatever case applies (2.1, 2.2 or 2.3), the patent holder has to provide a written statement to be filed at ITU-TSB, ITU-BR or the offices of the CEOs of ISO or IEC, respectively, using the appropriate "Patent Statement and Licensing Declaration" Form. This statement must not include additional provisions, conditions, or any other exclusion clauses in excess of what is provided for each case in the corresponding boxes of the form. diff --git a/sources/directive-patent-policy/sections/00-foreword.adoc b/sources/directive-patent-policy/sections/00-foreword.adoc new file mode 100644 index 0000000..b3dc799 --- /dev/null +++ b/sources/directive-patent-policy/sections/00-foreword.adoc @@ -0,0 +1,27 @@ +.Foreword +The EXPRESS Language Foundation ("`ELF`") is a registered public charity in the +US that facilitates the education, standardization, research, promotion, +definition, and usage of information modelling and programming languages, with a +focus on the EXPRESS language family. + +ELF works with international partners and experts across the globe, reflecting +the international nature of its mission. More information about ELF is available +on the official website (https://www.expresslang.org). + +The procedures used to develop this document and those intended for its further +maintenance are described in the ELF Directives. + +In particular the different approval criteria needed for the different types of +ELF documents should be noted. This document was drafted in accordance with the +editorial rules of the ELF Directives. + +Attention is drawn to the possibility that some of the elements of this +document may be the subject of patent rights. ELF shall not be held responsible +for identifying any or all such patent rights. Details of any patent rights +identified during the development of the document will be provided in the +Introduction. + +Any trade name used in this document is information given for the convenience of +users and does not constitute an endorsement. + +This document was prepared by the Technical Coordination Board (TCB). diff --git a/sources/directive-patent-policy/sections/00-intro.adoc b/sources/directive-patent-policy/sections/00-intro.adoc new file mode 100644 index 0000000..08d6ebb --- /dev/null +++ b/sources/directive-patent-policy/sections/00-intro.adoc @@ -0,0 +1,32 @@ +== Introduction + +=== General + +ELF is committed to expanding the realm of standards for information +modelling and programming languages, with a focus on the EXPRESS +language family and interoperability across the globe and communities +of practice. + +As a proponent of open standards, ELF does not endorse +mandatory usage of patents within ELF Standards. +The ELF Board of Directors has decided to align +IPR practice with major international standardization bodies +including ISO, IEC and ITU. + +=== Purpose + +This document describes the policy of ELF with regards to patent +usage within ELF deliverables and provides a +"`code of practice`" that is simple and straightforward. + +ELF deliverables are drawn up by technical, not patent, experts, +who may not be fully aware of all nuances in the complex +international legal situation of intellectual property rights. + +ELF deliverables are non-binding -- their objective is to ensure +compatibility of technologies and systems on a worldwide basis. + +To ensure the applicability and accessibility of ELF +deliverables, the implementation and continued usage of content within +the deliverables must be possible to the worldwide audience without +discrimination, including any patent embodiment in such deliverables. diff --git a/sources/directive-patent-policy/sections/01-scope.adoc b/sources/directive-patent-policy/sections/01-scope.adoc new file mode 100644 index 0000000..1e89787 --- /dev/null +++ b/sources/directive-patent-policy/sections/01-scope.adoc @@ -0,0 +1,18 @@ +== Scope + +This document provides the ELF patent policy, which governs all +standardization deliverables developed through the ELF +standardization process. + +The ELF patent policy is identical to the <> in content, +except where: + +* entity names such as "`ISO`", "`IEC`", "`ITU-T`" and "`ITU-R`" were +changed to "`ELF`"; + +* deliverables and processes pertaining to those entities have been +changed to their counterparts within ELF. + +Detailed arrangements arising from patents (licensing, royalties, etc.) +are left to the parties concerned, as these arrangements might differ +from case to case. diff --git a/sources/directive-patent-policy/sections/02-normrefs.adoc b/sources/directive-patent-policy/sections/02-normrefs.adoc new file mode 100644 index 0000000..f8c1275 --- /dev/null +++ b/sources/directive-patent-policy/sections/02-normrefs.adoc @@ -0,0 +1,5 @@ + +[bibliography] +== Normative References + +* [[[ISOPP,ISO/IEC/ITU common patent policy]]], _ISO/IEC/ITU common patent policy_, https://isotc.iso.org/livelink/livelink/fetch/2000/2122/3770791/Common_Policy.htm diff --git a/sources/directive-patent-policy/sections/03-terms.adoc b/sources/directive-patent-policy/sections/03-terms.adoc new file mode 100644 index 0000000..a696ddd --- /dev/null +++ b/sources/directive-patent-policy/sections/03-terms.adoc @@ -0,0 +1,5 @@ + +[source="DIR101"] + +[[terms]] +== Terms and definitions diff --git a/sources/directive-patent-policy/sections/04-policy.adoc b/sources/directive-patent-policy/sections/04-policy.adoc new file mode 100644 index 0000000..46c5ebc --- /dev/null +++ b/sources/directive-patent-policy/sections/04-policy.adoc @@ -0,0 +1,18 @@ + +[[information-transparency]] +== Patent information transparency policy + +ELF does not provide authoritative or comprehensive information +about evidence, validity or scope of patents or similar rights. + +However, the fullest available information shall be disclosed in any ELF-published standard. + +Therefore, any party participating in the work of ELF shall, +from the outset, draw the attention of the Executive Director and TCB +of ELF, to any known patent or to any known pending patent +application, either their own or of other organizations, although +ELF is unable to verify the validity of any such information. + +In a joint deliverable developed with other standardization bodies, +IPR requirements of all such standardization bodies who will be +publishing the deliverable shall be satisfied. diff --git a/sources/directive-patent-policy/sections/05-licensing.adoc b/sources/directive-patent-policy/sections/05-licensing.adoc new file mode 100644 index 0000000..aed2421 --- /dev/null +++ b/sources/directive-patent-policy/sections/05-licensing.adoc @@ -0,0 +1,37 @@ + +[[licensing-requirements]] +== Licensing requirements on patent holders + +=== General + +If an ELF deliverable is developed and such information as +referred to in <> has been disclosed, +one of the following three situations may arise. + +[[license-free]] +=== Situation 1: Licensing free-of-charge + +The patent holder is willing to negotiate licences free of charge with +other parties on a nondiscriminatory basis on reasonable terms and +conditions. + +Such negotiations are left to the parties concerned and are performed +outside ELF. + +[[license-nd]] +=== Situation 2: Licensing in a non-discriminatory manner + +The patent holder is willing to negotiate licences with other parties +on a non-discriminatory basis on reasonable terms and conditions. + +Such negotiations are left to the parties concerned and are performed +outside ELF. + +[[license-other]] +=== Situation 3: Licensing in other manners + +The patent holder is not willing to comply with the provisions of +either <> or <>. + +In such case, the deliverable shall not include provisions that depends +on the patent. diff --git a/sources/directive-patent-policy/sections/06-declaration.adoc b/sources/directive-patent-policy/sections/06-declaration.adoc new file mode 100644 index 0000000..b926c40 --- /dev/null +++ b/sources/directive-patent-policy/sections/06-declaration.adoc @@ -0,0 +1,12 @@ + +[[declaration]] +== Patent declaration requirements + +Whatever the licensing requirements (<>) +are, the patent holder must provide a written statement to be +filed at ELF, using the appropriate +"`Patent Statement and Licensing Declaration`" Form. + +This statement must not include additional provisions, conditions, or +any other exclusion clauses in excess of what is provided for each case +in the corresponding boxes of the form. diff --git a/sources/directive-patent-policy/sections/99-bibliography.adoc b/sources/directive-patent-policy/sections/99-bibliography.adoc new file mode 100644 index 0000000..b2916a4 --- /dev/null +++ b/sources/directive-patent-policy/sections/99-bibliography.adoc @@ -0,0 +1,10 @@ +[bibliography] +== Bibliography + +* [[[DIR101,ELF 101:2026]]], _ELF Directive: Standardization and publication_ + +* [[[ISODIR1,ISO/IEC Directives, Part 1]]], _ISO/IEC Directives, Part 1, Procedures for the technical work_ + +* [[[ISODIR2,ISO/IEC Directives, Part 2]]], _ISO/IEC Directives, Part 2, Principles and rules for the structure and drafting of ISO and IEC documents_ + +* [[[ISODIR1C,ISO/IEC Directives, Part 1, Consolidated ISO Supplement]]], _ISO/IEC Directives, Part 1, Consolidated ISO Supplement, Procedures specific to ISO_ diff --git a/sources/directive-standardization/document.adoc b/sources/directive-standardization/document.adoc new file mode 100644 index 0000000..d858115 --- /dev/null +++ b/sources/directive-standardization/document.adoc @@ -0,0 +1,33 @@ += ELF Directive: Standardization and publication +:title-main-en: ELF Directive: Standardization and publication +:docnumber: 101 +:edition: 1 +:copyright-year: 2026 +:revdate: 2026-08-30 +:language: en +:doctype: standard +:technical-committee: TCB +:imagesdir: images +:mn-document-class: elf +:mn-output-extensions: xml,html,doc,pdf,rxl +:docidentifier: ELF 101:2026 +:data-uri-image: +:local-cache-only: + +include::sections/00-foreword.adoc[] + +include::sections/00-intro.adoc[] + +include::sections/01-scope.adoc[] +include::sections/02-normrefs.adoc[] +include::sections/03-terms.adoc[] +include::sections/04-authority.adoc[] +include::sections/05-document-types.adoc[] +include::sections/06-process.adoc[] +include::sections/07-public-review.adoc[] +include::sections/08-comments.adoc[] +include::sections/09-corrections.adoc[] +include::sections/10-ipr.adoc[] +include::sections/11-maintenance.adoc[] +include::sections/12-registration.adoc[] +include::sections/99-bibliography.adoc[] diff --git a/sources/directive-standardization/sections/00-foreword.adoc b/sources/directive-standardization/sections/00-foreword.adoc new file mode 100644 index 0000000..b3dc799 --- /dev/null +++ b/sources/directive-standardization/sections/00-foreword.adoc @@ -0,0 +1,27 @@ +.Foreword +The EXPRESS Language Foundation ("`ELF`") is a registered public charity in the +US that facilitates the education, standardization, research, promotion, +definition, and usage of information modelling and programming languages, with a +focus on the EXPRESS language family. + +ELF works with international partners and experts across the globe, reflecting +the international nature of its mission. More information about ELF is available +on the official website (https://www.expresslang.org). + +The procedures used to develop this document and those intended for its further +maintenance are described in the ELF Directives. + +In particular the different approval criteria needed for the different types of +ELF documents should be noted. This document was drafted in accordance with the +editorial rules of the ELF Directives. + +Attention is drawn to the possibility that some of the elements of this +document may be the subject of patent rights. ELF shall not be held responsible +for identifying any or all such patent rights. Details of any patent rights +identified during the development of the document will be provided in the +Introduction. + +Any trade name used in this document is information given for the convenience of +users and does not constitute an endorsement. + +This document was prepared by the Technical Coordination Board (TCB). diff --git a/sources/directive-standardization/sections/00-intro.adoc b/sources/directive-standardization/sections/00-intro.adoc new file mode 100644 index 0000000..20c1212 --- /dev/null +++ b/sources/directive-standardization/sections/00-intro.adoc @@ -0,0 +1,19 @@ +== Introduction + +ELF is committed to expanding the realm of open standards for information +modelling and programming languages across the globe and across communities +of practice. + +To facilitate its mission, the ELF Board of Directors has decided +to align standardization and publication processes with international +best practices, such as the ISO standardization process, and the +<>. +This document aims to achieve the said intention. + +The document describes the ELF standardization process, from +conception, IPR policy, technical committee establishment, collaboration +policies (liaisons), to the publishing of work items. + +Processes described in this document contain parts that relate +to all ELF technical committees and the TCB, which +carries responsibility of implementing these processes. diff --git a/sources/directive-standardization/sections/01-scope.adoc b/sources/directive-standardization/sections/01-scope.adoc new file mode 100644 index 0000000..3435e1e --- /dev/null +++ b/sources/directive-standardization/sections/01-scope.adoc @@ -0,0 +1,35 @@ +== Scope + +This document formalizes the standardization and publication processes +of ELF. + +Specifically, it describes the processes and requirements for the +standardization and publication of the following document types +produced by ELF, including: + +Directive:: normative document that provides requirements for +internal ELF processes + +Standard:: normative document that provide requirements, specifications or guidelines +for the public + +Guide:: informative internal document for ELF technical committees + +Specification:: informative specification for the public + +Report:: informative internal or public report + +Amendment:: normative document that amend a published ELF document + +Technical corrigendum:: document that describes a minor amendment +of a published ELF document, that does not affect the overall validity +of the original document + + +This document does not apply to the following types of documents +produced by ELF, although processes described in this document +can be optionally used as guidance for rigor: + +* policy statements; +* internal administrative documents; and +* how-to guides. diff --git a/sources/directive-standardization/sections/02-normrefs.adoc b/sources/directive-standardization/sections/02-normrefs.adoc new file mode 100644 index 0000000..fdf2274 --- /dev/null +++ b/sources/directive-standardization/sections/02-normrefs.adoc @@ -0,0 +1,5 @@ + +[bibliography] +== Normative References + +* [[[WTOTBTP,WTO TBT Principles]]], _,Annex 2: Decision of the Committee on Principles for the Development of International Standards, Guides and Recommendations with relation to Articles 2, 5 and Annex 3 of the Agreement; Decisions and recommendations adopted by the TBT Committee since 1 January 1995: Annexes to Part 1; _WTO Agreements Series: Technical Barriers to Trade_, World Trade Organization diff --git a/sources/directive-standardization/sections/03-terms.adoc b/sources/directive-standardization/sections/03-terms.adoc new file mode 100644 index 0000000..6bec096 --- /dev/null +++ b/sources/directive-standardization/sections/03-terms.adoc @@ -0,0 +1,116 @@ +//[source="ISODIR1,ISODIR1C,ISODIR2"] + +[[terms]] +== Terms, definitions and abbreviations + +=== Terms and definitions + +[[term-std-project]] +==== standardization project + +an organized process with one or more _standardization work items_ (<>) +that contributes towards a defined scope of work + +[[term-std-work-item]] +==== standardization work item + +publishable _document_ (<>) that relates to standardization + +[[term-project-owner]] +==== project owner + +entity with authority in charge of a _standardization project_ +(<>) + +[[term-document]] +==== document + +written output + +[[term-cc-deliverable]] +==== ELF deliverable + +_document_ (<>) that could be an ELF Standard, +Guide, Specification, Report + +[[term-iso-deliverable]] +==== ISO TC deliverable + +_document_ (<>) of an ISO TC as described in <> + +NOTE: According to <>, ISO TC deliverables include the following types: International Standards, Technical Specifications, Publicly Available Specifications and Technical Reports. + +[[term-cc-tc]] +==== ELF technical committee +alt:[ELF TC] + +internal committee of ELF tasked with a scope of work it +is responsible for + +==== document stage + +stage of document as specified in the ISO harmonized stages (as defined in <>) + +[[term-std-project-output]] +==== standardization project output + +output of a _standardization project_ (<>) + +NOTE: In this document, it explicitly means any documents and IP rights +produced by the standardization project. + +[[term-sdo]] +==== standardization body +alt:[standards-developing organization] +alt:[SDO] + +entity that publishes _standardization work items_ (<>) + + +[[term-std-proposal]] +==== proposal for standardization + +proposal for a new work item for standardization + +[[term-co-develop]] +==== co-develop +alt:[collaborative development] + +act of developing a work item by multiple parties from the proposal stage + +[[term-co-publish]] +==== co-publish +alt:[collaborative publishing] + +act of publishing _documents_ (<>) of identical content +by multiple parties + +==== joint work item + +work item _co-developed_ (<>) by both parties + + +==== joint publication + +publication that is _co-published_ (<>) by ELF with +an external _standardization body_ (<>) + +NOTE: Both parties may jointly hold copyright of the joint publication. + +[[term-board]] +==== ELF Board of Directors + +persons serving as a Board Director for and with a statutory obligation +to ELF + +[[term-repo]] +==== ELF Document Repository + +designated repository used to store ELF documents + + +=== Abbreviations + +IPR:: Intellectual Property Rights + +TCB:: Technical Coordination Board diff --git a/sources/directive-standardization/sections/04-authority.adoc b/sources/directive-standardization/sections/04-authority.adoc new file mode 100644 index 0000000..45ac2c8 --- /dev/null +++ b/sources/directive-standardization/sections/04-authority.adoc @@ -0,0 +1,39 @@ +[[authority]] +== Authority + +=== General + +The TCB is responsible for developing the corresponding processes +and tools, and for their employment. + +[[authority-tcb]] +=== Technical Coordination Board + +The TCB is responsible for: + +* policy development: providing recommendations to the Board of + Directors on the ELF standardization and publication processes; + +* policy establishment: developing and supporting process + documents, including: + +** this document; and +** ELF publication requirements; and + +* maintenance: periodic review and perform amendments necessary + to support the processes and requirements established in this + document; + +* execution: faithful execution and maintenance of the ELF + standardization process; + +* enforcement: enforcing ELF publication requirements on the publication + of ELF deliverables; + +* mediation: raising issues and problems encountered concerning the processes + and procedures described in this document to the Board of Directors for + further consideration; and + +* coordination: supporting liaisons between ELF technical committees and + project teams with corresponding parties of external standardization + bodies. diff --git a/sources/directive-standardization/sections/05-document-types.adoc b/sources/directive-standardization/sections/05-document-types.adoc new file mode 100644 index 0000000..659e739 --- /dev/null +++ b/sources/directive-standardization/sections/05-document-types.adoc @@ -0,0 +1,75 @@ +[[document-types]] +== Document types + +All documents must have at least one document type, or category. A +document may appear in more than one category, if appropriate. + +=== Directive + +Internal, normative documents approved by the ELF Board of Directors, +developed by the TCB, that provides requirements for +internal ELF processes. + + +=== Standard + +Normative documents created through the ELF standardization process +that provide requirements, specifications or guidelines for the public. + +Requirements in standards shall be based on objective performance +rather than based on descriptive characteristics. + + +=== Guide + +Informative, internal documents that describe guidelines for the work of +ELF technical committees. + +Often a document discussing problems or issues and making suggestions for +action. + + +=== Specification + +Informative specifications for the public. + +It could be an experimental specification intended for research and exploration, +such as to encourage trial implementations, to determine its usefulness and +applicability. + +A published Specification deemed successful would be candidates for progression +towards a Standard. + + +=== Amendment + +Normative documents that amend a published ELF document, such as a +Standard. + + +=== Technical corrigendum + +Document that describes a minor amendment of a published ELF +document, that does not affect the overall validity of the original +document. + +Could be a normative or informative document for public or +internal consumption. + + +=== Reports + +Informative document, reporting on an event or presenting findings +of a study or research effort, which may reach conclusions but does +not contain suggestions for action, except incidentally. + +Intended for internal or public consumption. + +[example] +A report on an ELF conference. + + +=== Administrative + +A document type for meeting minutes, proposals to committees, policy +documents, and other material, generally of an internal nature. diff --git a/sources/directive-standardization/sections/06-process.adoc b/sources/directive-standardization/sections/06-process.adoc new file mode 100644 index 0000000..00d5127 --- /dev/null +++ b/sources/directive-standardization/sections/06-process.adoc @@ -0,0 +1,540 @@ + +[[process]] +== Standardization process + +=== General + +Every ELF deliverable starts as a project. + +An ELF project goes through the following processes: + +* starts with a proposal; +* the proposal is given to the approving entity for enactment; +* assigns a committee as project owner once the project is approved; +* the committee creates one or more working drafts from the proposal; +* the committee decides to endorse a committee draft; +* the approved committee draft becomes a standards draft +* the draft standard is given to the approving entity for endorsement; +* the draft standard is approved for publication as a standard. + +//NOTE: TODO: joint publishing + +=== Project stages + +The following table provides a mapping between ELF project stages and +ISO project stages. This document identifies stages +according to the ELF project stage names. + +[cols="1,1,1,1,1",options="header"] +.Alignment between ISO and ELF project stages +|=== +|Stage identifier +|ELF stage +|ISO harmonized stage (<>) +|ELF deliverable +|ISO deliverable + +|*Preliminary* +|00 Preliminary +|00 Preliminary +|PWI +|PWI + +|*Proposal* +|10 Proposal +|10 Proposal +|NWIP +|NWIP + +|*Preparatory* +|20 Preparatory +|20 Preparatory +|WD +|WD + +|*Committee* +|30 Committee +|30 Committee +|CD +|CD + +|*Enquiry* +|40 Enquiry +|40 Enquiry +|DS +|DIS + +|*Approval* +|50 Approval +|50 Approval +|FDS +|FDIS + +|*Publication* +|60 Publication +|60 Publication +|ES +|IS + +|*Review* +|90 Review +|90 Review +| +| + +|*Withdrawal* +|95 Withdrawal +|95 Withdrawal +| +| + +|=== + + +=== Project track + +There is only one project track in ELF as considered by the TCB. + + +=== Project ownership + +==== General + +All ELF non-administrative documents must be owned by a single +Technical Committee (the "`owning`" Technical Committee) even if two +or more TCs participate in the work of developing the document. + + +==== Transition of ownership on TC retirement + +When a TC completes its scope of work and is shut down, the ownership +of its documents moves to the TCB. + +TCB may retain ownership of a document once assigned to it, or +it may assign the document to a different or new Technical Committee, +generally if follow-on work or maintenance is required on the document. + + +=== Project membership + +==== General + +The owning TC is responsible for maintaining expert membership of a +project group. + +ELF members are allowed to nominate experts to the project group +with approval of the owning TC. + +At least one person, at most two, serves as project leader, as decided +by the owning TC. + +The project leader(s) shall assume project editorship unless that +activity is specifically assigned to another individual. + + +==== External members + +Individuals who are not members of ELF are only allowed to participate in +a project if specifically authorized by the project owning TC, in consultation +with the project leader, and approved by the TCB. + + +=== Project stages + + +==== Preliminary stage + +===== Initiation methods + +A standardization project can be initiated in one of the following ways: + +. a project defined as part of the charter process of a TC; + +. a TC decides to create a new project as an addition to its program of work; + +. the TCB or the Board of Directors decides that a project should +be initiated and assigns it to a Technical Committee. + + +===== Initiation requirements + +When a project is initiated, the following items must be defined +by the proposer as part of the proposal to the TCB: + +. scope + +. target audience + +. relevant regulatory or market needs (as feasible and appropriate) + (this satisfies <>) + +. current scientific and technological developments + (this satisfies <>) + +. schedule for development and publication + +. proposer, project leader + +All documents other than administrative documents must have an editor +or editors who are members of the Technical Committee(s) developing the +document. + + + +===== Confirmation + +Once a project is confirmed initiation: + +. the project shall be assigned a project number as decided by the TCB; + +. the project's name and stage shall be listed in the project registry + (this satisfies <>); and + +. the project will be announced by the TCB to all members with a + brief description of its scope (including objective and rationale) + at an early enough stage that facilitates amendments and comments + (this satisfies <>). + +NOTE: This document supports the creation of a project registry. + + +===== First draft + +A first draft of the standardization deliverable may be created +for proposal submission, or may be created in the Committee stage. + +Disclaimers and necessary statements such as relating to IPR and +copyright shall be placed in an obvious place in the draft. + + +==== Proposal stage + +When the TCB determines interest within ELF to develop the +proposed project, the project initiator should submit a proposal +to the TCB for ballot indicating its wish to develop the proposed project. + +If accepted, the project shall be adopted by an ELF TC. +Members of the project group shall be represented by experts. +This project shall then be listed in the TCB register of projects. + +If rejected, its output may still be developed by one or more members +of ELF if appropriate, and the resulting output may still be +proposed to the TCB for development in later stages. + + +A "`Report`" document type shall be published upon a successful ballot +of two-thirds approval at this stage. + + +==== Preparatory stage + +This is an optional stage. + +The goal of the preparatory stage is to create a "`working draft`" +of the deliverable approved by the project group within the TC. + +Once the project team decides the working draft has advanced +to being a "`committee draft`" or a "`draft standard`", this +stage ends. + +There is no ballot at this stage. + + +==== Committee stage + +This is an optional stage. + +The goal of the committee stage is to create a "`committee draft`" +of the deliverable approved by the TC. + +The owning TC distributes the committee draft and may select a 8-week or 10-week +comment period for TC members to comment. + +Within 4 weeks of completion of the comment period, the owning TC shall distribute +all formal comments received during ballot to TC members. + +Given the results of comments, the Chair of the TC, considering TC consensus, +in consultation with the project leader (if necessary), +shall decide on the below outcomes: + +. to prepare and circulate a revised committee draft for consideration; or + +. to register the committee draft for the enquiry stage. + +In case TC consensus is unclear from the results, a ballot (<>) can be launched +to determine consensus for stage advancement. + +A "`Specification`" document type shall be published upon advancement +to the enquiry stage. + + +[[stage-enquiry]] +==== Enquiry stage + +The goal of the enquiry stage is to create a "`draft standard`" +of the deliverable approved by the TC. + +The public review period (<>) shall be started within +4 weeks of entering this stage. + +Once the owning TC deems a document under development to be +ready for publication, the Chair of the owning TC shall arrange +for an official ballot (<>) amongst TC members. +"`No`" votes must be accompanied with technical reasons. + +If no "`No`" votes were registered in the DIS ballot, +the project is deemed to have unanimous support. It shall be fast-tracked +towards the Approval stage for TCB ballot. + +If the ballot was successful but at least one "`No`" vote has been received, +the project is advanced to Approval stage. + +If the ballot failed, the Chair of the owning TC, in consultation +with the project leader to decide whether to prepare and circulate a revised +draft standard for re-balloting. + + +==== Approval stage + +The goal of the approval stage is to create a "`final draft standard`" +of the deliverable approved by the ELF membership. + +The public review period (<>) shall be started within +4 weeks of entering this stage, unless the document has already +been reviewed publicly at the Enquiry stage (<>). + +A "`last call`" for formal comments shall be issued by the Chair of +the owning TC to both the TCB and to the full ELF membership +of 8 weeks. + +The formal commenting process is described in detail at <>. + +After the close of the commenting period, the Chair of TCB shall +distribute the comments to the ELF membership within +4 weeks of the close, and conduct a 8-week ballot (<>) +of TCB members for a vote to approve publication. + +All TCB members are required to vote in this ballot. A TCB member +that did not vote in the TCB poll is considered to have violated +membership terms of the TCB, and has a 3-week period to rectify. + +"`No`" votes from a TCB member must be accompanied with constructive +comments. + +If the ballot was successful, the project is deemed to be ready for +publication and is advanced to the publication stage. + +If the ballot failed, the Chair of the owning TC, in consultation +with the project leader to decide whether to prepare and circulate a revised +final draft standard for re-balloting. + + +[[draft-stages]] +==== Draft development stages (Preparatory, Committee and Enquiry stages) + +. Each new draft version of the document as it is developed shall be +posted by the editor(s) on the ELF Document Repository. A +version is defined as a checkpoint where the developers want review +from individuals other than active contributors, typically at the +end of a development stage when the draft is a candidate for ballot. + +. The availability of each new draft version shall be announced +to all TCs and as appropriately, to external liaison or partner +working groups (this satisfies <>). + +. A draft version may be announced to the ELF membership +if ELF-wide comment is requested +(this satisfies <>). + +. A draft version may be posted for external review and +comments upon approval by TCB (see <>). +This is normally be done at the Enquiry and Approval stages, +where the draft is considered more mature for appropriate +external input. + +. Once initial approval is given by TCB, a draft may be posted +for external review and comment multiple times. + +In every of the development stages, resolution of all outstanding +comments is required to proceed towards ballot. + + + + + +[[pre-publication]] +==== Pre-publication stages (Enquiry and Approval stages) + +Once a "`draft standard`" or a "`final draft standard`" is approved +towards publication, a public review period ensues. + +The public review process is described in <>. + + + +==== Publication stage + +// TODO: + +===== Distribution + +Once TCB approves a document for publication, the Chair of the +owning TC shall forward the final draft standard to the +Executive Director of ELF for publication. + +A standard designated for public access will be distributed +on the ELF document register (this satisfies <>). + +Internal documents are made available only to members of ELF +via the members area of the ELF website, and are registered in +the ELF Internal Document Register. + +[[dual-logo]] +===== Dual-logo documents + +A dual-logo document is a deliverable co-published by ELF and an +external standardization body under the marks of both parties. + +For a dual-logo document, after the collaborating standardization +body accepts a joint work item for publication, the joint work item +will be published by ELF under the corresponding document type. + + +===== Statement changes + +The "`boilerplate`" statements of IP, appropriate usage and +disclaimer will be changed to the external (public) statement. + + +===== Registration at the public document register + +The name, category, version and project number of the deliverable +shall be registered in the ELF Public Document Register. + + + +=== Abandonment + +==== Abandonment of joint work items + +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 other party 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 other party to allow publication of the document. + +If the abandoning party wishes to rejoin an abandoned work item, it is +allowed, given a notice is filed with the TCB, unless in exceptional +circumstances. + + + + +[[process-balloting]] +=== Balloting + +A ballot is launched upon gauging consensus within a group +(TC, TCB or amongst all members). + +In each ballot, a member is allocated three options: + +* Yes +* No +* Abstain + +A "`No`" vote must be accompanied by constructive comments. "`Abstain`" votes +are not counted against the outcome. + +Consensus is considered to have been reached when there are two-thirds of "`Yes`" votes. + + + +[[appeals]] +=== Appeals + +An appeal may be raised by any affected party against a procedural +decision taken in the ELF standardization process, including decisions +taken by a technical committee or the TCB. + +An appeal shall be submitted in writing to the Executive Director +within 30 days of the decision being announced to the ELF membership +or published in the corresponding ELF document repository, stating +the decision appealed against and the grounds for the appeal. + +The Executive Director shall present the appeal to the Board of +Directors, which considers the appeal and decides upon it. + +Members of the Board of Directors who took part in the contested +decision shall not take part in deciding the appeal. + +The decision of the Board of Directors on an appeal is final. + + +=== Availability of working documents + +Drafts and working documents are available according to +each party's normal practices. + + + +=== Promotional activities in co-developed projects + +Promotional programs will be shared between the collaborating +parties for the purpose of coordinating marketing activities. + + + +=== External progression + +In some cases, ELF deliverables are sent to be progressed +at another standards body: + +* upon completion of the Approval stage, an ELF document may be sent + immediately to an external standardization body for progression + to become a standard; and + +* if a published ELF document is subsequently decided to + be forwarded to another standards body for progression. + +In these situations, the ELF document shall be accompanied by a +link at the ELF website, that provides the document at the target standards +body, completely with document number, title, etc. given by that +standards body. + +It is anticipated that such documents will be progressed and modified +according to the processes of the recipient standards body. ELF +shall attempt to ensure that the link remains valid, and if +possible for the most current version of the document. + + +[[liaisons]] +=== Liaisons and collaborative development + +ELF may co-develop and co-publish documents with external +standardization bodies. + +Such collaboration is governed by a collaboration agreement between +ELF and the collaborating party, which shall be approved by the +Board of Directors. + +For projects under a collaboration agreement, ELF agrees to adopt a +developmental track not slower than a corresponding track selected +by the external standardization body to ensure synchronicity between +development outcome and publication. + +The project stages of the collaborating parties shall be synchronized +correspondingly: if a deliverable is advanced or rejected at the +external standardization body, the ELF project stage shall be advanced +or retained accordingly. + + +=== Document requirements + +Requirements of an ELF document are stated in <>. + diff --git a/sources/directive-standardization/sections/07-public-review.adoc b/sources/directive-standardization/sections/07-public-review.adoc new file mode 100644 index 0000000..247ef49 --- /dev/null +++ b/sources/directive-standardization/sections/07-public-review.adoc @@ -0,0 +1,104 @@ +[[public-review]] +== Public review process + + +=== General + +A public review period of 60 days is required for compliance to +<>, which ELF adheres to. + + +=== Timing + +A 60-day public review shall be held in the DIS or FDIS stages +of the standardization deliverable. + +Under co-development, the public review shall be held on +the first instance of reaching the DIS stage: + +* Comments to ELF shall be performed through ELF's public review procedure. +* Comments to an ISO TC shall be performed according to <> and <>. +* Comments to an external standardization body shall be according to their own procedures. + +The co-development parties shall agree to synchronization of the dates +of review periods for the maximum benefit to the joint work item. + + +=== Informal comments + +Informal comments can be solicited from and posted to ELF +communication channels, such as the ELF mailing lists. + +While all participants are free to contribute +suggestions and comments, the actual process of development and +revision of any ELF document must be made by the technical +committees developing the document, and by members of ELF. + +Participants may offer comments not only upon documents currently +posted for review and comment, but upon +published documents of ELF. + +The TCB has overall control of the public review process +including what documents may be posted, the duration of +postings, etc. + +For details of handling informal comments, see <>. + + +=== Formal comments via the document repository + +Formal comments have to be submitted via the issue tracker of the +corresponding ELF document repository. + +In a public review process where formal comments are received: + +* the full list of formal comments is published in the issue tracker +of the corresponding ELF document repository; + +* formal comments from non-ELF members should be addressed +and communicated to the commenter individually. + +For details of handling formal comments, see <>. + + + +[[announcement-channels]] +=== Announcement channels + +When a draft document is made available for public review, it shall be +announced: + +* on the public review page of the ELF website (https://www.expresslang.org); and +* on the issue tracker of the corresponding ELF document repository. + + +==== Eligibility + +. At the request of the Chair of the owning TC and +upon approval of the TCB, any draft intended for +publication is eligible for posting to the <>. + +. A document or section of a document may be posted for public review +and comment at any point within its development but generally it should be +well-formed and close to final draft before such posting. + +. If a section of a larger document is posted to the public review +page, the context of the section must be made clear so that relevant +comments can be made. + +. When a document previously posted for public review is finally +published, a notification of the fact will be posted to the public +review page along with any title changes. + + +==== TC responsibilities + +. Since posting a document for public review and comment invites non-ELF +individuals to participate, the owning TC is responsible +for monitoring comments on the public review process and acting upon +them as appropriate. + +. Since any participant in the public review process may comment upon any +published document at any time, the TCB will monitor +the comments on such documents and bring those comments to the +attention of the owning TC. diff --git a/sources/directive-standardization/sections/08-comments.adoc b/sources/directive-standardization/sections/08-comments.adoc new file mode 100644 index 0000000..be3f325 --- /dev/null +++ b/sources/directive-standardization/sections/08-comments.adoc @@ -0,0 +1,39 @@ +[[comments]] +== Comments + +=== General + +The commenting process is managed by the TCB. The TCB is +responsible for operating the issue tracker of the corresponding +ELF document repository and the distribution of formal comments. + + +[[comments-formal]] +=== Formal comments + +Formal comments are binding comments where the project team +whose work is being commented on must respond to. + +These comments received are considered "`open comments`", meaning +that these comments will be published to the ELF membership. + +Formal comments shall be submitted via the issue tracker of the +corresponding ELF document repository. + +Formal comments on a standardization deliverable shall be shared +with the owning TC within 2 weeks of receiving them. + + +[[comments-informal]] +=== Informal comments + +These comments do not require a response from the project team +whose work is being commented on. + + +[[comments-resolution]] +=== Resolution of comments + +Comments and feedback on standardization work items +shall be considered impartially and judged purely according +to their technical contributions to the work item. diff --git a/sources/directive-standardization/sections/09-corrections.adoc b/sources/directive-standardization/sections/09-corrections.adoc new file mode 100644 index 0000000..cc3cade --- /dev/null +++ b/sources/directive-standardization/sections/09-corrections.adoc @@ -0,0 +1,9 @@ + +[[corrections]] +== Corrections and amendments + +Corrections and amendments to standardization documents are +considered projects themselves, and should be handled +as described in <>. + +// TODO: perhaps some fast tracking possible. diff --git a/sources/directive-standardization/sections/10-ipr.adoc b/sources/directive-standardization/sections/10-ipr.adoc new file mode 100644 index 0000000..3d32274 --- /dev/null +++ b/sources/directive-standardization/sections/10-ipr.adoc @@ -0,0 +1,41 @@ +[[ipr]] +== Intellectual property rights + +=== Free of restrictions + +Text of all working documents as well as co-developed/co-published deliverables will remain free of IPR restrictions that would limit their application. + +=== Copyright + +Copyright of standardization deliverables created under this document +is vested in ELF. + +Copyright of contributions remains with their authors; contributors +grant ELF the license described under <> for the +development and publishing of the deliverables. + + +[[publication-license]] +=== Publication license + +In fulfilment of the commitment that the text of ELF documents remains +free of restrictions that would limit their application, ELF makes its +published documents available to the public under the Creative Commons +Attribution 4.0 International Public License (CC BY 4.0). + + +[[member-sourced]] +=== Member-sourced documents + +Authors of ELF deliverables grant ELF a world-wide, +non-exclusive, non-sub-licensable license +(except for the submission and adoption by other standardization bodies), +to use contents of submitted documents to ELF, +for the development and publishing of the deliverables. + +=== Patented content + +Patented content in a standard will be governed by the ELF IPR policy. + +Any patents involved knowingly in an ELF deliverable must be made +transparent prior to the DIS stage. diff --git a/sources/directive-standardization/sections/11-maintenance.adoc b/sources/directive-standardization/sections/11-maintenance.adoc new file mode 100644 index 0000000..466f9dc --- /dev/null +++ b/sources/directive-standardization/sections/11-maintenance.adoc @@ -0,0 +1,36 @@ +[[maintenance]] +== Maintenance of deliverables + +=== Review period + +The review period of a standardization deliverable is 5 years. + +The review shall be performed by the owning TC, if it has been +disbanded, the TCB. + +=== Updates + +When a document is deemed to be updated, the owning TC shall +take action to either begin the review period in order to +update the document, or begin a new project to produce an amendment. + +When a document is revised, any changes (as opposed to editorial +corrections) should result in the document going through the same +review process originally used for its publication. + +A summary of changes from the previous edition should be +provided at the end of the Foreword. + + +=== New versions + +A document once published may undergo revision and become a new +version or dot release (i.e. V1-V2 or V2.0-V2.1) under several +circumstances. + + +=== Withdrawal + +When a review determines that a published item should be +withdrawn, it should be withdrawn from the list of published +standards. diff --git a/sources/directive-standardization/sections/12-registration.adoc b/sources/directive-standardization/sections/12-registration.adoc new file mode 100644 index 0000000..d2b8a76 --- /dev/null +++ b/sources/directive-standardization/sections/12-registration.adoc @@ -0,0 +1,13 @@ +[[agency]] +== Maintenance agency and registration authority + +=== General + +ELF recognizes that a maintenance agency or +registration authority is required for the successful implementation of +certain standardization deliverables. + +=== Default volunteer role + +The TCB shall serve as the maintenance agency or registration authority +for ELF standardization deliverables as necessary. diff --git a/sources/directive-standardization/sections/99-bibliography.adoc b/sources/directive-standardization/sections/99-bibliography.adoc new file mode 100644 index 0000000..e3222de --- /dev/null +++ b/sources/directive-standardization/sections/99-bibliography.adoc @@ -0,0 +1,10 @@ +[bibliography] +== Bibliography + +* [[[WTOTBT,WTO Technical Barriers To Trade Agreements]]], World Trade Organization, _The WTO Agreements Series Technical Barriers to Trade_ + +* [[[DIR102,ELF 102:2026]]], _ELF Directive: Standard document requirements_ + +* [[[ISODIR1,ISO/IEC Directives, Part 1]]], _ISO/IEC Directives, Part 1, Procedures for the technical work_ + +* [[[ISODIR1C,ISO/IEC Directives, Part 1, Consolidated ISO Supplement]]], _ISO/IEC Directives, Part 1, Consolidated ISO Supplement, Procedures specific to ISO_