《Integrated Justice Exchange Document Methodology, Naming, and.doc》由会员分享，可在线阅读，更多相关《Integrated Justice Exchange Document Methodology, Naming, and.doc（107页珍藏版）》请在三一文库上搜索。
1、wd-ijtc-MNDR-1.0.07/13/2021 3:03 下午 Copyright OASIS Open 2005. All Rights Reserved. Page 1 of 107 1 2Integrated Justice Exchange 3Document Methodology, Naming, and 4Design Rules (MNDR) 5Working Draft, April 20, 2006 6 7Document identifier: 8wd-ijtc-MNDR-1.0.0.doc 9Location: 10Persistent: TBD 11This
2、Version: http:/www.oasis-open.org/apps/org/workgroup/legalxml-intj-exmndr/ 12Previous Version http:/www.oasis-open.org/apps/org/workgroup/legalxml-intj- 13exmndr/documents.php 14Technical Committee: 15OASIS LegalXML Integrated Justice TC 16Chairs: 17Ellen Perry, MTG Management Consultants 18John Rue
3、gg, LA County Information Systems Advisory Body (ISAB) 19Editors: 20John Ruegg, LA County Information Systems Advisory Body (ISAB) 21 22Marcus Leon, LA County Information Systems Advisory Body (ISAB) 23 24Marguerite Soto, LA County Internal Services Department 25 26 27Contributors: 28Scott Came, Jus
4、tice Integration Solutions, Inc. 29Tom Carlson, National Center for State Courts 30Ellen Perry, MTG Management Consultants, L.L.C. 31John Ruegg, LA County Information Systems Advisory Body (ISAB) 32Nancy Rutter, Maricopa County, Arizona 33Abstract: 34The purpose of this document is to establish guid
5、ance on how to develop GJXDM 35Information Exchange Package Documentation. 36Status: 37This document has been drafted by the OASIS LegalXML Integrated Justice MNDR 38subcommittee and is being submitted for review/revision to the OASIS LegalXML 39Integrated Justice TC. It will also be given to other
6、groups in the justice community for 40review/revision. These groups include the GJXDM Training and Technical Assistance wd-ijtc-MNDR-1.0.07/13/2021 3:03 下午 Copyright OASIS Open 2005. All Rights Reserved. Page 2 of 107 41Committee (GTTAC), the Global XML Structure Task Force (XSTF), and the IJIS Inst
7、itute 42XML Advisory Committee. This document is a Working Group Draft NOT yet accepted by 43the Working Group as reflecting its consensus; however, it will serve as the basis for 44discussions. As a work in progress, it should NOT be considered authoritative or final. 45Other subsequently issued do
8、cuments will supersede this document 46 47Committee members should send their comments on this specification to the 48workgroup_mailerlists.oasis-open.org list. Others should subscribe to and send 49comments to the mailto:legalxml-intjusticelists.oasis-open.org list. To subscribe, send 50an email me
9、ssage to mailto:legalxml-intjusticelists.oasis-open.org?subject=Subscribe 51with the word “subscribe” as the body of the message. 52 wd-ijtc-MNDR-1.0.07/13/2021 3:03 下午 Copyright OASIS Open 2005. All Rights Reserved. Page 3 of 107 53Notices 54OASIS takes no position regarding the validity or scope o
10、f any intellectual property or other rights 55that might be claimed to pertain to the implementation or use of the technology described in this 56document or the extent to which any license under such rights might or might not be available; 57neither does it represent that it has made any effort to
11、identify any such rights. Information on 58OASISs procedures with respect to rights in OASIS specifications can be found at the OASIS 59Website. Copies of claims of rights made available for publication and any assurances of 60licenses to be made available, or the result of an attempt made to obtain
12、 a general license or 61permission for the use of such proprietary rights by implementors or users of this specification, 62can be obtained from the OASIS President. 63OASIS invites any interested party to bring to its attention any copyrights, patents or patent 64applications, or other proprietary
13、rights which may cover technology that may be required to 65implement this specification. Please address the information to the OASIS President. 66Copyright OASIS Open 2005. All Rights Reserved. 67This document and translations of it may be copied and furnished to others, and derivative works 68that
14、 comment on or otherwise explain it or assist in its implementation may be prepared, copied, 69published and distributed, in whole or in part, without restriction of any kind, provided that the 70above copyright notice and this paragraph are included on all such copies and derivative works. 71Howeve
15、r, this document itself does not be modified in any way, such as by removing the 72copyright notice or references to OASIS, except as needed for the purpose of developing OASIS 73specifications, in which case the procedures for copyrights defined in the OASIS Intellectual 74Property Rights document
16、must be followed, or as required to translate it into languages other 75than English. 76The limited permissions granted above are perpetual and will not be revoked by OASIS or its 77successors or assigns. 78This document and the information contained herein is provided on an “AS IS” basis and OASIS
17、79DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO 80ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE 81ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A 82PARTICULAR PURPOSE. wd-ijtc-MNDR-1.0.07/13/2021 3:03 下午 Copyright OASIS Op
18、en 2005. All Rights Reserved. Page 4 of 107 84Table of Contents 851INTRODUCTION.6 861.1AUDIENCE.6 871.2SCOPE.6 881.2.1What this MNDR contains.7 891.2.2What this MNDR does not address.7 901.3PURPOSE.7 911.4TERMINOLOGY AND NOTATION.7 921.5PRINCIPLES.8 931.6TERMS AND DEFINITIONS.9 941.6.1Software Licen
19、sing Definitions.9 951.7SYMBOLS AND ABBREVIATIONS.9 961.8RELATIONSHIP TO OTHER XML SPECIFICATIONS.11 971.8.1Global Justice XML Data Model (GJXDM).11 981.8.2OASIS Universal Business Language.11 991.9NORMATIVE REFERENCES.11 1001.10NON-NORMATIVE REFERENCES.12 1012INFORMATION EXCHANGE PACKAGE DOCUMENTAT
20、ION OVERVIEW.14 1022.1BACKGROUND.14 1032.1.1Justice Information Sharing Initiative (Global).14 1042.1.2Global Justice XML Data Model (GJXDM).14 1052.1.3GJXDM Information Exchange Package (GIEP) .14 1062.1.4GJXDM Information Exchange Package Documentation (GIEPD).14 1072.2GIEPD FUNCTIONAL USES.15 108
21、2.2.1Samples / Project starting points.15 1092.2.2Jurisdictional Standards.15 1102.2.3Geopolitical Standards.15 1112.2.4Exchange Documents, Reference Documents .15 1122.3GIEPD DEVELOPMENT PROCESS GUIDANCE.15 1132.3.1Workgroup Composition .15 1142.3.2Development Process Steps.16 1153INFORMATION EXCHA
22、NGE PACKAGE DOCUMENTATION (GIEPD).18 1163.1GIEPD DEVELOPMENT METHODOLOGY DESCRIPTION.18 1173.2GIEPD INFORMATION EXCHANGE DOMAIN MODEL DESCRIPTION.18 1183.2.1Graphical Domain Model Documentation Rules.22 1193.2.2Textual Domain Model.23 1203.2.3Textual Domain Model Documentation Rules .24 1213.3GIEPD
23、SCHEMAS.26 1223.3.1Document Schema.27 1233.3.2Subset Schema.27 1243.3.3Constraint Schema.27 1253.3.4Extension Schema.27 1263.4GIEPD INSTANCE DOCUMENTS.28 1273.4.1Sample Source Documents leverages 204the GJXDM Information Exchange Package Documentation Guidelines GJXDM IEPD published 205by the GJXDM
24、XML Structured Task Force. 206 207GIEPD Development Process Guidance provides information about the composition and 208responsibilities of the development team, including the steps to follow to define an exchange, 209along with the required artifacts. 210 211Information Exchange Package Documentatio
25、n (GIEPD) - This section describes the required 212and optional components which make up a GIEPD including Domain Modeling documentation, 213Schema(s), XML Instance Documentation, other supporting documents and MNDR standards for 214Naming and Packaging the GIEPD into a MNDR conformant ZIP file . 21
26、5 216 wd-ijtc-MNDR-1.0.07/13/2021 3:03 下午 Copyright OASIS Open 2005. All Rights Reserved. Page 7 of 107 217Schema Set all other 260text is explanatory. 261 wd-ijtc-MNDR-1.0.07/13/2021 3:03 下午 Copyright OASIS Open 2005. All Rights Reserved. Page 8 of 107 262Figure 1 Rule Prefix Token Value 263 Attrib
27、ute Declaration Rules(ATD) Code List Rules (CDL) ComplexType Definition Rules(CTD) ComplexType Naming Rules (CTN) Documentation Rules (DOC) Element Declaration Rules (ELD) General Naming Rules (GNR) General Type Definition Rules (GTD) General XML Schema Rules (GXS) Instance Document Rules (IND) Mapp
28、ing Documentation Rules(MAP) Modeling Constraints Rules (MDC) Namespace Rules (NMS) Root Element Declaration Rules (RED) Schema Structure Modularity Rules (SSM) Standards Adherence Rules (STA) Versioning Rules (VER) 264 2651.5 Principles 266Open Standards All artifacts will rely on open standards to
29、 represent required content. 267 268Reuse versus Reinvent This work incorporates proven work developed by other groups, 269including GJXDM methods and standards and OASIS UBL. For example, this work is patterned 270after the successful development of similar methodology, naming, and design rules in
30、the OASIS 271UBL Technical Committee 272 273Collaboration - In developing these proposed rules and guidelines, the subcommittee will consult 274and collaborate with other groups in the justice community (including but not limited to the 275GJXDM Training and Technical Assistance Committee GTTAC, the
31、 Global XML Structure Task 276Force XSTF, and the IJIS Institute XML Advisory Committee.) In consulting with these groups, wd-ijtc-MNDR-1.0.07/13/2021 3:03 下午 Copyright OASIS Open 2005. All Rights Reserved. Page 9 of 107 277the subcommittee will seek to incorporate or reference, as appropriate, any
32、existing or emerging 278work product that they may have 279 2801.6 Terms and Definitions 281This document assumes a basic knowledge of XML which allows designers to create their own 282customized tags, enabling the definition, transmission, validation, and interpretation of data 283between applicati
33、ons and between organizations. A select set of Technical Terms and Definitions 284can be found in the Appendix C - Technical Terminology. 285 2861.6.1 Software Licensing Definitions 287Proprietary 288Proprietary refers to software or formats in which an entity retains distribution and modification 2
34、89rights. Proprietary software, and particularly products produced with the software, can be difficult 290to use without owning a license to the producing software. 291In some cases, a proprietary format becomes ubiquitous to the point that it is a de facto standard. 292Proprietary may refer to a so
35、ftware application itself, or to a product of a software application. For 293example, the underlying format of a document produced with a word processor may be 294proprietary, independent of whether the word processor is proprietary. 295Open Source 296Open Source refers to a group of licenses that a
36、llow entities to distribute software while allowing 297others to copy and modify it. Typically, Open Source licenses require that, if an entity modifies 298and distributes their modifications, they must also grant the same redistribution rights. This 299ensures that improvements to Open Source products are returned to the development 300community. 301Freely Ava