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] The <tool> element

Hi all,

I'm working on adding the <tool> element to Draft 2 and I have a few
(actually many) unresolved questions:

John proposed the following attributes:
- id
- name
- version
- company

Some of those names are used by other element for slight different purposes
(version of xliff, id of inline codes, etc.) If we use 'name' for tool, why
do we have 'phase-name' in <phase> (or 'company-name') and why we have
different kinds of 'type'?

Or should we go with 'tool-id', 'tool-name', 'tool-company', etc.?

What do we do with the current 'tool' attribute?
- deprecate it?
- make it the reference to to <tool> element?
- leave it as it?

- Do we want to allow an extension point for attribute in <tool>?
(I'm guessing yes)

- Do we want to allow an extension point for element in <tool>?
(I'm guessing yes)

- Should we add a new attribute in the element that refere to <tool> or use
the current 'tool' attribute? If we add one: is 'tool-id' the name to use?
(then why the other references are using 'phase-name' not 'phase-id'?

It seems we are going to have naming convention problem again.

John's original proposal is here:
(see also the two following messages in the same thread).

More later, on <reformat> that time.


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

Powered by eList eXpress LLC