Re: [xliff] ID constraints for the Resource Data module

Uwe, Kevin, can you please answer that on behalf of Ryan?

I believe that the proposed changes are necessary in the light of the approved fragid mechanism, more inline.

I hope that this can be resolved today in the meeting, so that the editorial team can act upon the decision by the next meeting, which seems a feasible deadline for csprd03

Dr. David Filip

=======================

LRC | CNGL | LT-Web | CSIS

University of Limerick, Ireland

telephone: +353-6120-2781

cellphone: +353-86-0222-158

facsimile: +353-6120-2734

http://www.cngl.ie/profile/?i=452

mailto: 

On Wed, Jan 8, 2014 at 12:11 PM, Yves Savourel <> wrote:

Hi Ryan, David, all,

While checking that the modules are following the same ID-related constraints as the extensions, I've found that it's not the case

for the Resource Data module.

The constraint for the id for <resourceItemRef>:

"The value of the OPTIONAL id attribute MUST be unique among all <resourceItemRef> children of the enclosing element."

The constraint for the id for <resourceItem>:

"The value of the OPTIONAL id attribute MUST be unique among all <resourceItem> children of the enclosing element."

Both <resouceItem> and <resourceItemRef> can exist inside a single <resourceData> element.

And <resourceData> can exist zero, one or more times within <file> and <unit>.

So to work properly with the URI Fragment identification we need both ids to have the following constraint:

The value of the id attribute MUST be unique among all <resourceItemRef> and <resourceItem> elements of the immediate enclosing

<file> or <unit> element.

Would that be OK?

I think that this is necessary, unless we want to allow modules to define more than one prefix, which we discussed and discarded last week. 

As a general question also: why allowing several <resourceData> per <file> or <unit>? That element has no attribute, so technically

it makes no difference to have all <resourceItem>/<resourceItemref> is one or more <resourceData>.

This change is not necessary, just seems to make sense to me and I do not see a reason to have more than one of the container elements unless they carry an id.

So I support changing the schema constraint to zero or one.

Any thoughts?

-yves

---------------------------------------------------------------------

To unsubscribe from this mail list, you must leave the OASIS TC that

generates this mail.  Follow this link to all your TCs in OASIS at:

https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php