annotate docs/ResultsSpecificationDocument.tex @ 703:375410a5571d

Merged with some uncommited parts. My mistake!
author Nicholas Jillings <n.g.r.jillings@se14.qmul.ac.uk>
date Wed, 08 Apr 2015 09:45:24 +0100
parents 69dc1ef007bc abed44552e79
children 6062bbcc29b8
rev   line source
nicholas@9 1 \documentclass{article}
nicholas@9 2
nicholas@9 3 \usepackage[margin=2cm]{geometry}
nicholas@9 4 \usepackage{listings}
nicholas@9 5 \usepackage{color}
nicholas@9 6
nicholas@9 7 \begin{document}
nicholas@9 8
nicholas@9 9 \large APE Browser Tool - Results Specification Document
nicholas@9 10
nicholas@9 11 \section{Introduction}
nicholas@9 12 This document outlines the return XML document structure to hold the results from the Browser Evaluation Tool, specifically for the APE Interface.
nicholas@9 13
nicholas@9 14 \section{Root}
n@696 15 The root of the document is \texttt{BrowserEvaluationResult}.
nicholas@9 16
n@696 17 \section{AudioElement}
n@696 18 A 1st level node, this contains the results for a specific audioElement.
n@696 19
n@696 20 \subsection{Attributes}
n@696 21 Has the following attributes, depending on the variables set in the Project Specification.
n@696 22 \begin{itemize}
n@696 23 \item \texttt{id} - Mandatory. This returns the ID of the track in question. This is either the value passed in from the project specification, or calculated based on the position in the list. For instance, in the automatic system, the first test sample has ID 0, the second ID 1 and so forth. The value passed in from the project specification can either be a string or a Number.
n@696 24 \item \texttt{url} - Mandatory. Returns the full URL given incase of errors or for later checking.
n@696 25 \end{itemize}
nicholas@9 26
nicholas@9 27 \subsection{Value}
nicholas@9 28 One of these elements per track, containing the value between 0 and 100 relating the user rating of the track. This is a mandatory element.
BrechtDeMan@702 29 % float or int? (I, Brecht, am sort of indifferent here, it used to be down to .01 or something before, so maybe that or .1)
n@703 30 % Nick - Can be a float, was trying to remove/reduce ambiguity from pixel position. But can easily make it to .01
nicholas@9 31
nicholas@9 32 \subsection{Comment}
n@696 33 One of these elements per track, containing any commenting data from the interface text boxes. Has the two following child nodes.
n@696 34 \begin{itemize}
n@696 35 \item \texttt{Question} - Returns the text next to the comment box
n@696 36 \item \texttt{Response} - Returns the text in the comment box
n@696 37 \end{itemize}
n@696 38
n@696 39 \section{PreTest and PostTest}
n@696 40 A 1st level node, contains the response to any pre-test questions given in the project specification. These are stored in the same Comment node as outlined in the above audioElement.
n@696 41
n@696 42 The PostTest is a 1st level node and contains the response to any post-test questions given in the project specification.
nicholas@9 43
nicholas@9 44 \section{Session Data}
nicholas@9 45 This will contain any captured session data. Currently not implemented but here for future referencing.
BrechtDeMan@702 46 % I used to have a 'global' comment for each 'session' as well
nicholas@9 47
nicholas@9 48 \section{Globals}
nicholas@9 49 Contains any comment boxes which were specified in the APE project specification with the comment ID, comment text and the comment results.
nicholas@9 50
nicholas@9 51 \end{document}