<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<?xml-stylesheet type="text/xsl" href="../part2stratml.xsl"?><StrategicPlan><Name>Charter</Name><Description>[B]ased on the success of Akoma Ntoso several Parliaments and tribunals have an urgent need to use a standardized format inside of a well-controlled workflow, supported by a strong management procedure, and developed within an accredited standards organization like OASIS.</Description><OtherInformation/><StrategicPlanCore><Organization><Name>LegalDocumentML Technical Committee</Name><Acronym>LDTC</Acronym><Identifier>_6653cd8a-628f-11e1-8869-002e7a64ea2a</Identifier><Description>A new OASIS technical committee is being formed. The OASIS LegalDocumentML (LegalDocML) Technical Committee has been proposed by the members of OASIS listed in the charter below. The TC name, statement of purpose, scope, list of deliverables, audience, IPR mode and language specified in the proposal will constitute the TC's official charter. Submissions of technology for consideration by the TC, and the beginning of technical discussions, may occur no sooner than the TC's first meeting.</Description><Stakeholder><Name>Participants</Name><Description>To become a participant in the TC at the first meeting, you must:(a) be an employee of an OASIS member organization or an individual member of OASIS, and
(b) join the Technical Committee using the "Join this TC" button on the TC's home page at [a].To be considered a voting member at the first meeting, you must:(a) join the Technical Committee at least 7 days prior to the first meeting (on or before 22 March 2012); and
(b) you must attend the first meeting of the TC, at the time and date listed in section 2.b below (29 March 2012 at 5:00pm UTC, 12:00pm (U.S. EST), 9:00am (U.S. PDT) 18:00 (CET)).Participants also may join the TC at a later time. All OASIS members with interest in the charter are welcome to participate in the TC's activities.Non-OASIS members who wish to participate may contact us about joining OASIS [b]. In addition, the public may access the information resources maintained for each TC: a mail list archive, document repository and public comments facility, which will be linked from the TC's public home page.</Description></Stakeholder><Stakeholder><Name>OASIS</Name><Description/></Stakeholder><Stakeholder><Name>European Institutions</Name><Description/></Stakeholder><Stakeholder><Name>Member States in Europe</Name><Description/></Stakeholder><Stakeholder><Name>Federated States</Name><Description/></Stakeholder><Stakeholder><Name>USA</Name><Description/></Stakeholder><Stakeholder><Name>Brazil</Name><Description/></Stakeholder></Organization><Vision><Description>An interdisciplinary virtuous circle [for] legislative/judicial/contractual drafting guidelines that take advantage of XML standards; tools that help apply XML to legal content in day-by-day uses, from initiatives to improve the operations of Parliaments, Congresses and Courts; and efforts to create innovation, transparency, assessment, and efficacy in the use of legal information.</Description><Identifier>_6653cfce-628f-11e1-8869-002e7a64ea2a</Identifier></Vision><Mission><Description>[To establish] an OASIS Technical Committee that, starting from the best legal practices and principles of legislative drafting, aims to model, represent, and manage legal documents as authorial, authentic, valid digital resources persistent over time (e.g. still accessible and valid after 100 years).</Description><Identifier>_6653d0fa-628f-11e1-8869-002e7a64ea2a</Identifier></Mission><Value><Name>Innovation </Name><Description/></Value><Value><Name>Transparency</Name><Description/></Value><Value><Name>Assessment</Name><Description/></Value><Value><Name>Efficacy</Name><Description/></Value><Value><Name>Legal Cultures</Name><Description>Legal culture, legislative traditions, political procedures, and legal principles have to be taken in consideration as the pillars in this domain, particularly as information and communication technology (ICT) opens new opportunities.</Description></Value><Value><Name>Legislative Traditions </Name><Description/></Value><Value><Name>Political Procedures </Name><Description/></Value><Value><Name>Legal Principles</Name><Description/></Value><Value><Name>Interoperability</Name><Description>Interoperability of legal content is another positive side effect expected from this TC, especially in supra-order legislative systems (e.g. European Institutions) or between the Member States in Europe and among the Federate States (e.g. Brazil, USA, etc.).</Description></Value><Goal><Name>Legal Document Standard</Name><Description>Create a common legal document standard for the interchange of parliamentary, legislative and judicial documents between institutions anywhere in the world.</Description><Identifier>_6653d1d6-628f-11e1-8869-002e7a64ea2a</Identifier><SequenceIndicator>1</SequenceIndicator><Stakeholder><Name>Parliaments </Name><Description>Parliaments, Congresses, courts and tribunals need to invest in a robust, persistent, non-volatile legal document XML standard for representing legal documents, legislative and judiciary workflows (e.g. electronic court filing (ECF)), lifecycle events, legal metadata, modelling relationships with ontology and eventually with rules (e.g. LegalRuleML initiative started in OASIS, January 2012).</Description></Stakeholder><Stakeholder><Name>Legislative Institutions</Name><Description/></Stakeholder><Stakeholder><Name>Judicial Institutions</Name><Description/></Stakeholder><OtherInformation/><Objective><Name>Promotion</Name><Description>Promote a common legal document standard (based on Akoma Ntoso-UN) that promotes world-wide best practices for the use of XML within a Parliaments’, Assembly’s or Congress’s document management processes, within courts’ and tribunals’ judgment management systems, and generally in legal documents including contracts.</Description><Identifier>_6653d294-628f-11e1-8869-002e7a64ea2a</Identifier><SequenceIndicator>1.1</SequenceIndicator><Stakeholder><Name>Parliaments</Name><Description/></Stakeholder><Stakeholder><Name>Assemblies </Name><Description/></Stakeholder><Stakeholder><Name>Congresses</Name><Description/></Stakeholder><Stakeholder><Name>Courts </Name><Description/></Stakeholder><Stakeholder><Name>Tribunals</Name><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Requirements</Name><Description>Collect requirements from the community of the stakeholders who create, manage and use legislative and legal documents (editors, libraries, public institutions, tribunals, publishers, etc.) in order to extend and refine the standard.</Description><Identifier>_6653d352-628f-11e1-8869-002e7a64ea2a</Identifier><SequenceIndicator>1.2</SequenceIndicator><Stakeholder><Name>Legislative and Legal Document Editors</Name><Description/></Stakeholder><Stakeholder><Name>Legislative and Legal Document Libraries</Name><Description/></Stakeholder><Stakeholder><Name>Legislative and Legal Document Publishers</Name><Description/></Stakeholder><Stakeholder><Name>Public Institutions </Name><Description/></Stakeholder><Stakeholder><Name>Tribunals</Name><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Community Support</Name><Description>Promote growth of a community that supports the stakeholders in order to adopt LegalDocML locally.</Description><Identifier>_6653d42e-628f-11e1-8869-002e7a64ea2a</Identifier><SequenceIndicator>1.3</SequenceIndicator><Stakeholder><Name>LegalDocML Community</Name><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Specifications and Documentation</Name><Description>Provide technical specifications and documentation in order to support the developers of tools and software applications relying on LegalDocML.</Description><Identifier>_6653d514-628f-11e1-8869-002e7a64ea2a</Identifier><SequenceIndicator>1.4</SequenceIndicator><Stakeholder><Name>Developers of LegalDocML Tools </Name><Description/></Stakeholder><Stakeholder><Name>Developers LegalDocML Software Applications</Name><Description/></Stakeholder><OtherInformation/></Objective></Goal><Goal><Name>Long-Term Storage and Access</Name><Description>Provide a format for long-term storage of and access to parliamentary, legislative and judicial documents that allows search, interpretation and visualization of documents.</Description><Identifier>_6653d5fa-628f-11e1-8869-002e7a64ea2a</Identifier><SequenceIndicator>2</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation>Legislative and judicial information needs particular attention in order to capture and preserve legal knowledge when paper is de-materialized into digital resources. Much legal knowledge is embedded in these documents and a specific approach is needed to prevent losses in the accompanying metadata which is often necessary for Parliamentary processing, judicial workflow, and contract management.</OtherInformation><Objective><Name/><Description/><Identifier>_6653d6ea-628f-11e1-8869-002e7a64ea2a</Identifier><SequenceIndicator/><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective></Goal><Goal><Name>Data and Metadata Model</Name><Description>Create a common data and metadata model so that experience, expertise, and tools can be shared and extended by the participating peers, be they courts, Parliaments, Assemblies, Congresses or administrative branches of governments.</Description><Identifier>_6653d7e4-628f-11e1-8869-002e7a64ea2a</Identifier><SequenceIndicator>3</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/><Objective><Name/><Description/><Identifier>_6653d8e8-628f-11e1-8869-002e7a64ea2a</Identifier><SequenceIndicator/><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective></Goal><Goal><Name>Naming and Linking Resources</Name><Description>Create a common mechanism for naming and linking resources (URI) so that documents produced by Parliaments and Courts can be easily cited and cross-referenced by other Parliaments, Courts or individual users.</Description><Identifier>_6653d9ec-628f-11e1-8869-002e7a64ea2a</Identifier><SequenceIndicator>4</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/><Objective><Name/><Description/><Identifier>_6653dafa-628f-11e1-8869-002e7a64ea2a</Identifier><SequenceIndicator/><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective></Goal><Goal><Name>Self Evidence</Name><Description>Be self-explanatory, that is to be able to provide any information for its use and meaning through a simple examination of schema and/or example documents, without the aid of specialized software.</Description><Identifier>_6653dc1c-628f-11e1-8869-002e7a64ea2a</Identifier><SequenceIndicator>5</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/><Objective><Name/><Description/><Identifier>_6653dd3e-628f-11e1-8869-002e7a64ea2a</Identifier><SequenceIndicator/><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective></Goal><Goal><Name>Extensibility</Name><Description>Be extensible, that is to allow modifications to the models within the AKOMA NTOSO framework so that local customisation can be achieved without sacrificing interoperability with other systems.</Description><Identifier>_6653ded8-628f-11e1-8869-002e7a64ea2a</Identifier><SequenceIndicator>6</SequenceIndicator><Stakeholder><Name>Akoma Ntoso</Name><Description/></Stakeholder><Stakeholder><Name>CEN/Metalex</Name><Description/></Stakeholder><OtherInformation>The specifications of the standard will have the name “Akoma Ntoso” and also the root of the XML-schema will be “akomaNtoso”. The name of the TC will be the OASIS LegalDocumentML(LegalDocML) Technical Committee.The LegalDocML TC will achieve compatibility with Akoma Ntoso 1.0., CEN/Metalex, applicable LegalXML vocabularies (e.g. eContracts) and possibly others that may come to the attention of the TC.</OtherInformation><Objective><Name/><Description/><Identifier>_6653e040-628f-11e1-8869-002e7a64ea2a</Identifier><SequenceIndicator/><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective></Goal></StrategicPlanCore><AdministrativeInformation><StartDate/><EndDate/><PublicationDate>2012-02-28</PublicationDate><Source>http://www.oasis-open.org/news/announcements/call-for-participation-oasis-legaldocumentml-legaldocml-tc</Source><Submitter><FirstName>Owen</FirstName><LastName>Ambur</LastName><PhoneNumber/><EmailAddress>Owen.Ambur@verizon.net</EmailAddress></Submitter></AdministrativeInformation></StrategicPlan>
