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] | [Elist Home]

Subject: [xliff] Tool Element proposal

Proposal (late, sorry)

Add a tool element as a child of <header>.

  <tool id='acme-killerapp-1' name='Killer App' version='1.0'
company='ACME L10n'/>

A simple schema for this element is as follows.

<xsd:element name="tool" minOccurs="0" maxOccurs="unbounded">
    <xsd:attribute name="id" type="xsd:string"/>
    <xsd:attribute name="name" type="xsd:string"/>
    <xsd:attribute name="version" type="xsd:string"/>
    <xsd:attribute name="company" type="xsd:string"/>

Other elements can be added as children to this element which could
give information about how they count, leverage, etc. as those elements
are defined. 

The tool-id attribute could then replace the tool attribute in those
places it is defined: <file> (this is a bit messy), <phase>, &

On a related point, it seems more appropriate to add a phase-name
atttribute to the <count> element rather than the tool-id attribute.
This would give us richer information about the count than just the
tool. The tool information for a count would be available via the
tool-id attribute of the <phase>, then. This logic could be extended to
the <alt-trans> element, also.


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

Powered by eList eXpress LLC