Changeset 1055
- Timestamp:
- 2005-03-05 19:21:16 (4 years ago)
- Files:
-
- standards/draft-pfeiffer-cmml-02.xml (modified) (20 diffs)
- standards/draft-pfeiffer-cmml-current.xml (modified) (19 diffs)
Legend:
- Unmodified
- Added
- Removed
- Modified
- Copied
- Moved
standards/draft-pfeiffer-cmml-02.xml
r1054 r1055 735 735 clip in its "id" attribute. This name can be used in URIs that 736 736 point either to the CMML file or the Annodex bitstream created 737 from it, and allow to point straight at the clip. This may737 from it, and allows to point straight at the clip. This may 738 738 either be done as a URI fragment or URI query specification. 739 739 </t> … … 819 819 html page or another Annodex bitstream clip or an image 820 820 etc. An "a" element without a "href" attribute is illegal and 821 shouldbe flagged or ignored.821 MUST be flagged or ignored. 822 822 </t> 823 823 824 824 <t>The text contained in an "a" element (i.e. the anchor text) 825 gives a short textual description of the link specified825 provides a short textual description of the link specified 826 826 through the "href" attribute. It explains why the connection 827 827 between the current clip and the destination URI is made. It … … 843 843 clip. This image may be used to visually summarise the content 844 844 of the clip when a link to it is displayed, e.g. by a search 845 engine or in a table of c ontents. The "img" element845 engine or in a table of clips. The "img" element 846 846 definition is very closely related to the xhtml "img" element 847 847 definition with a reduced number of attributes as they make … … 898 898 899 899 <t>For extracting a short text from the "desc" element as 900 needs to be displayed in a table of c ontents or as caption,900 needs to be displayed in a table of clips or as caption, 901 901 the first few characters of the description will be taken. It 902 902 is therefore recommended to place a short meaningful summary … … 906 906 907 907 <t>The internationalisation attributes specify the language of 908 the text in the description snf the "id" attribute a unique identifier909 for the element.908 the text in the description and the "id" attribute a unique 909 identifier for the element. 910 910 </t> 911 911 … … 920 920 <section title="Serialising CMML"> 921 921 922 <t>CMML is an annotation language that is meant to mark up any922 <t>CMML is an annotation language that is meant to mark up any 923 923 time-continuous data and be interleaved in a time-synchronous 924 924 fashion with other time-continuous bitstreams. Therefore, CMML … … 930 930 set up the CMML decoding environment, and contain header type 931 931 information. The content of a CMML bitstream then consists of 932 "clip" tags. The "stream" tag is not represented in the CMML 933 bitstream as it controls the authoring of the bitstream that is 934 created by interleaving the CMML with the media streams listed 935 in the "stream" tag. Its information is meant to be stored in the 936 encapsulation format. 932 "clip" tags. The "stream" tag is not copied into the CMML 933 bitstream as it controls the authoring of the Annodex bitstream. 934 Its information can be used in the encapsulation format. 937 935 </t> 938 936 … … 1010 1008 <t>The CMML secondary headers are a sequence of 1011 1009 two packets that contain the CMML and XML "setup" information: 1012 <list typ s="symbols">1010 <list type="symbols"> 1013 1011 <t>one packet with the CMML xml preamble and "cmml" tag.</t> 1014 1012 <t>one packet with the CMML "head" tag.</t> … … 1163 1161 </t> 1164 1162 1165 <t>The additional fields in a nCMML ident header packet for Ogg1163 <t>The additional fields in a CMML ident header packet for Ogg 1166 1164 have the following meaning: 1167 1165 </t> … … 1187 1185 </list> 1188 1186 1189 <t> Adefault granule rate for CMML is: 1/1000. The default1187 <t>The default granule rate for CMML is: 1/1000. The default 1190 1188 granule shift used is 32, which halfs the granule position to 1191 allow for the backwards pointer to be public.1189 allow for the backwards pointer. 1192 1190 </t> 1193 1191 … … 1210 1208 mapped always to 0 and utc time mappings cannot be represented. 1211 1209 It also loses all the message header fields which contain 1212 machine-readable meta information onthe physical bitstream.1210 machine-readable meta information about the physical bitstream. 1213 1211 </t> 1214 1212 … … 1246 1244 </t> 1247 1245 1248 <t>" Timebase numerator & denominator": if the "timebase"1246 <t>"Basetime numerator & denominator": if the "timebase" 1249 1247 attribute is given in a CMML instance document, it MUST be 1250 1248 represented in the skeleton ident header in the fields 1251 " Timebase numerator" and "Timebase denominator". It is converted1249 "Basetime numerator" and "Basetime denominator". It is converted 1252 1250 from a possible NPT or SMPTE representation to a rational number 1253 to be stored in these fishead fields. 1251 to be stored in these fishead fields. Note the name change from 1252 timebase to basetime with Annodex version 3.0, which further 1253 versions of CMML will also mirror. 1254 1254 </t> 1255 1255 1256 <t>"Presentationtime numerator & denominator": if the "timebase" 1257 attribute is given in a CMML instance document, it also 1258 determines the presentation time of the interleaved bitstream and 1259 the "Timebase numerator" and "Timebase denominator" MUST be 1260 copied to the "Presentationtime numerator" and "Presentationtime 1261 denominator" fields of the skeleton ident header. 1256 <t>"Presentationtime numerator & denominator": to be filled 1257 by the muxer appropriately, e.g. reusing the timebase values. 1262 1258 </t> 1263 1259 1264 <t>"UTC": if the "utc" attribute is given in a CMML instance document, 1265 it MUST be represented in the skeleton ident header in the "UTC" field. 1260 <t>"UTC": if the "utc" attribute is given in a CMML instance 1261 document, it MUST be represented in the skeleton ident header 1262 in the "UTC" field. 1266 1263 </t> 1267 1264 … … 1282 1279 fields "Granulerate numerator" and "Granulerate denominator". 1283 1280 The encoder MUST however ascertain that the values are sensible, 1284 and if it knows the accurate granule rate for a logical bitstrea 1281 and if it knows the accurate granule rate for a logical bitstream 1285 1282 overrun the user input with the one that was used during creation 1286 1283 of the interleaved bitstream. … … 1288 1285 1289 1286 <t>"Content-type" message header field: this attribute MUST be 1290 represented in the respective skeleton fisbone packet as a message header1291 field with name "Content-type", as it signifies the MIME type1287 represented in the respective skeleton fisbone packet as a message 1288 header field with name "Content-type", as it signifies the MIME type 1292 1289 of the media bitstream, providing for a decoding hint. If the user 1293 1290 does not specify the "contenttype" attribute, the encoder … … 1304 1301 <t>User specified message header fields: if "name" and "value" 1305 1302 attributes are specified in the "param" tags of the "import" tag, 1306 these MAY be represented in the skeleton fisbone packet of the respective1307 media bitstream as a message header field with the given name-value pair.1308 These fields are highly dependent on the type of media bitstream1309 handled and it therefore depends on the encoding tool to make1310 a selection of the parameters acquired. For example, an1311 audio bitstream that contains speech in a specific language may1312 be identified during CMML authoring through a param element with1313 "Content-Language" name, and acquired into the media bitstream1314 message header field of the same name.1303 these SHOULD be represented in the skeleton fisbone packet of the 1304 respective media bitstream as a message header field with the 1305 given name-value pair. These fields are highly dependent on the 1306 type of media bitstream handled and it therefore depends on the 1307 encoding tool to make a selection of the parameters acquired. For 1308 example, an audio bitstream that contains speech in a specific 1309 language may be identified during CMML authoring through a param 1310 element with "Content-Language" name, and acquired into the 1311 media bitstream message header field of the same name. 1315 1312 </t> 1316 1313 … … 1331 1328 </t> 1332 1329 1333 <t>"Granulerate numerator & denominator": if the "granulerate" 1334 attribute is present in the "cmml" tag, it MUST be represented 1335 in the fisbone header in the fields "Granulerate numerator" and 1336 "Granulerate denominator". The encoder MUST however ascertain 1337 that the values are sensible. The value defaults to "1/1000" if 1338 it is not specified by the user. 1330 <t>"Granulerate numerator & denominator": is fixed to the 1331 default value of "1/1000". 1339 1332 </t> 1340 1333 1341 1334 <t>"Content-type" message header field: the content type for 1342 1335 the fisbone packet that describes the CMML logical bitstream is 1343 fixed at "text/x-cmml" (or "text/cmml" after IANA registration 1344 of the MIME type. 1336 fixed at "text/x-cmml". 1345 1337 </t> 1346 1338 1347 1339 <t>"charset": if the xml processing directive contains an "encoding" 1348 attribute, this MUST be represented in the CMML fisbone packet as an1349 a ddendum to the message header field "Content-type" as a charset. For1350 example: "Content-type: text/x-cmml; charset=UTF-8".1340 attribute, this MUST be represented in the CMML fisbone packet as 1341 an addendum to the message header field "Content-type" as a 1342 charset. For example: "Content-type: text/x-cmml; charset=UTF-8". 1351 1343 </t> 1352 1344 … … 1361 1353 the "lang" and "dir" attributes are given in a "cmml" tag, they 1362 1354 MUST be represented in the fishbone packet of the CMML bitstream 1363 as message header fields with name "Content-Language" and "Content-Dir". 1355 as message header fields with name "Content-Language" and 1356 "Content-Dir". 1364 1357 </t> 1365 1358 … … 1370 1363 <t>Here is a list of the attribute values of the 1371 1364 "stream" tag and how they are being used: 1372 <list >1365 <list type="symbols"> 1373 1366 <t>id: not used, as this attribute is only used to enable 1374 1367 addressing of the stream tag the XML way (e.g. XPath). … … 1389 1382 <t>Here is a list of the attribute values of the 1390 1383 "import" tag and how they are being used: 1391 <list >1384 <list type="symbols"> 1392 1385 <t>id: this attribute may be represented as a message header field 1393 1386 in the respective skeleton fisbone packet. … … 1424 1417 <t>Here is a list of the attribute values of the 1425 1418 "param" tag list and how they are being used: 1426 <list >1419 <list type="symbols"> 1427 1420 <t>id: not used, as this attribute is only used to enable 1428 1421 addressing of the param tag the XML way (e.g. XPath). standards/draft-pfeiffer-cmml-current.xml
r1053 r1055 977 977 in the "id" attribute. This name can be used in URIs that point 978 978 either to the CMML file or the Annodex bitstream created from it, 979 and allow to point straight at the clip. This may either be done979 and allows to point straight at the clip. This may either be done 980 980 as a URI fragment or URI query specification. The "class" attribute 981 981 provides a space-separated list of style sheet classes, and the … … 1069 1069 html page or another Annodex bitstream clip or an image 1070 1070 etc. An "a" element without a "href" attribute is illegal and 1071 shouldbe flagged or ignored.1071 MUST be flagged or ignored. 1072 1072 </t> 1073 1073 1074 1074 <t>The text contained in an "a" element (i.e. the anchor text) 1075 gives a short textual description of the link specified1075 provides a short textual description of the link specified 1076 1076 through the "href" attribute. It explains why the connection 1077 1077 between the current clip and the destination URI is made. It … … 1093 1093 clip. This image may be used to visually summarise the content 1094 1094 of the clip when a link to it is displayed, e.g. by a search 1095 engine or in a table of c ontents. The "img" element1095 engine or in a table of clips. The "img" element 1096 1096 definition is very closely related to the xhtml "img" element 1097 1097 definition with a reduced number of attributes as they make … … 1151 1151 for the element, the "class" attribute a style-sheet mapping, and 1152 1152 the "title" attribute a brief description to be displayed in e.g. 1153 a table of c ontents or as caption.1153 a table of clips or as caption. 1154 1154 </t> 1155 1155 … … 1164 1164 <section title="Serialising CMML"> 1165 1165 1166 <t>CMML is an annotation language that is meant to mark up any1166 <t>CMML is an annotation language that is meant to mark up any 1167 1167 time-continuous data and be interleaved in a time-synchronous 1168 1168 fashion with other time-continuous bitstreams. Therefore, CMML … … 1174 1174 set up the CMML decoding environment, and contain header type 1175 1175 information. The content of a CMML bitstream then consists of 1176 "clip" tags. The "stream" tag is not represented in the CMML 1177 bitstream as it controls the authoring of the bitstream that is 1178 created by interleaving the CMML with the media streams listed 1179 in the "stream" tag. Its information is meant to be stored in the 1180 encapsulation format. 1176 "clip" tags. The "stream" tag is not copied into the CMML 1177 bitstream as it controls the authoring of the Annodex bitstream. 1178 Its information can be used in the encapsulation format. 1181 1179 </t> 1182 1180 … … 1216 1214 1217 1215 1218 <t>The fields in a nCMML ident header packet have the following1216 <t>The fields in a CMML ident header packet have the following 1219 1217 meaning: 1220 1218 </t> … … 1254 1252 <t>The CMML secondary headers are a sequence of 1255 1253 two packets that contain the CMML and XML "setup" information: 1256 <list typ s="symbols">1254 <list type="symbols"> 1257 1255 <t>one packet with the CMML xml preamble and "cmml" tag.</t> 1258 1256 <t>one packet with the CMML "head" tag.</t> … … 1431 1429 </list> 1432 1430 1433 <t> Adefault granule rate for CMML is: 1/1000. The default1431 <t>The default granule rate for CMML is: 1/1000. The default 1434 1432 granule shift used is 32, which halfs the granule position to 1435 allow for the backwards pointer to be public.1433 allow for the backwards pointer. 1436 1434 </t> 1437 1435 … … 1454 1452 mapped always to 0 and utc time mappings cannot be represented. 1455 1453 It also loses all the message header fields which contain 1456 machine-readable meta information onthe physical bitstream.1454 machine-readable meta information about the physical bitstream. 1457 1455 </t> 1458 1456 … … 1506 1504 </t> 1507 1505 1508 <t>"UTC": if the "utc" attribute is given in a CMML instance document, 1509 it MUST be represented in the skeleton ident header in the "UTC" field. 1506 <t>"UTC": if the "utc" attribute is given in a CMML instance 1507 document, it MUST be represented in the skeleton ident header 1508 in the "UTC" field. 1510 1509 </t> 1511 1510 … … 1526 1525 fields "Granulerate numerator" and "Granulerate denominator". 1527 1526 The encoder MUST however ascertain that the values are sensible, 1528 and if it knows the accurate granule rate for a logical bitstrea 1527 and if it knows the accurate granule rate for a logical bitstream 1529 1528 overrun the user input with the one that was used during creation 1530 1529 of the interleaved bitstream. … … 1532 1531 1533 1532 <t>"Content-type" message header field: this attribute MUST be 1534 represented in the respective skeleton fisbone packet as a message header1535 field with name "Content-type", as it signifies the MIME type1533 represented in the respective skeleton fisbone packet as a message 1534 header field with name "Content-type", as it signifies the MIME type 1536 1535 of the media bitstream, providing for a decoding hint. If the user 1537 1536 does not specify the "contenttype" attribute, the encoder … … 1548 1547 <t>User specified message header fields: if "name" and "value" 1549 1548 attributes are specified in the "param" tags of the "import" tag, 1550 these MAY be represented in the skeleton fisbone packet of the respective1551 media bitstream as a message header field with the given name-value pair.1552 These fields are highly dependent on the type of media bitstream1553 handled and it therefore depends on the encoding tool to make1554 a selection of the parameters acquired. For example, an1555 audio bitstream that contains speech in a specific language may1556 be identified during CMML authoring through a param element with1557 "Content-Language" name, and acquired into the media bitstream1558 message header field of the same name.1549 these SHOULD be represented in the skeleton fisbone packet of the 1550 respective media bitstream as a message header field with the 1551 given name-value pair. These fields are highly dependent on the 1552 type of media bitstream handled and it therefore depends on the 1553 encoding tool to make a selection of the parameters acquired. For 1554 example, an audio bitstream that contains speech in a specific 1555 language may be identified during CMML authoring through a param 1556 element with "Content-Language" name, and acquired into the 1557 media bitstream message header field of the same name. 1559 1558 </t> 1560 1559 … … 1590 1589 1591 1590 <t>"charset": if the xml processing directive contains an "encoding" 1592 attribute, this MUST be represented in the CMML fisbone packet as an1593 a ddendum to the message header field "Content-type" as a charset. For1594 example: "Content-type: text/x-cmml; charset=UTF-8".1591 attribute, this MUST be represented in the CMML fisbone packet as 1592 an addendum to the message header field "Content-type" as a 1593 charset. For example: "Content-type: text/x-cmml; charset=UTF-8". 1595 1594 </t> 1596 1595 … … 1605 1604 the "lang" and "dir" attributes are given in a "cmml" tag, they 1606 1605 MUST be represented in the fishbone packet of the CMML bitstream 1607 as message header fields with name "Content-Language" and "Content-Dir". 1606 as message header fields with name "Content-Language" and 1607 "Content-Dir". 1608 1608 </t> 1609 1609 … … 1614 1614 <t>Here is a list of the attribute values of the 1615 1615 "stream" tag and how they are being used: 1616 <list >1616 <list type="symbols"> 1617 1617 <t>id: not used, as this attribute is only used to enable 1618 1618 addressing of the stream tag the XML way (e.g. XPath). … … 1633 1633 <t>Here is a list of the attribute values of the 1634 1634 "import" tag and how they are being used: 1635 <list >1635 <list type="symbols"> 1636 1636 <t>id: this attribute may be represented as a message header field 1637 1637 in the respective skeleton fisbone packet. … … 1668 1668 <t>Here is a list of the attribute values of the 1669 1669 "param" tag list and how they are being used: 1670 <list >1670 <list type="symbols"> 1671 1671 <t>id: not used, as this attribute is only used to enable 1672 1672 addressing of the param tag the XML way (e.g. XPath).