RE: [ACTION-256]: Compile and circulate itsTool examples togehter with proposal text

Hi Dave, all,

Sorry to have missed the discussion at the f2f.
To summarize what I think I understand:


- MT Confidence would have not only one attribute: mtConfidence.
- Text Analysis Annotation (we should really change that name) would also have only one attribute: taConfidence

Both would also require the independent its:toolsRef attribute to be declared.

In both cases it would point to an existing <its:toolInfo> element (external or internal) that would be in a <its:processInfo> element (internally or externally). That toolInfo element would have the following:

- a required xml:id attribute for the ID
- a required dataCategory attribute - indicates the data category generated by that tool

- a required toolName element - indicates the name of the tool that generated the annotation
- an optional toolVersion element - indicates the version of the tool.
- an optional toolValue element - hold some data that is defined by the data category for the toolInfo element. In the case of MT Confidence the data would be the engine identifier.


Question:

--1) It seems we still have the data category defined in toolsRef. So technically is it necessary to declare it in <toolInfo>? I suppose having it there allows to know what the data is about without looking at the toolsRef attribute. But it's also duplicated data and could possibly (but improbably) end up with different values.

--2) I would name toolName, toolVersion and toolInfo just name, version and info: they are always inside <toolInfo> so can't be mis-interpreted.

--3) How would we use <processInfo> in HTML5. We can't really embed that in <script> because the reference is to <toolInfo> not a single ID we could place in ,script> as well (unlike the stand-off annotation).

Cheers,
-yves

Received on Monday, 5 November 2012 16:18:04 UTC