Title of Invention: Information processing apparatus and method and program Abstract: A system and method to facilitate editing of content data. An update metadata identification block identifies metadata that is affected (or must be updated) by destructive edit processing by a material data destructive edit processing block. If the metadata is required for updating, a realtime metadata update block updates realtime metadata and a nonrealtime metadata update block updates nonrealtime metadata in correspondence with the destructive edit processing. A proxy data update block updates proxy data. A clip information file update block updates a clip information file. A clip write block records the data of each clip updated by the above-mentioned processing to an optical disc. Detailed Description: Part general_description_paragraphs: Part CROSS REFERENCES TO RELATED APPLICATIONS: The present invention contains subject matter related to Japanese Patent Application JP 2004-294028 filed in the Japanese Patent Office on Oct. 6, 2004, the entire contents of which being incorporated herein by reference. Part BACKGROUND OF THE INVENTION: The present invention relates to an information processing apparatus and method and a program and, more particularly, to an information processing apparatus and method and a program that correctly support the easier destructive editing of content data for example. With related-art VTRs (Video Tape Recorders), in recording content data such as image data and audio data to a tape device, which is a recording medium, only the content data is usually recorded on the tape device. Metadata such as a time code may be attached to content data; this time code is recorded along the time axis with content data on a tape device. Therefore, if content data is edited by rewriting a part thereof for example, the metadata is updated only in the part corresponding (or accompanying) the edited part of the content data. In contrast, a technique has been recently developed in which content data such as image data and audio data is recorded in a non-linear manner onto a random-accessible recording media such as an optical disc and a hard disc (refer to Japanese Patent Laid-Open No. 2001-29242, for example). In this technique, each piece of recorded content data is managed by a file system as a file (or a clip). In the case of a television program made up of video and audio for example, the content data of this television program is managed as a set of a plurality of files, such as an image file, an audio file, and a metadata file. At this moment, metadata is also generated as the information for managing and reproducing these files. Namely, if content data is recorded in a non-linear manner like this, the content data is attached with many more pieces of metadata than in the case of the VTR. Therefore, like the case of the VTR, if an editing job is executed such as rewriting content data, the contents of the metadata corresponding to the content data must also be updated so as to maintain the integrity of the files forming the content data. With related-art technologies, in the editing of non-linearly recorded data such as above, an edit device does not update the original data to be edited, but newly generates a file that includes the information indicative of editing contents (or the information from which editing results may be derived) (this type of editing is known as non-destructive editing) (refer to Japanese Patent Laid-Open No. 2001-29242, for example). Part SUMMARY OF THE INVENTION: However, in the above-mentioned non-destructive editing, a file providing editing results with the original data left unremoved is newly generated, so that, if an editing job is executed in which a part of content is overwritten with another piece of content data for example, a problem may be caused that the recording area of each recording medium is used in an unwanted manner. Therefore, in the case of recording media such as optical disc in which content is recorded in a non-linear manner, it is also recently required, as with the VTR, to actually update the content data subject to editing (this editing is referred to as destructive editing). However, a problem is that this destructive editing requires each user, in destructively editing image data and audio data, to execute each update job for the metadata corresponding to each piece of the data, thereby making it difficult to maintain the integrity of these data. For example, in a method in which only the metadata corresponding to the edit interval on the time axis of destructively edited image data and audio data is updated, the metadata having no time concept is not subjected to rewriting, so that little integrity may be maintained between the destructively edited image data and audio data and the metadata thereof and between a plurality of pieces of metadata. The maintenance of integrity becomes more difficult as the numbers and types of metadata corresponding to content data subject to destructive editing increase. Moreover, if the integrity of metadata is lost, the user cannot recognize the loss, which presents another problem. It is therefore desired to provide an information processing apparatus and method and a program that are adapted, in destructive editing of content data, to also update the metadata corresponding to the content data so as to maintain the integrity of each piece of the content data and the metadata, thereby correctively and easily executing the destructive editing of the content data to ensure the operations of devices and applications based on the metadata. In carrying out the invention and according to one aspect thereof, there is provided an information processing apparatus having material data destructive editing block for executing destructive editing in which data is actually updated for the material data; metadata identifying block for identifying metadata that is affected by the destructive editing of the material data by the material data destructive editing block; and metadata update block for updating the metadata identified by the metadata identifying block. The above-mentioned information processing apparatus further has content data reading block for reading the content data from a recording medium; and content data writing block for writing the content data to the recording medium. The material data destructive editing block destructively edits material data of content data read from the recording medium by the content data reading block and the content data writing block writes the material data destructively edited by the material data destructive editing block and the content data including the metadata updated by the metadata update block to the recording medium. In the above-mentioned information processing apparatus, the material data destructive editing block destructively edits the material data and updates identification information to be attached to the material data. The metadata identifying block identifies metadata having identification information for identifying metadata to be destructively edited by the material data destructive editing block. The metadata update block updates the identification information for identifying the material data to be destructively edited by the material data destructive editing block included in the metadata identified by the metadata identifying block to the identification information updated by the material data destructive editing block. In the above-mentioned information processing apparatus, the metadata update block has a realtime metadata update block for updating realtime metadata requiring realtime nature in reproducing the metadata at the time of reproducing the material data, in the metadata to be added to the material data; and a nonrealtime metadata update block for updating nonrealtime metadata requiring no realtime nature in reproduction of the metadata at the time of reproduction of the material data, in the metadata to be added to the material data. The above-mentioned information processing apparatus has a proxy data update block for updating proxy data that is a low-resolution data of the material data, along with the destructive editing by the material data destructive editing block. The above-mentioned information processing apparatus has a management information update block for updating management information for managing each piece of data included in the content data, along with the destructive editing by the material data destructive editing block. The above-mentioned information processing apparatus has an update confirming block for confirming a user whether to execute updating of the metadata by the metadata update block. Only when the user allows the updating, the metadata update block updates the metadata. The above-mentioned information processing apparatus further has a mismatch information generation block for generating mismatch information indicative of a mismatch between the material data destructively edited and the metadata corresponding to the material data if the user does not allow the updating of the metadata as confirmed by the update confirming block. In carrying out the invention and according to another aspect thereof, there is provided an information processing method for an information processing apparatus for processing material data forming content and content data formed by metadata to be attached to the material data. This method has the steps of executing destructive editing in which data is actually updated for the material data; identifying metadata that is affected by the destructive editing of the material data by the material data destructive editing step; and updating the metadata identified by the metadata identifying step. In carrying out the invention and according to still another aspect thereof, there is provided a program for making a computer execute processing associated with material data forming content and content data formed by metadata added to the material data. This program has the steps of executing destructive editing in which data is actually updated for the material data; identifying metadata that is affected by the destructive editing of the material data by the material data destructive editing step; and updating the metadata identified by the metadata identifying step. As described and according to the present invention, content data may be correctly destructively edited in an easier manner than related-art technologies. In addition, the present invention may guarantee the operations of metadata-based devices and applications. Part DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS: The following describes preferred embodiments of the present invention. This invention will be described in further detail by way of example with reference to the accompanying drawings. The invention described herein and the embodiments thereof have the following correlation. The description hereof is intended to make sure of the fact that the embodiments supporting the invention described herein are described herein. Therefore, if there is any embodiment that, although described in the description of the preferred embodiment, is not described herein as corresponding to the invention, this does not denote in any manner that such an embodiment does not corresponding to the present invention. Conversely, if any embodiment is described herein as corresponding to the invention, it does not denote in any manner that such an embodiment does not corresponding to other inventions than the present invention. The description hereof does not denote the entire invention described herein. In other words, the existence of any invention described herein and not claimed herein will not deny the existence of any inventions that may be filed as a divisional application, emerge as a result of amendment, or added hereto in the future. In the present invention, an information processing apparatus (for example, an edit device shown in FIG. 1) for processing material data forming content (for example, an image data file or an audio data file shown in FIG. 4) and content data (for example, a clip directory shown in FIG. 4) made up of metadata (for example, a realtime metadata file or a nonrealtime metadata shown in FIG. 4) attached to the above-mentioned material data is provided. This information processing apparatus has material data destructive edit means (for example, a material data destructive edit block shown in FIG. 14) for executing destructive editing (for example, destructive edit processing shown in FIG. 14) for actually updating material data, metadata identification means (for example, an update metadata identification block shown in FIG. 18) for identifying metadata to be affected by the destructive editing of material data by the material data destructive edit means, and metadata update means (for example, a realtime metadata update block and nonrealtime metadata update block shown in FIG. 18) for updating the metadata identified by the metadata identification means. The above-mentioned information processing apparatus further has content data read means (for example, a clip read block shown in FIG. 18) for reading content data from a recording medium (for example, an optical disc shown in FIG. 1) and content data write means (for example, a clip write block shown in FIG. 18) for writing content data to a recording medium. The material data destructive edit means destructively edits the material data of the content data read from a recording medium by the content data read means and the content data write means writes and content data including the material data obtained by the destructive editing by the material data destructive edit means and the metadata obtained by updating by the metadata update means to a recording medium. The above-mentioned material data destructive edit means destructively edits material data and, at the same time, updates the identification information (for example, extended UMID shown in FIG. 8) to be attached to the material data. The metadata identification means identifies the metadata having the identification information of the material data that is destructively edited by the material data destructive edit means. The metadata update means updates the identification information of the material data to be destructively edited by the material data destructive edit means included in the metadata identified by the metadata identification means to the identification information updated by the material data destructive edit means. In the above-mentioned information processing apparatus, the metadata update block has a realtime metadata update block (for example, realtime metadata update block shown in FIG. 18) for updating realtime metadata (for example, realtime metadata file shown in FIG. 4) requiring realtime nature in reproducing the metadata at the time of reproducing the material data, in the metadata to be added to the material data; and a nonrealtime metadata update block (for example, nonrealtime metadata update block shown in FIG. 18) for updating nonrealtime metadata (for example, nonrealtime metadata file shown in FIG. 4) requiring no realtime nature in reproduction of the metadata at the time of reproduction of the material data, in the metadata to be added to the material data. The above-mentioned information processing apparatus has a proxy data update block (for example, proxy data update block shown in FIG. 18) for updating proxy data (for example, a low-resolution data file shown in FIG. 4) that is a low-resolution data of the material data, along with the destructive editing by the material data destructive editing block. The above-mentioned information processing apparatus has a management information update block (for example, a clip information file update block shown in FIG. 18) for updating management information (for example, a clip information file shown in FIG. 4) for managing each piece of data included in the content data, along with the destructive editing by the material data destructive editing block. The above-mentioned information processing apparatus has an update confirming block (for example, an update confirmation processing block shown in FIG. 18) for confirming a user whether to execute updating of the metadata by the metadata update block. Only when the user allows the updating, the metadata update block updates the metadata. The above-mentioned information processing apparatus further has a mismatch information generation block (for example, a mismatch information generation block shown in FIG. 18) for generating mismatch information indicative of a mismatch between the material data destructively edited and the metadata corresponding to the material data if the user does not allow the updating of the metadata as confirmed by the update confirming block. In the present invention, an information processing method of an information processing apparatus (for example, an edit device shown in FIG. 1) for processing material data (for example, an image data file or an audio data file shown in FIG. 4) forming content and content data (for example, a clip directory shown in FIG. 4) made up of metadata (for example, a realtime metadata file or a nonrealtime metadata file shown in FIG. 4) attached to the above-mentioned material data is provided. This method has the steps of executing destructive editing (for example, a destructive editing processing shown in FIG. 14) (for example, step S33 shown in FIG. 21) in which data is actually updated for the material data; identifying metadata (for example, step S34 shown in FIG. 21) that is affected by the destructive editing of the material data by the material data destructive editing step; and updating the metadata identified by the metadata identifying step (for example, step S39 shown in FIG. 21 or step S55 shown in FIG. 22). In carrying out the invention and according to still another aspect thereof, there is provided a program for making a computer execute processing associated with material data forming content (for example, an image data file or an audio data file shown in FIG. 4) and content data (for example, a clip directory shown in FIG. 4) made up of metadata (for example, a realtime metadata file or a nonrealtime metadata file shown in FIG. 4) attached to the above-mentioned material data is provided. This program has the steps of executing destructive editing (for example, step S33 shown in FIG. 21) in which data is actually updated for the material data (for example, destructive editing processing shown in FIG. 14); identifying metadata (for example, step S34 shown in FIG. 21) that is affected by the destructive editing of the material data by the material data destructive editing step; and updating the metadata identified by the metadata identifying step (for example, step S39 shown in FIG. 21 or step S55 shown in FIG. 22). The following describes preferred embodiments of the invention with reference to accompanying drawings. Now, referring to FIG. 1, there is shown an exemplary configuration of a program production system practiced as one embodiment of the invention. In FIG. 1, reference numeral 1 denotes a system for producing programs (or content) that are broadcast by television for example. The program production system 1 has a camcorder 11 and an edit device 13. The camcorder 11 takes a picture of a subject and records material data 21 such as taken image data and audio data and metadata 22 thereof to an optical disc 12, which is a recording medium. Thus, the camcorder 11 is used for material gathering work, one of program production processes. The edit device 13 edits the material data 21 and the metadata 22 recorded on the optical disc 12, in which two or more pieces of data are linked together, unwanted portions are deleted, audio data is inserted, character data such as subtitles is inserted, and a fully packaged data 23 that is data completed as content is generated, for example. Thus, the edit device 13 is used for editing work, one of program production processes. The optical disc 12 is a mass storage recording medium, such as CD (Compact Disc) and DVD (Digital Versatile Disc), and is used to record material data 21 and metadata 22 for example. The optical disc 12 is a random-accessible, thereby managing each item of data as a file in a time-independent manner (or in a nonlinear manner). Therefore, for example, the edit device 13 is made accessible to any file recorded on the optical disc 12 regardless of the recording sequence thereof. Namely, in the program production system 1, the camcorder 11 and the edit device 13 pass the material data 21 and the metadata 22 to each other via the random accessible optical disc 12. Referring to FIG. 2, there is shown an exemplary configuration of record areas of the optical disc 12 shown in FIG. 1. In FIG. 2, a record area 30 of the optical disc 12 has an alternate area 31, file systems 32A and 32B, a nonrealtime metadata area (NRT (NonRealTime) area) 33 and a clip area 34. The alternate area 31 provides a record area for use in an alternate manner if another record area is damaged by scratch, smear, defective manufacture, or expired service life for example to become inaccessible. The file systems 32A and 32B stores management information for managing the data stored in the NRT area 33 and the clip area 34 as files. The NRT area 33 stores NonRealTime metadata (NRT) that is the metadata corresponding to a clip to be recorded in the clip area 34. A clip is a set of data that form one piece of content. For example, a clip is formed of image data, audio data, realtime metadata (RT) made up of the metadata corresponding to each frame of image data, and proxy data that is low-resolution data of image data and audio data, for example. A clip is a unit indicative of one session of image processing from starting of image taking by the operator to the end thereof. Namely, one clip image signal is normally made up of an image signal composed of a plurality of frames. It should be noted that a clip is not only indicative of one session of image processing, but also indicative of a time from the start of image taking in that image processing to the end thereof. A clip is also indicative of the length and amount of the image data obtained by one session of image processing and indicative of the image data itself. In addition, a clip is indicative of the length and amount of the various data obtained by (or associated with) one session of image processing and indicative of an aggregate itself of these various data. To be more specific, the data included in each clip includes material data such as image data and audio data, various metadata associated with other material data, proxy data that is low-resolution data of material data, and play list data for controlling the reproduction of material data, for example. For example, in the material gathering work shown in FIG. 1, a data group obtained by one session of imaging (from start to end of imaging) to be executed by the camcorder 11 is one clip. It should be noted that, if plural pieces of image data are linked together by an editing job in the edit device 13, one piece of image data as a result of the editing job (and each piece of data corresponding to this image data) provides one clip. The metadata to be attached to the material data of a clip includes realtime metadata composed of the data of contents that require being realtime in read processing and nonrealtime metadata composed of the data of contents that do not require being realtime in read processing. Realtime metadata (RT) includes LTC (Linear Time Code) for identifying the position of each image signal frame by use of particular time information such as hour, minute and second, FTC (File Time Code) that is the number of each frame and relative positional information from the start frame of each file, UB (User Bit) indicative of the signal characteristic of the image signal of that frame, UMID (Unique Material Identifier) indicative of each frame, GPS (Global Positioning System) information indicative of the position at which an image was taken by the video camera, an essence marker indicative of information associated with the contents of essence data such as image signal and audio signal, ARIB (Association of Radio Industries and Businesses) metadata, and setting/control information about the video camera by which the image was taken, for example. It should be noted that the ARIB metadata is the metadata for communication interface such as SDI (Serial Digital Interface) standardized by ARIB, an standardization organization. The video camera setting/control information includes IRIS control value, white balance/black balance mode, and lens information associated with lens zooming and focusing. Nonrealtime (NRT) metadata is the metadata for an entire clip. NRT metadata includes a conversion table indicative of the correlation between LTCs corresponding to frames and frame numbers (FTCs), UMID and GPS information, and other information, for example. It should be noted that a frame is a unit of image signals, or the image data for one screen of image (or various types of data corresponding to that image data). A clip is a unit indicative of one session of image processing, from starting of image taking by the operator to ending thereof. Namely, one clip of image signal usually consists of plural frames of image signal. The above-mentioned realtime metadata and nonrealtime metadata may be attached to any unit of image data. In what follows, an example will be described in which realtime metadata is attached to image data, frame by frame, and nonrealtime metadata is attached to image data, clip by clip. Namely, in the following example, it is supposed that realtime metadata be frame metadata that is attached to image signal, frame by frame, and include the data corresponding to the attached frame. Also, it is supposed that nonrealtime metadata be clip metadata that is attached to image signal, clip by clip, and include the data corresponding to an entire attached clip. Normally, image data is arranged as a file, clip by clip, to be managed by a file system. In such a case, nonrealtime metadata may be metadata for each file including image data. It should be noted that realtime metadata and nonrealtime metadata may also include other data than mentioned above. Realtime metadata and nonrealtime metadata may also include the data of same contents. Each piece of data as the above-mentioned realtime metadata may be nonrealtime metadata or, inversely, each piece of data mentioned above as nonrealtime metadata may be realtime metadata. For example, essence markers, ARIB metadata or video camera setting/control information for example may be nonrealtime metadata. UMID and GPS information may be included in realtime metadata or in both realtime metadata and nonrealtime metadata. As shown in FIG. 2, the clip area 34 sequentially records clip data, like clip 34A, clip 34B and so on, for example. In FIG. 2, an area not yet recorded with a clip of the clip area 34 is an unused area 34C. It should be noted that the clip 34A is made up of body A including the image data and audio data belonging to the clip 34A, footer information F_A, and header information H_A. Likewise, the clip 34B is made up of body B including the image data and audio data belonging to clip 34B, footer information F_B, and header information H_B. In the optical disc 12, each piece of data is managed as a file by means of the management information of the file systems 32A and 32B as shown in FIGS. 3 through 5. Any file system may be used for the management of the data recorded to the optical disc 12. For example, UDF (Universal Disc Format) or ISO9660 (International Organization for Standardization 9660) may be used. If a magnetic disc such as a hard disc is used instead of the optical disc 12, a file system such as FAT (File Allocation Tables), NTFS (New Technology File System), HFS (Hierarchical File System), or UFS (Unix™ File System) may be used. Alternatively, a propriety file system may be used. In each of the above-mentioned file systems, the data recorded to the optical disc 12 is managed by a directory structure and files as shown in FIG. 3. Referring to FIG. 3, a root directory (ROOT) 51 has a PROAV directory 52 in which the information associated with image data and audio data and an edit list indicative of material data edit results are arranged in lower directories. It should be noted that the root directory 51 also has configuration table data and so on, not shown. The PROAV directory 52 has a disc metafile (DISCMETA.XML) 53, an index file (INDEX.XML) 54 including management information for managing all clips and edit lists recorded to the optical disc 12, a copy index file (INDEX.BUP) 55, a disc information file (DSICINFO.XML) 56, a copy disc information file (DISCINFO.XML) 57, a clip root directory (CLPR) 58 in which clip data is arranged in lower directories, and an edit list root directory (EDTR) 59 in which edit list data is arranged in lower directories. In the clip root directory 58, the data of clips recorded to the optical disc 12 is managed in different directories for different clips; for example, in the example shown in FIG. 3, the data of three clips are managed in three directories of a clip directory (C0001) 61, a clip directory (C0002) 62, and clip directory (C0003) 63. Namely, The data of the first clip recorded to the optical disc 12 are managed as files of a lower directory of the clip directory 61, the data of the second clip recorded to the optical disc 12 are managed as files of a lower directory of the clip directory 62, and the data of the third clip recorded to the optical disc 12 are managed as files of a lower directory of the clip directory 63. In the edit list root directory 59, the edit lists recorded to the optical disc 12 are managed in different directories for different edit processing operations; for example, in the example shown in FIG. 3, four edit lists are managed in four directories of an edit list directory (E0001) 64, an edit list directory (E0002) 65, an edit list directory (E0003) 66, and an edit list-directory (E0004) 67. Namely, the edit lists indicative of the first edit results of clips recorded to the optical disc 12 are managed as files of a lower directory of the edit list directory 64, the edit lists indicative of the second edit results are managed as files of lower directory of the edit list directory 65, the edit lists indicative of the third edit results are managed as files of lower directory of the edit list directory 66, and the edit lists indicative of the second edit results are managed as files of lower directory of the edit list directory 67. The data of the clip first recorded to the optical disc 12 are arranged and managed as files as shown in FIG. 4 in a lower directory of the clip directory 61 arranged in the clip root directory 58. In the example of FIG. 4, the clip directory 61 has a clip information file (C0001C01.SMI) 71 for managing this clip, an image data file (C0001V01.MXF) 72 including the image data of this file, eight audio data files (C0001A01.MXF through C0001A08.MXF) 73 through 80 including audio data of the channels of this clip, a proxy data file (C0001S01.MXF) 81 including low-resolution data corresponding to the image data of this clip, a nonrealtime metadata file (C0001M01.XML) 82 including the metadata corresponding to the entire clip and nonrealtime metadata that does not require realtime nature such as a conversion table relating LTC (Linear Time Code) with frame number for example, a realtime metadata file (C0001R01.BIM) 83 including the metadata corresponding to the frames of image data of this clip and the realtime metadata that requires realtime nature such as LTC for example, and a picture pointer file (C0001I01.PPF) 84 including a frame structure (for example, the information associated with the data compression algorithm for each picture in MPEG (Moving Picture Experts Group) and the information such as an offset address from the head of file) of the image data file 72. In the example shown in FIG. 4, the image data, proxy data, and the realtime metadata, which require realtime nature at the time of reproduction, are each manages as one file, thereby preventing the read time from increasing. The audio data also requires realtime nature and is provided for eight channels in order to cope with the audio multi-channel such as the 7.1-channel scheme. These eight channels of audio data are each managed as one file. However, the audio data may also be managed as other than eight files; for example, the number of audio data files may be seven or less or nine or more. Likewise, the image data, the proxy data, and the realtime metadata may also be managed as two or more files as required. In the example shown in FIG. 4, the nonrealtime metadata that does not require realtime nature is managed as a file that is different from the realtime metadata that require realtime nature. This prevents unnecessary metadata from being read during the normal reproduction of image data for example, thereby reducing the processing time necessary for the reproduction processing and mitigating the load of the processing. It should be noted that the nonrealtime metadata file 82 is written in XML (extensible Markup Language) in order to provide universality. The realtime metadata file 83 is a BIM file obtained by compiling the XML file in order to reduce the processing time of reproduction processing and mitigating the load of the processing. An exemplary file configuration of the clip directory 61 shown in FIG. 4 may be applied in all clip directories corresponding to the clips recorded to the optical disc 12. Namely, the exemplary file configuration shown in FIG. 4 may be applied in other clip directories 62 and 63 shown in FIG. 3, so that the description of this exemplary file configuration will be skipped. The following describes an exemplary file configuration in lower directories of the edit list root directory 59 shown in FIG. 3. The lower directories of the edit list directory 65 arranged in the above-mentioned edit list root directory 59 have edit list data that is the information associated with the results of the second editing of the data of clips recorded to the optical disc 12, these pieces of edit list data being managed as files as shown in FIG. 5. In the example shown in FIG. 5, the edit list directory 65 has an edit list file (E0002E01.SMI) 91 that is a file for managing this edit result (or edit list), a nonrealtime metadata file for edit list (E0002M01.XML) 92 that is a file including the nonrealtime metadata corresponding to the entire edited material data (or the portion extracted as edited data from the material data of all clips used for the editing) or the nonrealtime metadata newly generated on the basis of the former nonrealtime metadata, a play list file (E0002P01.SMI) 93, a picture pointer file for play list (C0002I01.PPF) 94, an image data file for play list (E0002V01.BMX) 95, an audio data files for play list (E0002A01.BMX through E0002A04.BMX) 96 through 99, a proxy data file for play list (E0002S01.BMX) 100, and a realtime metadata file for play list (E0002R01.BBM) 101. Referring to FIG. 5, nonrealtime metadata that does not require realtime nature is managed as files different from realtime metadata that requires realtime nature. This prevents unnecessary metadata from being read during the reproduction of image data for example (or during the reproduction of edit results) by use of a reproduction procedure (or a play list), thereby reducing the processing time necessary for the reproduction processing and mitigating the load of the processing. The nonrealtime metadata file for edit list 92 is a file that includes the new nonrealtime metadata generated on the basis of the nonrealtime metadata (the nonrealtime metadata files in lower directories of the clip root directory 58) of the clips used for the editing on the basis of the results of the editing. For example, when an editing operation has been executed, the portion corresponding to the edited material data is extracted from the nonrealtime metadata included in the nonrealtime metadata file 82 shown in FIG. 4. The extracted portion is then used to reconstruct new nonrealtime metadata with the edited material data being one clip. The reconstructed nonrealtime metadata is managed as a nonrealtime metadata file for edit list. Namely, the edited material data is added with the new nonrealtime metadata with the edited material data being one clip and this nonrealtime metadata is managed as one nonrealtime metadata file for edit list. Therefore, this nonrealtime metadata file for edit list is generated every time an editing operation is executed. It should be noted that this nonrealtime metadata file for edit list 92 is written in XML in order to provide universality. Likewise, the image data, the proxy data, and the realtime metadata may also be managed as two or more files as required. The number of files corresponding to audio data may be three or less or five or more. The exemplary configuration of the edit list directory 65 shown in FIG. 5 is applicable to all edit lists (or edit results). Namely, the exemplary file configuration shown in FIG. 5 is also applicable to other edit list directories 64, 66, and 67 shown in FIG. 3, so that the description thereof will be skipped. As shown in FIG. 4, image data and audio data are independently managed as an image data file 72 and audio data files 73 through 80 such that these pieces of data may be separately edited (AV (Audio Visual) independent editing) with ease. FIG. 6 shows exemplary-configurations of the formats (AV independent formats) of the image data file 72 and the audio data files 73 through 80 thus managed. The AV independent format provides files in which video data and audio data are collectively arranged. It should be noted that picture items are collectively arranged in an integral multiple of the sector length of the optical disc 12 in the body of the video file of the AV independent format, so that the size of the entire body is also an integral multiple of the sector length of the optical disc 12. Namely, the body of each video file of the AV independent format has a size with sector alignment provided. In MXF, an index table is optional and therefore the video file shown in FIG. 6 (and the audio file to be described later) employs no index table. In the AV independent format, audio data (or voice data) of WAVE format is arranged in KLV (Key Length Value) structure in the body of the file for each channel and a header and a footer are attached to the body to configure an audio file. Namely, in the AV independent format, eight channels of audio data are each independently formed into an audio file. With an audio file of each channel, the audio data of that channel is put in the WAVE format, which is then collectively put in KLV structure to be arranged in the body, to which a header and a footer are attached. It should be noted that the audio data of WAVE format of a given channel are put in KLV structure to be arranged in the body of each audio file of AV independent format. The size of this audio data in its entirety does not always become an integral multiple of the sector length of the optical disc 12. Therefore, in order to provide sector alignment, a filler of KLV structure having a size enough for providing sector alignment is arranged after the audio data of KLV structure in the body of each audio file of AV independent format. As described above, with the AV independent format, video data are collectively arranged in a video file and audio data of all channels are collectively arranged in the audio files corresponding to these channels. This configuration facilitates editing such as the AV independent editing in which video data and audio data are separately edited. It should be noted that image data, audio data, proxy data, and realtime metadata are divided by predetermined time intervals to be recorded as annual-ring data so as to easily maintain realtime nature at the time of reproduction when these data are recorded to the optical disc 12. Namely, the annual-ring data made up of corresponding portions of all data is recorded to the optical disc 12 in a continuous manner. FIG. 7 is a schematic diagram illustrating an exemplary configuration of the realtime metadata file 83 (C001R01.BIM) shown in FIG. 4. As shown in FIG. 7, a realtime metadata file 120 is made up of decode information (DecoderInit) 121 for storing reference information for reproduction and initial description 122 that is a metadata body. Realtime metadata is metadata to be attached to each frame of image data. Namely, the realtime metadata file 120 is configured as a set of metadata (frame units (FUU Fragment Update Unit)) for frames. The initial description 122 has frame unit count information (or the number of FUUs) 123 indicative of the number of frame units, followed by frame units for frames, such as FUU 124A, FUU 124B, FUU 124C, FUU 124D, and so on. It should be noted that the start FUU 124A is indicative of the start information and is configured as a realtime metadata target material filler. Following this FUU 124A, FUU 124B for the frame having frame number 0 that is the start frame of image data is arranged, followed by FUU 124C corresponding to the frame having frame number 1, FUU 124D corresponding to the frame having frame number 2, and so on. It should be noted that the value of the frame unit count information 123 is “the number of frames of image data +1” on the basis of the above-mentioned configuration. Each frame unit is written with the LTC of the corresponding frame, the UMID of the corresponding frame, and a KLV packet made up of information such as the essence marker for example of the corresponding frame. FIG. 8 shows a basic exemplary configuration of the UMID. In FIG. 8, an extended UMID 131 is 64-byte identification information that globally uniquely identifies all materials such as image data, audio data, and metadata. The UMID has a basic UMID 132 that includes minimum necessary basic information and the extended UMID 131 obtained by attaching a source pack 133 that is extended information to the basic UMID 132. Namely, the 64-byte extended UMID 131 is made up of the 32-byte basic UMID 132 and the 32-byte source pack 133. The basic UMID 132 is made up of a 12-byte universal label 141, a 1-byte data length 142, a 3-byte instance number 143, and a 16-byte material number 144. The universal label 141 stores universal label information indicative that this ID is the UMID defined by SMPTE (Society of Motion Picture and Television Engineers). The universal label 141 is made up of a 10-byte fixed header indicative of UMID, 1-byte information indicative of the type of a target AV material to which this UMID is allocated, and 1-byte information indicative of a method of generating each field value of UMID. The data length 142 stores information indicative of the data length of this UMID. Namely, the value of the data length 142 is 32 bytes in the case of the basic UMID and 64 bytes in the case of extended UMID. The instance number 143 is a field for storing information indicative of an instance. This field stores identification information for identifying a material with the value of the material number 144 being the same. For example, if the same data is copied several times, the value of the instance number 143 may be changed depending on the copy method used for identification, thereby identifying the copied data. Namely, this instance number 143 allows the UMID to be used for the identification other than the globally unique identification of material. The material number 144 is a field for storing identification information for globally uniquely identifying a material and is made up of a time snap that is time information, globally unique device identification information, and a random number. The source pack 133 is extended information for the basic UMID 132 and made up of 8-byte time information 145, 12-byte positional information 146, and 12-byte personal information 147. The time information 145, the positional information 146, and the personal information 147 are fields for storing the information associated with the generation of materials to which the UMID is allocated. Namely, a time of generation is stored in the time information 145, GPS (Global Positioning System) information indicative of the position at which the material has been generated is stored in the positional information 146, and the information about a person who has generated the material is stored in the personal information 147. FIG. 9 shows an exemplary basic configuration of a KLV packet. In FIG. 9, a KLV packet 150 is KLV-coded data composed of key data 151, length data 152, and value data 153. This format is compliant with SMPTE 335M/RP214. The key data 151 of the KLV packet 150 is an identifier indicative of a KLV-coded data item. For this identifier, an identifier corresponding to each data item defined in an SMTPE metadata dictionary is used. The length data 152 of the KLV packet 150 is indicative of the length of the value data 153 in bytes. The value data 153 of the KLV packet 150 is made up of a data body such as text data like an XML (extensbile Markup Language) for example. Namely, the KLV packet 150 is the data of a data item indicated by the key data 151, the data of a data item indicated by the length data 152, and the data obtained by encoding the data indicated by the value data 153. Each piece of data included in realtime metadata is composed of above-mentioned each type of data that is a KLV packet having the above-mentioned data structure. Realtime metadata composed of plural pieces of data is largely divided into an essential portion and an optional portion depending on the contents of each type of data. The essential portion is the data included in the realtime metadata corresponding to all frames and composed of various kinds of data such as LTC, user bit, UMID, essence marker, and other KLV data. The optional portion is composed of the data included in realtime metadata as required. The data included in the optional portion includes ARIB metadata and video camera setting/control information, for example. It should be noted the lengths of the essential portion and the optional portion are predetermined fixed lengths. Also, realtime metadata is required to have realtime nature so as to cope with the data transfer through a synchronous communication interface such as SDI, so that the essential portion (and the optional portion) is made up of one file of BIM (BInary Format for MPEG-7), thereby allowing high-speed access to the optical disc 12. The following describes the index file 54 shown in FIG. 3. An index file is used to manage the information about files recorded to the optical disc 12. For the clips stored below a clip root directory are described as a clip table. In the clip table, clips to be managed are specified by use of UMID. Each piece of data forming each clip is also specified by use of UMID. The index file also manages edit lists in the same manner, specifying edit lists to be managed by use of UMID. The following describes information included in the nonrealtime metadata file 82 shown in FIG. 4. The nonrealtime metadata file 82 provides an additional information for that clip, about the image data files and audio data files stored in the same clip directory as the nonrealtime metadata file 82, this additional information requiring no realtime nature. The nonrealtime metadata file 82 includes the UMID of a clip (or a clip information file 71) to which the nonrealtime metadata file 82 is added and an LTC change point table (LtcChangeTable) that is a table information about frames in which LTC changes are nonlinear. The nonrealtime metadata file 82 also includes a typical user bit (TypicalUbit) composed of “reel number” that is information for identifying a recording medium in which each clip is recorded. “Reel number” is information for use in facilitating the management of clips, frequently used in VTR. Further, the nonrealtime metadata file 82 includes a basic UMID change point table (BodyUmidBasicChangeTable) that is a table information about frames in which values of basic UMID (Basic) that is the basic information included in UMID (BodyUmid) of each frame of image data change, a time information change point table (BodyUmidWhenChangeTable) that is table information about frames in which values of time information (When) of UMID (BodyUmid) of each frame of image data change, a positional information change point table (BodyUmidWhereChangeTable) that is table information about frames in which values of positional information (Where) of UMID of each frame of image data change, and a personal information change point table (BodyUmidWhoChangeTalbe) that is table information about frames in which values of personal information (Who) of UMID (BodyUmid) of each frame of image data change. In addition, the nonrealtime metadata file 82 includes a KLV packet table (KlvPacketTable) that is table information about frames attached with KLV packets. Besides, the nonrealtime metadata file 82 includes the information about the video format of image data, the information about the audio format of audio data, the information about the hardware and software used for data recording and editing, the information about user, the title information about
{'bibliographic_information': "{'country': 'US', 'doc-number': '11243006', 'kind': 'B2', 'date': '20051004', 'extension': '351', 'invention_title': 'Information processing apparatus and method and program'}", 'source_file': './grant/2010/ipg100622.xml', 'source_data': 'USPTO-Grant'}