In addition, the <name of OASIS TC> also would like to recognize the following people 12 | for their insights and support:
13 ||
17 | |
19 |
20 | |
22 |
The following individuals participated in the creation of this document and are 26 | gratefully acknowledged.
27 | 28 |In addition, the <name of OASIS TC> also would like to recognize the following people 34 | for their insights and support:
35 | 36 |Copyright © OASIS Open 2019. All Rights Reserved.
8 |All capitalized terms in the following text have the meanings assigned to them in the
9 | OASIS Intellectual Property Rights Policy (the "OASIS IPR Policy"). The full
This document and translations of it may be copied and furnished to others, and 12 | derivative works that comment on or otherwise explain it or assist in its 13 | implementation may be prepared, copied, published, and distributed, in whole or in 14 | part, without restriction of any kind, provided that the above copyright notice and 15 | this section are included on all such copies and derivative works. However, this 16 | document itself may not be modified in any way, including by removing the copyright 17 | notice or references to OASIS, except as needed for the purpose of developing any 18 | document or deliverable produced by an OASIS Technical Committee (in which case the 19 | rules applicable to copyrights, as set forth in the OASIS IPR Policy, must be 20 | followed) or as required to translate it into languages other than English.
21 |The limited permissions granted above are perpetual and will not be revoked by OASIS 22 | or its successors or assigns.
23 |This document and the information contained herein is provided on an "AS IS" basis 24 | and OASIS DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO 25 | ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY OWNERSHIP 26 | RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR 27 | PURPOSE.
28 |The following table contains information about revisions to this 26 | document.
27 | 28 || Revision | 30 | 31 |Date | 32 | 33 |Editor | 34 | 35 |Description of changes | 36 | 37 |
|---|---|---|---|
| 01 | 40 | 41 |<Date month year> | 42 | 43 |44 | 45 | | 46 | 47 | |
Copyright © OASIS Open 2019. All Rights Reserved.
26 | 27 |All capitalized terms in the following text have the meanings assigned to them in the 28 | OASIS Intellectual Property Rights Policy (the "OASIS IPR Policy"). The full Policy may be found at the OASIS website.
29 | 30 |This document and translations of it may be copied and furnished to others, and 31 | derivative works that comment on or otherwise explain it or assist in its 32 | implementation may be prepared, copied, published, and distributed, in whole or in 33 | part, without restriction of any kind, provided that the above copyright notice and 34 | this section are included on all such copies and derivative works. However, this 35 | document itself may not be modified in any way, including by removing the copyright 36 | notice or references to OASIS, except as needed for the purpose of developing any 37 | document or deliverable produced by an OASIS Technical Committee (in which case the 38 | rules applicable to copyrights, as set forth in the OASIS IPR Policy, must be 39 | followed) or as required to translate it into languages other than English.
40 | 41 |The limited permissions granted above are perpetual and will not be revoked by OASIS 42 | or its successors or assigns.
43 | 44 |This document and the information contained herein is provided on an "AS IS" basis 45 | and OASIS DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO 46 | ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY OWNERSHIP 47 | RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR 48 | PURPOSE.
49 | 50 |
19 |
|
48 | |
51 |
52 | |
81 |
82 | |
86 |
Not applicable.
16 | 17 | 18 |Kristen James Eberlein (
This document is part of a work product that also includes:
54 |<Add an abstract for the committee note here>
90 |This document was last revised or approved by the OASIS Darwin Information Typing 94 | Architecture (DITA) TC on the above date. The level of approval is also listed 95 | above. Check the “Latest version” location noted above for possible later revisions 96 | of this document.
97 |TC members should send comments on this document to the TC’s email list. Others
98 | should send comments to the TC’s public comment list, after subscribing to it by
99 | following the instructions at the “Send A Comment” button on the TC’s web page at
100 |
When referencing this note, the following citation format should be used:
105 |This OASIS TC Open Repository ( github.com/oasis-open/dita-stylesheets ) is a community public repository that supports participation by anyone, whether affiliated with OASIS or not. Substantive contributions (repository "code") and related feedback is invited from all parties, following the common conventions for participation in GitHub public repository projects. Participation is expected to be consistent with the OASIS TC Open Repository Guidelines and Procedures, the LICENSE designated for this particular repository (Apache License v 2.0), and the requirement for an Individual Contributor License Agreement. Please see the repository README document for other details.
8 |Content accepted as "contributions" to this TC Open Repository, as defined below, are distinct from any Contributions made to the associated OASIS Darwin Information Typing Architecture (DITA) TC itself. Participation in the associated Technical Committee is governed by the OASIS Bylaws, OASIS TC Process, IPR Policy, and related policies. This TC Open Repository is not subject to the OASIS TC-related policies. TC Open Repository governance is defined by separate participation and contribution guidelines as referenced in the OASIS TC Open Repositories Overview.
14 |Because different licenses apply to the OASIS TC's specification work, and this TC Open Repository, there is no guarantee that the licensure of specific repository material will be compatible with licensing requirements of an implementation of a TC's specification. Please refer to the LICENSE file for the terms of this material, and to the OASIS IPR Policy for the terms applicable to the TC's specifications, including any applicable declarations.
19 |Formally, "contribution" to this TC Open Repository refers to content merged into the "Code" repository (repository changes represented by code commits), following the GitHub definition of contributor: "someone who has contributed to a project by having a pull request merged but does not have collaborator [i.e., direct write] access." Anyone who signs the TC Open Repository Individual Contributor License Agreement (CLA), signifying agreement with the licensing requirement, may contribute substantive content — subject to evaluation of a GitHub pull request. The main web page for this repository, as with any GitHub public repository, displays a link to a document listing contributions to the repository's default branch (filtered by Commits, Additions, and Deletions).
25 | 26 |This TC Open Repository, as with GitHub public repositories generally, also accepts public feedback from any GitHub user. Public feedback includes opening issues, authoring and editing comments, participating in conversations, making wiki edits, creating repository stars, and making suggestions via pull requests. Such feedback does not constitute an OASIS TC Open Repository contribution. Some details are presented under "Read permissions" in the table of permission levels for a GitHub organization. Technical content intended as a substantive contribution (repository "Code") to an TC Open Repository is subject to evaluation, and requires a signed Individual CLA.
27 | 28 | 29 |OASIS TC Open Repositories use the familiar fork-and-pull collaboration model supported by GitHub and other distributed version-control systems. Any GitHub user wishing to contribute should fork the repository, make additions or other modifications, and then submit a pull request. GitHub pull requests should be accompanied by supporting comments and/or issues. Community conversations about pull requests, supported by GitHub notifications, will provide the basis for a consensus determination to merge, modify, close, or take other action, as communicated by the repository Maintainers.
35 |Questions or comments about this TC Open Repository's activities should be composed as GitHub issues or comments. If use of an issue/comment is not possible or appropriate, questions may be directed by email to the repository Maintainer(s). Please send general questions about TC Open Repository participation to OASIS Staff at repository-admin@oasis-open.org and any specific CLA-related questions to repository-cla@oasis-open.org.
41 | 42 |