Jim, Attached is a first draft proposal for an open repository. Please feel free to comment, edit, revise, etc. The TC will need to decide which of the six license options to employ. No recommendation at this time. Also, we will need to identify one or more ECF TC members to list as initial maintainers. I am happy to help, but do not have enough GitHub experience at this time. Gary Graham From:
legalxml-courtfiling@lists.oasis-open.org <
legalxml-courtfiling@lists.oasis-open.org> On Behalf Of James E Cabral Sent: Monday, December 16, 2019 12:46 PM To: Graham, Gary <
GGraham@courts.az.gov>; Chet Ensign <
chet.ensign@oasis-open.org> Cc:
legalxml-courtfiling@lists.oasis-open.org Subject: [legalxml-courtfiling] RE: TC repository for non-normative artifacts CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. Thanks Gary. No rush. __ Jim Cabral 502 509 4532 From:
legalxml-courtfiling@lists.oasis-open.org <
legalxml-courtfiling@lists.oasis-open.org > on behalf of Graham, Gary <
GGraham@courts.az.gov > Sent: Monday, December 16, 2019 12:02:12 PM To: James E Cabral <
jec@mtgmc.com >; Chet Ensign <
chet.ensign@oasis-open.org > Cc:
legalxml-courtfiling@lists.oasis-open.org <
legalxml-courtfiling@lists.oasis-open.org > Subject: [legalxml-courtfiling] RE: TC repository for non-normative artifacts Jim, Yes, I will work on drafting the proposal. I may not have it ready until after Christmas. I would like to first get up to speed on Open Repository. I also think it would be appropriate to give some thought on criteria and procedures for TC endorsement of submittals. Of the two approaches suggested by Chet, I am thinking the second would be preferred, but I need to learn about Open Repository first. Gary Graham From:
legalxml-courtfiling@lists.oasis-open.org <
legalxml-courtfiling@lists.oasis-open.org > On Behalf Of James E Cabral Sent: Thursday, December 12, 2019 7:53 AM To: Chet Ensign <
chet.ensign@oasis-open.org > Cc:
legalxml-courtfiling@lists.oasis-open.org Subject: [legalxml-courtfiling] RE: TC repository for non-normative artifacts CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. Thank you Chet. That sounds like a great option for our needs. To move forward with this approach, we need someone to draft a proposal for creation on an open repository and then vote as a committee to approve the proposal. Since our next meeting is in March, that will likely be an online ballot. Gary, since it was your idea, would you like to draft the proposal? I’m willing to assist as needed. __ Jim Cabral 502 509 4532 From: Chet Ensign Sent: Wednesday, December 11, 2019 6:52 PM To: James E Cabral Cc:
legalxml-courtfiling@lists.oasis-open.org Subject: Re: TC repository for non-normative artifacts Jim, this sounds like a perfect case for an Open Repository. The Open Repo program, as you know, let's TC's sponsor open source projects that anyone can contribute to. I can see how you could define and set up an ECF Extensions Open Repo where people could fork the repo, add their extensions, then issue pull requests. You could either use the pull request as the filtering point - that is, the TC wouldn't accept it unless it conformed with the provided guidance so that any extensions on the main branch would be deemed usable by others. Or, alternatively, you could set a low bar at that point and have a second repo where you hosted those that passed TC review. The Open Repo program is described in
https://www.oasis-open.org/resources/open-repositories/ Let me know if this helps. /chet On Wed, Dec 11, 2019 at 10:58 AM James E Cabral <
jec@mtgmc.com > wrote: Chet, Now that the LegalXML ECF TC has published ECF 5.0 and is waiting for the necessary implementations before we can request approval as an OASIS specification, we are discussing ways the TC can support implementers. One resource we think we would be useful is a repository of non-normative, implementation-specific extensions to the ECF 4.x and 5.x specifications. When we wrote the specifications, we provided guidance on how implementers should extend ECF messages with their own XML schemas, types, elements, and code lists. ECF 5.0, in particular, includes a defined set of extension points where additional content can be added. We would like implementers to be able to submit their extensions for review by the TC. If the TC finds the extensions conform with the guidance provided in the applicable ECF specifications, the extensions would be published on a publicly available site for other implementers to discover and download for their own use. Ideally, each newly approved extension could be published by the TC without requiring work by OASIS staff (TC administrators). OASIS supports a number of potential solutions for this, including
http://docs.oasis-open.org , Github repos, Wikis, JIRAs and others. The TC is unclear which of these would be most appropriate for this use case. Based on your experience with other TCs, what would you suggest? Thanks, __ Jim Cabral 502 509 4532 -- /chet ---------------- Chet Ensign Chief Technical Community Steward OASIS: Advancing open source & open standards for the information society
http://www.oasis-open.org Mobile: +1 201-341-1393 Attachment: OASIS ECF TC Repository Proposal - Draft.docx Description: OASIS ECF TC Repository Proposal - Draft.docx