OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

xliff message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: RE: [xliff] Split specification

I also support this approach and I am looking forward to discussing it in the TC meetings. Thank you Rodolfo for bringing it up.




De : xliff@lists.oasis-open.org <xliff@lists.oasis-open.org> De la part de Bryan Schnabel
Envoyà: 23 June 2021 14:55
à: xliff@lists.oasis-open.org; Rodolfo Raya <rmraya@maxprograms.com>
Objet : Re: [xliff] Split specification


I support this approach 100%. It makes great sense that CAT tools makers might be more inclined to certify support for XLIFF Core, and then pick the modules they want to support. My opinion all along has been that the core specification is bloated with modules the community may not wish to specialize in.


Looking forward to this debate in the TC meetings. I intend to take a very firm stand in favor of Rodolfo's proposed split.






On Wednesday, June 23, 2021, 5:20:36 AM PDT, Rodolfo Raya <rmraya@maxprograms.com> wrote:






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.





Rodolfo M. Raya


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]