Re: TC repository for non-normative artifacts

[Chet Ensign <chet.ensign@oasis-open.org>]

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Â