/usr/share/doc/stilts/sun256/votcopy.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 | <html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<link rel="stylesheet" type="text/css" href="sun-style.css">
<title>votcopy: Transforms between VOTable encodings</title>
</head>
<body>
<hr>
<a href="votcopy-usage.html">Next</a> <a href="secB.37.2.html">Previous</a> <a href="cmdUsage.html">Up</a> <a href="index.html">Contents</a> <br> <b>Next: </b><a href="votcopy-usage.html">Usage</a><br>
<b>Up: </b><a href="cmdUsage.html">Command Reference</a><br>
<b>Previous: </b><a href="secB.37.2.html">Examples</a><br>
<hr>
<hr>
<h2><a name="votcopy">B.38 <code>votcopy</code>: Transforms between VOTable encodings</a></h2>
<p>The VOTable standard provides for three basic encodings
of the actual data within each table: TABLEDATA, BINARY and FITS.
TABLEDATA is a pure-XML encoding, which is relatively easy for humans
to read and write.
However, it is verbose and not very efficient for transmission
and processing,
for which reason the more compact BINARY format has been defined.
FITS format shares the advantages of BINARY, but is more likely to
be used where a VOTable is providing metadata 'decoration' for
an existing FITS table.
In addition, the BINARY and FITS encodings may carry their data
either inline
(as the base64-encoded text content of a <code>STREAM</code> element)
or externally
(referenced by a <code>STREAM</code> element's <code>href</code> attribute).
</p>
<p>These different formats have their different advantages and
disadvantages. Since, to some extent, programmers are humans too,
much existing VOTable software deals in TABLEDATA format even though
it may not be the most efficient way to proceed.
Conversely, you might wish to examine the contents of a BINARY-encoded
table without use of any software more specialised than a text editor.
So there are times when it is desirable to convert from one of
these encodings to another.
</p>
<p><code>votcopy</code> is a tool which translates between these
encodings while
making a minimum of other changes to the VOTable document.
The processing may result in some changes to lexical details
such as whitespace in start tags, but the element structure is not
modified. Unlike <code><a href="tpipe.html">tpipe</a></code> it does not impose
STIL's model of what constitutes a table on the data between
reading it in and writing it out, so subtleties dependent on
the exact structure of the VOTable document will not be mangled.
The only important changes should be the contents of
<code>DATA</code> elements in the document.
</p>
<ul>
<li><a href="votcopy-usage.html">B.38.1 Usage</a></li>
<li><a href="secB.38.2.html">B.38.2 Examples</a></li>
</ul>
<hr><a href="votcopy-usage.html">Next</a> <a href="secB.37.2.html">Previous</a> <a href="cmdUsage.html">Up</a> <a href="index.html">Contents</a> <br> <b>Next: </b><a href="votcopy-usage.html">Usage</a><br>
<b>Up: </b><a href="cmdUsage.html">Command Reference</a><br>
<b>Previous: </b><a href="secB.37.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>
|