This file is indexed.

/usr/share/doc/stilts/sun256/taplint.html is in stilts-doc 3.1.2-2.

This file is owned by root:root, with mode 0o644.

The actual contents of the file can be viewed below.

  1
  2
  3
  4
  5
  6
  7
  8
  9
 10
 11
 12
 13
 14
 15
 16
 17
 18
 19
 20
 21
 22
 23
 24
 25
 26
 27
 28
 29
 30
 31
 32
 33
 34
 35
 36
 37
 38
 39
 40
 41
 42
 43
 44
 45
 46
 47
 48
 49
 50
 51
 52
 53
 54
 55
 56
 57
 58
 59
 60
 61
 62
 63
 64
 65
 66
 67
 68
 69
 70
 71
 72
 73
 74
 75
 76
 77
 78
 79
 80
 81
 82
 83
 84
 85
 86
 87
 88
 89
 90
 91
 92
 93
 94
 95
 96
 97
 98
 99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
<html>
   
   <head>
      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
      <link rel="stylesheet" type="text/css" href="sun-style.css">
      <title>taplint: Tests TAP services</title>
   </head>
   
   <body>
      <hr>
      <a href="taplint-usage.html">Next</a> <a href="secB.19.2.html">Previous</a> <a href="cmdUsage.html">Up</a> <a href="index.html">Contents</a> <br> <b>Next: </b><a href="taplint-usage.html">Usage</a><br>
       <b>Up: </b><a href="cmdUsage.html">Command Reference</a><br>
       <b>Previous: </b><a href="secB.19.2.html">Examples</a><br>
      
      <hr>
      <hr>
      <h2><a name="taplint">B.20 <code>taplint</code>: Tests TAP services</a></h2>
      <p><code>taplint</code> runs a series of tests on a Table Access Protocol
         (<a href="http://www.ivoa.net/Documents/TAP/">TAP</a>)
         service and reports the results.  Unlike most of the other tools in 
         this package it is not likely to be of use to normal users;
         its intended use is for people developing or operating TAP services
         to assess their services, perhaps with a view to improving compliance.
         
      </p>
      <p>Testing takes place in a number of stages; it is possible to choose 
         which stages are run in by using the <code>stages</code> parameter.
         The default output (<code>format=text</code>)
         is line-based text to standard output,
         and each report line is of the (fairly greppable) form:
         <pre>
   T-SSS-MMMMxN aaaaa...
</pre>
         where the parts have the following meanings:
         <ul>
            <li><code>T</code>: Report type,
               one of E(rror), W(arning), I(nfo), S(ummary), F(ailure).
               See the documentation of the <code>report</code> parameter for
               further description of what these mean.
               The <code>report</code> parameter can be used to suppress some of these;
               only <code>E</code> indicates actual service compliance errors, but
               including the others may make it easier to see what's going on.
               
            </li>
            <li><code>SSS</code>: Stage abbreviation, as used in the <code>stages</code>
               parameter.  The <code>stages</code> parameter can be used to select
               which stages are run.
               
            </li>
            <li><code>MMMM</code>: Message label, which is always the same for
               messages generated by the same test, is usually different for
               messages generated by different tests, and may be somewhat mnemonic.
               
            </li>
            <li><code>x</code>: Continuation indicator,
               either "<code>-</code>" or "<code>+</code>".
               In most cases it is "<code>-</code>", indicating the first line of
               a message, but multi-line messages (rare) use "<code>-</code>" for the first
               line and "<code>+</code>" for any continuation lines.
               
            </li>
            <li><code>N</code>: Sequence number, which is 1 for the first time
               message <code>T-SSS-MMMM</code> is reported, and increases by one
               for each subsequent appearance.
               After a certain maximum (determined by the <code>maxrepeat</code>
               parameter) additional reports with the same code are no longer output
               individually, but a summary of the number of reports so discarded
               is written at the end of the section with the character "<code>x</code>"
               instead of the sequence number.
               This behaviour prevents the output being swamped by
               multiple reports of the same issue.
               If the <code>maxrepeat</code> parameter is increased above 9, more than
               one digit will be used here (so e.g. for maxrepeat=999, the format would
               be <code>NNN</code> not <code>N</code>).
               
            </li>
            <li><code>aaaaa...</code>: Message text, a free text description of
               what is being reported.
               
            </li>
         </ul>
         
      </p>
      <p>If you don't like that format, others may be selected using the
         <code>format</code> parameter, which currently also supports JSON.
         For more flexible interaction with the output you can invoke
         <code>taplint</code> <a href="taskApi.html">programmatically</a>
         and supply your own 
         <a href="http://andromeda.star.bris.ac.uk/starjavadocs/uk/ac/starlink/ttools/taplint/OutputReporter.html"><code>OutputReporter</code></a>
         instance.
         
      </p>
      <p>TAP is a complicated beast, referencing many standards
         (including 
         <a href="http://www.ivoa.net/Documents/TAP/">TAP</a>,
         <a href="http://www.ivoa.net/Documents/UWS/">UWS</a>,
         <a href="http://www.ivoa.net/Documents/VODataService/">VODataService</a>,
         <a href="http://www.ivoa.net/Documents/latest/ADQL.html">ADQL</a>,
         <a href="http://www.ivoa.net/Documents/latest/VOResource.html">VOResource</a>,
         <a href="http://www.ivoa.net/Documents/VOSI/">VOSI</a>,
         <a href="http://www.ivoa.net/Documents/TAPRegExt/">TAPRegExt</a>,
         <a href="http://www.ivoa.net/documents/DALI/">DALI</a>,
         <a href="http://www.ivoa.net/Documents/ObsCore/">ObsCore</a>,
         <a href="http://www.ivoa.net/Documents/VOTable/">VOTable</a>,
         <a href="http://www.w3.org/Protocols/rfc2616/rfc2616.html">HTTP</a>,
         <a href="https://www.w3.org/TR/rdfa-lite/">RDFa Lite</a>),
         and it is hard to write a validator which is comprehensive, especially
         one which can provide useful output for services with a range of 
         compliance levels.
         This tool tries to make a wide range of tests, but does not claim to
         be comprehensive.  An idea of what tests it does perform can be gained 
         from the stages listed in the description of the <code>stages</code>
         parameter.  It does make a fairly good job of checking that declared
         metadata is consistent and matches the data actually returned from queries,
         and it tests job submission in most of the various ways permitted by the TAP
         standard.  Things it does not test much include complex ADQL queries, 
         coordinate/STC-related data types, queries in non-ADQL languages,
         and service registration.
         
      </p>
      <ul>
         <li><a href="taplint-usage.html">B.20.1 Usage</a></li>
         <li><a href="secB.20.2.html">B.20.2 Examples</a></li>
      </ul>
      <hr><a href="taplint-usage.html">Next</a> <a href="secB.19.2.html">Previous</a> <a href="cmdUsage.html">Up</a> <a href="index.html">Contents</a> <br> <b>Next: </b><a href="taplint-usage.html">Usage</a><br>
       <b>Up: </b><a href="cmdUsage.html">Command Reference</a><br>
       <b>Previous: </b><a href="secB.19.2.html">Examples</a><br>
      
      <hr><i>STILTS - Starlink Tables Infrastructure Library Tool Set<br>Starlink User Note256<br>STILTS web page:
         <a href="http://www.starlink.ac.uk/stilts/">http://www.starlink.ac.uk/stilts/</a><br>Author email:
         <a href="mailto:m.b.taylor@bristol.ac.uk">m.b.taylor@bristol.ac.uk</a><br>Mailing list:
         <a href="mailto:topcat-user@jiscmail.ac.uk">topcat-user@jiscmail.ac.uk</a><br></i></body>
</html>