Issue69

Title Attributes on <result>
Priority bug Status chatting
Superseder Nosy List dburke, dburnett, eburger, oran, sarvi
Assigned To dburnett Topics

Created on 2006-03-24.20:34:24 by dburnett, last changed 2006-03-24.20:34:24 by dburnett.

Messages
msg122 (view) Author: dburnett Date: 2006-03-24.20:34:24
Supercedes Issue 65-9.

From Issue 65-9:
9. What does the grammar attribute on <result> mean in the context of 
verification?
[Sarvi>>] I believe this could contain the grammar URI that was matched with 
the RECOGNIZE command. But it probably wouldn't make much sense in many cases 
where there may not be an associated RECOGNIZE operation.

I think we should say that the result attribute should be  ignored for 
verification results.  

From Dave Burke on 3/21/06:
o Clarify that grammar attribute on <result> is not present for verification 
results.

From Dan Burnett on 3/24/06:
Actually, it could be.  The original intent was to permit recognition, 
verification, and enrollment results within the same structure.  Because 
originally we were referring to NLSML externally, we created the <extensions> 
and <result-type> elements (which are incorrectly left over in some of the 
examples) as a way to extend that external spec.  However, those aren't 
actually defined anywhere and are redundant in the current spec where the 
contents of the enrollment and verification schemas are to be understood as 
going directly into the NLSML structure under the <result> element.
...
Technically we should now create just one XML schema showing a <result> 
element containing all of the possible result pieces, but I believe the 
chances of making a mistake at this point are greater than the value of 
creating the combined schema.
History
Date User Action Args
2006-03-24 20:34:27dburnettcreate