<?xml version="1.0" encoding='ISO-8859-1'?>
<!-- DTD for a results of a single TRECVID known-item or instance search run -->


<!-- A video search run result contains the search results for
a single system (variant) run against all the topics
-->

<!ELEMENT videoSearchRunResult (videoSearchTopicResult+)>

<!-- ptype - processing type (I interactive or F for "fully automatic") 

    trtype - system training type (See Guidelines under "Restrictions")
             INS searches use "X"

     sysId - associated ID of the system (variant) that produced this
             result. This should incorporate an abbreviated form of
             the research group's name to make it unique across
             groups. 10 characters or less would be appreciated.

  priority - evaluation priority (1,2,...4) If not all runs can be
             judged, then judging will begin with the run with priorty
             1 and so on.

 condition - whether the run used info (including the file name) from
             the IACC.1 *_meta.xml files (YES) or did not (NO). INS
             search use "NO"

   usersat - searcher satisfaction with the system used in this run

              - For interactive KIS runs, an real number between 1 and 7 inclusive
              representing ordered categories, chosen based on completion 
              of the following statement:  "I ...

               1 strongly disagree
               2 moderately disagree
               3 slightly disagree
               4 neither agree nor disagree
               5 slightly agree
               6 moderately agree
               7 strongly agree
        
               with the statement that 'I am satisfied with this search system.'"

              If multiple scores are to be summarized, use their median.

              - For automatic KIS runs use any number (1-7); it is required but 
                will not be used. 

              - For INS runs, use any number (1-7); it is required but will not
                be used.

      desc - verbal description of the characteristics of this run,
             how it differs in approach, resources, etc from others
             runs.


-->
<!ATTLIST videoSearchRunResult pType   (I|F)   #REQUIRED 
                              trType   (A|B|C|D|X) #REQUIRED
                               sysId   CDATA     #REQUIRED 
                            priority   (1|2|3|4) #REQUIRED
                           condition   (YES|NO)  #REQUIRED
                             usersat   CDATA     #REQUIRED
                                desc   CDATA     #REQUIRED>


<!-- A video search topic result contains the search results for
a single topic.
-->
<!ELEMENT videoSearchTopicResult (item*)>


<!-- tNum - number of the topic searched to produce this result


     elapsedTime - for interactive searches, the elapsed time in
                   minutes from the time the searcher saw the topic
                   until the searching on that topic ended. This is
                   limited to at most 5 minutes.

                 - for automatic runs would be the time in minutes
                   from the time the system is presented with the
                   topic until the searching on that topic ended

      searcherId - for interactive KIS and INS, a unique identifier
                   for the person who did the search

                 - for automatic (KIS and INS) runs should be set to
                   some constant dummy value.  -->

<!ATTLIST videoSearchTopicResult   tNum   CDATA  #REQUIRED
                            elapsedTime   CDATA  #REQUIRED                     
                            searcherId    CDATA  #REQUIRED>


<!-- A result item identifies a video clip retrieved as relevant
to the topic for this video search result.
-->
<!ELEMENT item     EMPTY >

<!-- seqNum - a sequence number 1,2,3,...  The lower the sequence
number the greater the likelihood the clip meets the need expressed by
the topic. 
              For KIS: automatic run sequence numbers start at 1 and range
              up to at most 100, while interactive runs return at most one
              item per topic.

              For INS: up to 1000 items may be returned per topic.

     shotId - KIS, the shotId contains the file ID (number) from the
              collection.xml file for the IACC.1 test collection

            - INS, the shotId contains the first (number) part of the
              file name of the clip found to contain one or more
              instances of the target, e.g. for the clip "234.mpg",
              shotID would contain just "234".

elapsedTime - the elapsed time in minutes from the time the searcher
              saw the topic until this item was added to the result

--> 
<!ATTLIST item seqNum      CDATA #REQUIRED
               shotId      CDATA #REQUIRED
          elapsedTime      CDATA #IMPLIED>