Author: Prodoc
Date: 2004-11-16 23:37:59 +0300 (Tue, 16 Nov 2004)
New Revision: 797
Modified:
trunk/www.matroska.org/data/technical/specs/tagging/index.html
Log:
Updated/added (ISO) resource links
Modified: trunk/www.matroska.org/data/technical/specs/tagging/index.html
===================================================================
--- trunk/www.matroska.org/data/technical/specs/tagging/index.html 2004-11-16 20:14:33 UTC (rev 796)
+++ trunk/www.matroska.org/data/technical/specs/tagging/index.html 2004-11-16 20:37:59 UTC (rev 797)
@@ -676,20 +676,17 @@
<tr>
<td>RECORDING_LOCATION</td>
<td>UTF-8</td>
- <td>The location where the item was recorded. The countries corresponding to the string, same 2 octets as in Internet
- 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, "US, Texas, Austin". 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, "US, , Austin". </td>
+ <td>The location where the item was recorded. The countries corresponding to the string, same 2 octets as in <a href="http://www.iana.org/cctld/cctld-whois.htm/">Internet domains</a>, or possibly <a href="http://www.iso.org/iso/en/prods-services/iso3166ma/02iso-3166-code-lists/list-en1.html/">ISO-3166</a>. This code is followed by a comma, then more detailed information such as state/province, another comma, and then city. For example, "US, Texas, Austin". 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, "US, , Austin". </td>
</tr>
<tr>
<td>COMPOSITION_LOCATION</td>
<td>UTF-8</td>
- <td>Location that the item was originaly designed/written. The countries corresponding to the string, same 2 octets as in Internet
- 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, "US, Texas, Austin". 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, "US, , Austin".</td>
+ <td>Location that the item was originaly designed/written. The countries corresponding to the string, same 2 octets as in <a href="http://www.iana.org/cctld/cctld-whois.htm/">Internet domains</a>, or possibly <a href="http://www.iso.org/iso/en/prods-services/iso3166ma/02iso-3166-code-lists/list-en1.html/">ISO-3166</a>. This code is followed by a comma, then more detailed information such as state/province, another comma, and then city. For example, "US, Texas, Austin". 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, "US, , Austin".</td>
</tr>
<tr>
<td>COMPOSER_NATIONALITY</td>
<td>UTF-8</td>
- <td>Nationality of the main composer of the item, mostly for classical music. The countries corresponding to the string, same 2 octets as in Internet
- domains, or possibly ISO 3166.</td>
+ <td>Nationality of the main composer of the item, mostly for classical music. The countries corresponding to the string, same 2 octets as in <a href="http://www.iana.org/cctld/cctld-whois.htm/">Internet domains</a>, or possibly <a href="http://www.iso.org/iso/en/prods-services/iso3166ma/02iso-3166-code-lists/list-en1.html/">ISO-3166</a>.</td>
</tr>
<tr id="Personal">
<th colspan="5">Personal</th>
@@ -833,8 +830,7 @@
<td>PURCHASE_CURRENCY</td>
<td>UTF-8</td>
<td>The currency type used to pay for the entity. Use <a
- href="http://www.bsi-global.com/Technical%2BInformation/Publications/_Publications/tig90.xalter"
- >ISO 4217</a> for the 3 letter currency code.</td>
+ href="http://www.xe.com/iso4217.htm">ISO-4217</a> for the 3 letter currency code.</td>
</tr>
<tr id="legal">
<th colspan="5">Legal</th>
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.