[www] r517 - trunk/www.matroska.org/data/technical/specs/tagging

Author: atamido
Date: 2004-08-23 11:47:05 +0400 (Mon, 23 Aug 2004)
New Revision: 517

Modified:
   trunk/www.matroska.org/data/technical/specs/tagging/index.html
Log:
Validation fixes.

Modified: trunk/www.matroska.org/data/technical/specs/tagging/index.html
===================================================================
--- trunk/www.matroska.org/data/technical/specs/tagging/index.html	2004-08-23 07:45:53 UTC (rev 516)
+++ trunk/www.matroska.org/data/technical/specs/tagging/index.html	2004-08-23 07:47:05 UTC (rev 517)
@@ -281,8 +281,8 @@
   Tags. While it is possible to use Tag names that are not listed below, this
   is not reccommended as compatability will be compromised. If you find that there
   is a Tag missing that you would like to use, then please contact the Matroska
-  team for its inclusion in the specifications before the format reaches 1.0.</p>
-<p>
+  team for its inclusion in the specifications before the format reaches 1.0.
+</p>
 
 <div class="techdef">
 <table>
@@ -358,7 +358,7 @@
   <tr>
     <td>PERFORMER</td>
     <td>UTF-8</td>
-    <td>Individual performers singled out for mention; e.g., Yoyo Ma (violinist).</a></td>
+    <td>Individual performers singled out for mention; e.g., Yoyo Ma (violinist).</td>
   </tr>
   <tr>
     <td>COMPOSER</td>
@@ -387,7 +387,7 @@
   <tr>
     <td>LEAD_PERFORMER</td>
     <td>UTF-8</td>
-    <td>Lead Performer/Soloist(s). This can sometimes be the same as ARTIST.</a></td>
+    <td>Lead Performer/Soloist(s). This can sometimes be the same as ARTIST.</td>
   </tr>
   <tr>
     <td>ACCOMPANIMENT</td>
@@ -395,41 +395,38 @@
     <td>Band/orchestra/accompaniment. This is akin to the <a href="http://www.id3.org/id3v2.3.0.html#TPE2" target="_blank">TPE2
       tag in ID3.</a></td>
   </tr>
-    <tr>
+  <tr>
     <td>DIRECTOR</td>
     <td>UTF-8</td>
     <td>This is akin to the <a href="othertagsystems/riffmcispecs.html" target="_blank">IART
       tag in RIFF</a>.</td>
   </tr>
-    <tr>
+  <tr>
     <td>ASSISTANT_DIRECTOR</td>
     <td>UTF-8</td>
     <td>The name of the assistant director.</td>
   </tr>
-    <tr>
+  <tr>
     <td>DIRECTOR_OF_PHOTOGRAPHY</td>
     <td>UTF-8</td>
     <td>The name of the director of photography.</td>
   </tr>
-  </tr>
-    <tr>
+  <tr>
     <td>SOUND_DESIGNER</td>
     <td>UTF-8</td>
     <td>The name of the sound designer.</td>
   </tr>
-  </tr>
-    <tr>
+  <tr>
     <td>CARTOON_FILM_ARTIST</td>
     <td>UTF-8</td>
     <td>The name of the cartoon film artist(s).</td>
   </tr>
-  </tr>
-    <tr>
+  <tr>
     <td>CHIEF_CAMERAMAN</td>
     <td>UTF-8</td>
     <td>The name of the chief cameraman (often the same as DIRECTOR_OF_PHOTOGRAPHY).</td>
   </tr>
-    <tr>
+  <tr>
     <td>SOUND_ENGINEER</td>
     <td>UTF-8</td>
     <td>The name of the sound engineer or sound recordist.</td>
@@ -716,12 +713,12 @@
       domains, or possibly ISO 3166. This code is followed by a comma, then more detailed information such as state/province, another comma, and then city. For example, &quot;US, Texas, Austin&quot;. This will allow for easy sorting. It is okay to only store the country, or the country and the state/province. More detailed information can be added after the city through the use of additional commas. In cases where the province/state is unknown, but you want to store the city, simply leave a space between the two commas. For example, &quot;US, , Austin&quot;. </td>
   </tr>
   <tr>
-  <td>RECORDING_COORDINATES</td>
+    <td>RECORDING_COORDINATES</td>
     <td>UTF-8</td>
-    <td>Geographical cooridnates of the idem. e.g. "Latitude: 29° 34’ 40”N, Longitude: 98° 41’ 22”W" </td>
+    <td>Geographical cooridnates of the idem. e.g. "Latitude: 29 34 40, Longitude: 98 41 22" </td>
   </tr>
   <tr>
-  <td>RECORDING_ALTITUDE</td>
+    <td>RECORDING_ALTITUDE</td>
     <td>UTF-8</td>
     <td>Altitude of the idem. e.g. "357 meters" "-30 meters" </td>
   </tr>
@@ -1010,9 +1007,8 @@
     <td>The terms of use for this item. This is akin to the USER tag in ID3.</td>
   </tr>
 </table>
-
-
-<h1>Notes<a name="notes"></h1>
+</div>
+<h1>Notes<a name="notes"/></h1>
 <ul>
 <li>In the Target list, a logicial OR is applied on all tracks, a logicial OR is applied on all chapters. Then a logical AND is applied between the Tracks list and the Chapters list to know if an element belongs to this Target.</li>
 </ul>