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] Extensions points for attributes

Thanks for the correction David.

The constraints later in the text indeed do specify the restriction.


Maybe in the next draft we can make this more explicit in the attribute list section?

Currently the text in the list of allowed attribute is the same for both true extension points and module-only ones:


-     attributes from other namespaces, OPTIONAL


Maybe it could be changed for <ec>, <sc>, <pc> and <pc> to something like:


-     attributes from other modules, OPTIONAL (see constraints below)


Just a thought.






From: xliff@lists.oasis-open.org [mailto:xliff@lists.oasis-open.org] On Behalf Of David Filip
Sent: Friday, May 26, 2017 12:07 AM
To: Yves Savourel <ysavourel@enlaso.com>
Cc: XLIFF Main List <xliff@lists.oasis-open.org>
Subject: Re: [xliff] Extensions points for attributes


Yves, I don't think this is a mistake. 

On xsd these have the wildcard "other"

But in the extension points are constrained to modules.

Cheers dF 


On May 26, 2017 04:45, "Yves Savourel" <ysavourel@enlaso.com> wrote:

Hi all,


There is a mistake in the section “4.9.1 Extension Points” of the specification (2.0 and 2.1).

It lists only <mrk> and <sm> as the inline code allowing extensions. But according the definition for <pc>, <sc>, <ec> and <ph>: those elements can also have extensions.






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