Re: [xliff] Split specification

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

I just saw this Rodolfo. There are many other examples at OASIS...Â

- theÂOpen Services for Lifecycle Collaboration (OSLC) Open Project developed a core spec and multiple associated specs (https://github.com/oslc-op/oslc-specs/tree/master/specs

- theÂOASIS Open Data Protocol (OData) TC has the basic spec and then a number of associated modules (http://docs.oasis-open.org/odata/

- XACML, the extensible access control language, has its core v3.0 spec and then a host of implementation/use case specific supporting specs (https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=xacml#technical

And there are others. So, yes, you're far from alone in taking this approach.Â

/chetÂ

On Wed, Jun 23, 2021 at 8:20 AM Rodolfo Raya <rmraya@maxprograms.com> wrote:

Â

Hi,

Â

In last meeting we talked about the possibility to publish core separated from modules. It seems we are not alone.

Â

I recently attended a webinar from the DITA TC and the separation of the standard in two parts was announced. There will be a âBaseâ release containing only basic DITA stuff and later a âTechnicalâ release will include specialized modules.

Â

So, it looks like the idea is not so crazy after all.

Â

Thoughts?

Â

Rodolfo

--Â
Rodolfo M. Raya
https://www.maxprograms.com

Â

--

ChetÂEnsign

Chief Technical Community Steward

OASIS Open

Â

Â

Â

	+1 201-341-1393
	chet.ensign@oasis-open.org
	www.oasis-open.org