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

 


Help: OASIS Mailing Lists Help | MarkMail Help

xliff-comment message

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


Subject: csprd02 comment - splitting of modules and extended elements


Hi all,

For <file> we have:

- Zero or one <skeleton> element followed by
- Zero or one <notes> element followed by
- Zero or one <mda:metadata> elements followed by
- Zero, one or more <res:resourceData> elements followed by
- Zero or one <slr:profiles> elements followed by
- Zero or one <slr:data> elements followed by
- Zero or one <val:validation> elements followed by
- One or more <unit> or <group> elements in any order followed by
- Zero, one or more elements from any namespace.

For a processor that implements only the core, extended elements and modules are exactly the same: it tries to preserve both types
as-it.

In <file>, outputting the modules elements before <unit>/<group> block and the extended elements after the <unit>/<group> block
forces the writer to know about which namespace should be written where.

In other word: one cannot implement a processor that is only aware of the core.

Regards,
-yves





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