JP4299683B2 - Metadata management method, metadata management apparatus, metadata management program, and recording medium recording the metadata management program - Google Patents

Description

  The present invention relates to a content cooperation technique, and more particularly, to a metadata management method, a metadata management apparatus, a metadata management program, and a recording medium on which a metadata management program is recorded.

  In recent years, accompanying information (hereinafter referred to as metadata) for each content has been actively added to multimedia content such as video, still images, text, and animation. For example, in the Semantic Web, metadata such as title, author, and creation date is assigned to content, and by using the metadata, efficient information search, collection, and content inference are possible. In addition, in MPEG7 (Moving Picture Experts Group), feature information and keywords of a target content are assigned to video content, and the video content can be efficiently searched using the metadata and understood.

  For example, in Patent Document 1, an index is assigned to each of video content, audio content, and text content as metadata, and synchronized playback of a plurality of multimedia contents is realized based on a scenario that describes the relationship between the indexes. is doing.

As described above, in the Semantic Web and MPEG7, metadata is assigned to contents and objects, and cooperation between a plurality of contents is realized by using the metadata.
JP-A-5-290551 (paragraphs 0014 to 0024, FIGS. 1 to 6)

  However, it is common for content and object producers to provide metadata at the time of production, and the metadata has not changed unless the producer newly adds it.

  In addition, it is important for content to hold a wide variety of metadata when considering the linkage of a large number of unspecified content, but it is important to presuppose a wide variety of metadata in any situation. Really impossible. In addition, metadata that is rarely used will be retained, reducing the scalability of the system.

  A method of increasing and updating metadata at any time on the producer side is also conceivable, but when considering the linkage of content on the Internet, the number is enormous, and new content is constantly created, so it is realistic. It is difficult.

  The present invention has been made in view of such a problem, and performs the process of linking contents to each other, and the metadata that each content holds by making the union of a plurality of content metadata new metadata An object of the present invention is to provide a method for dynamically increasing and updating the content without the need of the creator.

In order to solve such a problem, the present invention uses the following means.
In the metadata management method, the first linkage component transmits a linkage message describing the first data of the first content to the second linkage component, and the second linkage component is sent from the first linkage component. The first data of the first content described in the received cooperation message is entered in distinction from the second metadata attached to the second content, and the second cooperation component performs the first cooperation. The second data related to the first data of the first content described in the cooperation message received from the component is acquired from the second metadata attached to the second content, and filled in the reply message To the first linkage component, and the first linkage component receives the reply message received from the second linkage component. The second data described in Sage, it was decided to fill in distinction from the first metadata assigned to the first data.

By doing so, in the metadata management method, the first data of the first content transmitted by the first linkage component is used as the second data in which the second linkage component is assigned to the second content. Can be entered separately from metadata. Further, the second data transmitted by the second linkage component can be entered separately from the first metadata given to the first data by the first linkage component.

  In the embodiment described later, the first linkage component corresponds to, for example, an HTML document linkage component, and the second linkage component corresponds to, for example, a video content linkage component.

  In the metadata management method, the metadata corresponding to the first event data of the event that has occurred in the first content is entered in the cooperation message transmitted by the first cooperation component, and the second cooperation component includes: The second metadata assigned to the second content is searched for a location that matches the first event data or metadata in the received cooperation message, and the second metadata described in the detected location is searched. The second content is controlled based on the event data.

  By doing so, in the metadata management method, the first linkage component transmits a linkage message in which metadata corresponding to the first event data of the event that has occurred in the first content is entered, and the second linkage component is sent. The cooperation component can control the second content based on the second event data described in the portion matching the first event data or the metadata detected from the second metadata. .

  In the metadata management method, the metadata described in the cooperation message received by the second cooperation component is converted into the second metadata as metadata corresponding to the second event data used when controlling the second content. We decided to fill in the data.

  In this way, in the metadata management method, the second linkage component is provided with the second content by entering the metadata described in the received linkage message in the second metadata. Metadata can be increased dynamically.

  In the metadata management method, the second cooperative component controls the first event data described in the cooperative message received from the first cooperative component and the second content in the reply message to be transmitted. And the metadata corresponding to the first event data described in the reply message. The metadata corresponding to the first event data described in the reply message is entered. It was decided to fill in the first metadata as data.

  By doing so, in the metadata management method, the second cooperation component includes the first event data described in the cooperation message received from the first cooperation component and the second content in the reply message. The metadata corresponding to the second event data used for the control can be entered, and the first linkage component converts the metadata described in the received reply message into the first message described in the reply message. The first metadata can be entered as metadata corresponding to one event data.

In the metadata management method, if the first metadata described in the cooperation message received by the second cooperation component is not written in the second metadata attached to the second content, Enter the date and time when the metadata of 1 was entered in the second metadata,
If the second metadata described in the reply message received by the first linkage component is not entered in the first metadata attached to the first content, the second metadata is changed to the first metadata. Enter the date and time you entered in 1 metadata,
The first metadata is already entered in the second metadata, or the second metadata is already entered in the first metadata,
If the date and time entered is before the specified date and time,
Delete the first or second metadata that has already been entered,
If the date and time entered is later than the specified date and time,
The entered date and time is updated to the date and time when the first metadata or the second metadata is newly entered.

  In this way, in the metadata management method, the date and time when the first metadata is entered for the second metadata and the date and time when the second metadata is entered for the first metadata are entered. If the first metadata and the second metadata are already entered, and the date and time entered is before the predetermined date and time, the first metadata entered If the metadata or the second metadata is deleted and it is later than the set date and time, the date and time when the first metadata or the second metadata is newly entered are entered. Can be updated.

  In the metadata management method, the first metadata or the second metadata in the metadata management method is deleted when the number of metadata to be managed exceeds a predetermined value, Executed from old metadata.

  In this way, in the metadata management method, when the number of metadata to be managed exceeds a predetermined value, the date and time entered can be deleted from the old metadata.

  In the metadata management method, an inquiry as to whether to execute entry of the first data in the second metadata and transmission of the reply message based on the cooperation message received by the second cooperation component is displayed. Only when an instruction to display and execute is input via the input means, the first data is entered into the second metadata and the reply message is transmitted.

  By doing so, in the metadata management method, only when there is an instruction to execute, the first data of the second metadata is added to the second metadata based on the cooperation message received by the second cooperation component. Filling and sending of reply messages can be performed.

  In the metadata management method, when the first event data or the second event data is not described in the first metadata or the second metadata assigned to the first content or the second content In addition, the first event data or the second event data is dynamically entered into the first metadata or the second metadata.

  In this way, in the metadata management method, event data can be dynamically written in the metadata when the event data is not described in the metadata attached to the content.

  In the metadata management method, the newly entered first metadata or second metadata is distinguished from the existing first metadata or second metadata, and the newly entered first metadata or second metadata is distinguished. The use of the metadata or the second metadata is limited.

  By doing so, the metadata management method can distinguish newly entered metadata from existing metadata and limit the use of the newly entered metadata.

  The metadata management method includes a metadata management database that manages a copy of the first metadata or the second metadata assigned to the first content or the second content, and includes the first linkage component or the second content. When the linking component performs reference or writing of the first metadata or the second metadata assigned to the first content or the second content, the first metadata in the metadata management database or We decided to use a copy of the second metadata.

  In this way, the metadata management method can use a copy of the metadata in the metadata management database when referring to and writing the metadata attached to the content.

The first cooperation component of the metadata management apparatus transmits a cooperation message describing the first data of the first content to the second cooperation component, and is described in the reply message received from the second cooperation component. The second data is written separately from the first metadata assigned to the first data, and the second linkage component is described in the linkage message received from the first linkage component. The first data of the first content is entered separately from the second metadata assigned to the second content, and the first data described in the cooperation message received from the first cooperation component The second data related to the first data of the content is obtained from the second metadata attached to the second content and returned. It was decided to send to fill the first coordination components to message.

By doing so, in the metadata management apparatus, the first cooperation component transmits the cooperation message describing the first data of the first content to the second cooperation component, and the second cooperation component. The second data described in the reply message received from the component can be entered separately from the first metadata given to the first data. The second linkage components, the first data of the first content that is described in conjunction message received from the first coordination components, the second metadata and districts assigned to the second content The second data added to the second content and the second data related to the first data of the first content described in the cooperation message received from the first cooperation component are entered separately. It can be obtained from the metadata, filled in a reply message and sent to the first cooperating component.

  In the metadata management apparatus, a first linkage component that writes metadata corresponding to the first event data of an event that has occurred in the first content in the linkage message, and a second linkage that is assigned to the second content. A part where the first event data or metadata is described in the received cooperation message is searched from the metadata, and the second content is based on the second event data described in the detected part. And a second linkage component that controls.

  By doing so, in the metadata management apparatus, the first linkage component transmits a linkage message in which metadata corresponding to the first event data of the event that has occurred in the first content is entered, and the second linkage component is sent. The cooperation component can control the second content based on the second event data described in the portion matching the first event data or the metadata detected from the second metadata. .

  In the metadata management device, the metadata described in the received cooperation message is entered in the second metadata as metadata corresponding to the second event data used when controlling the second content. It was decided to have two linked components.

  By doing so, in the metadata management apparatus, the second linkage component is provided with the second content by writing the metadata described in the received linkage message in the second metadata. Metadata can be increased dynamically.

  Fill in the reply message that transmits the first event data described in the cooperation message received from the first cooperation component and the metadata corresponding to the second event data used when controlling the second content A first cooperation component that writes the metadata described in the received reply message to the first metadata as metadata corresponding to the first event data described in the reply message. With components.

  By doing in this way, in the metadata management apparatus, the second cooperative component includes the first event data described in the cooperative message received from the first cooperative component and the second content in the reply message. The metadata corresponding to the second event data used for the control can be entered, and the first linkage component converts the metadata described in the received reply message into the first message described in the reply message. The first metadata can be entered as metadata corresponding to one event data.

  In the metadata management apparatus, when the first metadata described in the received cooperation message is not written in the second metadata attached to the second content, the first metadata is changed to the first metadata. If the date and time entered in the metadata of No. 2 is entered, and the first metadata is already entered in the second metadata, and the date and time entered is before the predetermined date and time, If the first metadata already entered is deleted and the date and time entered are later than the predetermined date and time, the date and time entered is updated to the date and time when the first metadata was newly entered. If the second linkage component and the second metadata described in the received reply message are not entered in the first metadata attached to the first content, the second metadata is First metade If the second metadata has already been entered in the first metadata, and if the entered date is before the predetermined date, it will be entered. If the date and time entered are later than the predetermined date and time, the entered date and time are updated to the date and time when the second metadata is newly entered. It was decided to provide a linkage component.

  By doing so, the metadata management apparatus enters the date and time when the first metadata is entered for the second metadata and the date and time when the second metadata is entered for the first metadata. If the first metadata and the second metadata are already entered, and the date and time entered is before the predetermined date and time, the first metadata entered If the metadata or the second metadata is deleted and it is later than the set date and time, the date and time when the first metadata or the second metadata is newly entered are entered. Can be updated.

  The metadata management apparatus includes a metadata management database that manages a copy of the first metadata or the second metadata assigned to the first content or the second content, and includes the first content or the second content. A first copy that uses a copy of the first metadata or the second metadata in the metadata management database when referring to or writing the first metadata or the second metadata attached to the content The cooperation component or the second cooperation component is provided.

  In this way, the metadata management method can use a copy of the metadata in the metadata management database when referring to and writing the metadata attached to the content.

  A metadata management program for executing the metadata management method is provided.

  By doing so, the metadata management program can execute the metadata management method.

  A computer-readable recording medium on which a program for executing the metadata management method is recorded is provided.

  By doing so, the program for executing the metadata management method can be operated on a computer that can read the recording medium.

  By coordinating between the contents and using the union of the metadata of multiple contents as new metadata, the metadata held by each content is dynamically increased and updated without the need of the producer. It becomes possible to provide a method.

  With the reception of the cooperation message and the reply message, the metadata possessed by the content dynamically increases. In other words, even if the content creator does not extend the metadata, the metadata held by each content dynamically increases due to the user's cooperation between the contents, and as a result, the cooperation between many unspecified contents Is possible.

  When receiving the cooperation message, each content executes event data described in the cooperation message or an event indicated by a location matching the metadata, based on metadata possessed by itself. In other words, even when the same linkage message is received, events occurring in each content change due to the difference in metadata possessed, so that a variety of content linkages are possible.

  Accompanying the reception of the cooperation message, the metadata described in the cooperation message is added to the metadata possessed by the content. In particular, since it is added as metadata for the event data used in the cooperative operation, it is possible to provide metadata according to the actual usage situation.

  By exchanging the reply message, the metadata of the source content of the cooperative message is expanded. At this time, the metadata possessed by the content that has undergone the cooperative operation, especially the metadata for the event data used in the cooperative operation, is added, so it is possible to add various metadata while maintaining the relevance It becomes.

  Among the metadata possessed by the content, among the metadata that was added as a result of linkage operations, metadata that has not been used for a certain period of time can be automatically deleted. Enables efficient management.

  Since the intention of the user can be reflected when the metadata possessed by the content increases with the cooperation between the contents, it is possible to add only appropriate metadata.

  If there is no description of the event data that occurred in the metadata held by the content, the event data is dynamically described in the metadata. Can be created and extended.

  Due to the linkage operation, the newly added metadata and existing metadata are differentiated, and the use of the newly added metadata is restricted. By adding useless metadata, it is possible to prevent the irrelevant metadata from increasing in a chain.

  Introduce a new metadata management database that manages the copy of metadata held by content, and refer to and write metadata (copy) in this metadata management database when referencing and writing content metadata Thus, using this system, it is possible to link with content created by a third party.

  The metadata management program for executing the metadata management method can be read and operated by the computer.

Embodiments of the present invention will be described in detail with reference to the drawings.
[First embodiment]
<< Summary of Embodiment >>
In the present embodiment, the first metadata attached to the first content and the second metadata attached to the second content are exchanged via a message, and both of the contents are in common. By using the union of metadata as new metadata, the metadata can be dynamically increased or updated.

≪Configuration of content linkage system≫
FIG. 1 is a diagram showing a configuration of a content cooperation system (hereinafter simply referred to as “system”) according to a first embodiment of the present invention. This system realizes cooperation between contents registered in the system, and can be realized by a computer such as a PC (Personal Computer).

  The system includes a content registration unit 1 for registering / releasing content to / from the system, a linked component management unit for managing linked components for each content file type, and providing linked components corresponding to the content when the content is registered 2. A path for message communication is provided between the linked component provided from the linked component management unit 2 and the content, the browser unit 3 displays the content, and the content click displayed on the browser unit 3 When an action occurs, the cooperation message received from the cooperation component assigned to the content is sent to the other cooperation component assigned to each content registered in the system and received from the other cooperation component. Composed of inter-component communication unit 4 to send a reply message to the specified coordination components.

  The browser unit 3 includes an HTML (Media Text Markup Language) HTML document link component 5 and a video content link component 6, an HTML document media viewer 7 such as a Web browser used for displaying registered content, and a video as examples of link components. Assume that a video content media viewer 8 such as a player is provided. Note that content of other file types, for example, a linkage component and a media viewer (word processor application) corresponding to a document created by a word processor may be included.

  FIG. 2 is a diagram showing a configuration of the content registration unit 1 according to the embodiment of the present invention. The content registration unit 1 includes a registration / release operation receiving unit 11 that receives content registration / release, a content management table 13 that manages the registration status (for example, file name and identification ID) of content in the system, and content management thereof. A content management unit 12 for registering / releasing content to / from the table 13 and a file type notification unit 14 for determining the file type of the content when the content is registered and notifying the linked component management unit 2 Is done. By registering the content in the content registration unit 1, the browser unit 3 can display and play the content.

  FIG. 3 is a diagram showing a configuration of the cooperation component management unit 2 according to the embodiment of the present invention. The link component management unit 2 receives the file type of the newly registered content from the link component DB 23 that manages the link component corresponding to each file type and the file type notification unit 14 of the content registration unit 1, and sets the file type as the file type. From the component search unit 21 that searches for a corresponding link component from the link component DB 23, the link component searched by the component search unit 21 is acquired from the link component DB 23, and the link component is transmitted from the component distribution unit 22 that transmits the link component to the browser unit 3. Composed.

  FIG. 4A is a diagram showing a configuration of the HTML document cooperation component 5 and the HTML document media viewer 7 according to the embodiment of the present invention. The HTML document cooperation component 5 receives event information of an event that has occurred in the content from the HTML document media viewer 7 displaying the content, and based on the cooperation script 51, obtains an event name and event data from the received event information. Event reception unit 52 to be acquired, event / method conversion unit 54 that converts the acquired event name into a linkage method based on the linkage rule 53, identification of the HTML document 73 in the event data, linkage method, and linkage metadata acquired earlier Create a cooperation message describing the ID (stored in the content ID 50), receive the cooperation message transmission unit 56 to be transmitted to the inter-component communication unit 4, and the cooperation message transmitted from the inter-component communication unit 4, and describe in the cooperation message It has been The cooperative message receiving unit 57 for acquiring the event data, the cooperative method, and the cooperative metadata, the method / function converter 58 for converting the cooperative method name in the cooperative message into the control function name based on the cooperative rule 53, and the cooperative script 51 are also included. In addition, an external control execution unit 59 that executes the control indicated by the control function name acquired by the media / function conversion unit 58 using the event data acquired by the metadata processing unit 55 as an argument. 73, the metadata 75 associated with the event data in the event information (cooperation metadata) is acquired, and when the cooperation message is received, the metadata 75 possessed by the HTML document 73 is searched for cooperation. Detect event data or linkage metadata in the message Composed of metadata processing unit 55 for acquiring the event data described in the corresponding section.

  The HTML document media viewer 7 receives an event output unit 71 that transmits an event generated on the content to the outside, and an event input unit 72 that receives control information from the outside and executes processing indicated by the control information on the content. Are provided in advance. The HTML document 73 includes data 74 of the content itself, and metadata 75 that is supplementary information for the data 74. At this time, the metadata 75 can be written in addition to being read from the outside.

  FIG. 4B is a diagram showing the configuration of the video content cooperation component 6 and the video content media viewer 8 according to the embodiment of the present invention. The configuration and functions of each unit are the same as those of the HTML document cooperation component 5 and the HTML document media viewer 7 except that the target is video content.

  FIG. 5A is a diagram showing a configuration of the metadata processing unit 55 according to the embodiment of the present invention. The metadata processing unit 55 refers to the metadata 75 possessed by the content 73, acquires metadata (cooperative metadata) corresponding to the event data in the event information, and transmits the metadata to the cooperative message transmission unit 56. By referring to the reference unit 551 and the metadata 75 possessed by the content, the metadata 75 is searched for event data in the cooperation message received by the message reception unit 57 or a part where the cooperation metadata is described. A metadata collation unit 552 that acquires event data described in a corresponding portion of the data 75, and a metadata that additionally records the cooperation metadata in the received cooperation message as metadata of the event data acquired by the metadata collation unit 552. Data editing unit 553 and the received cooperation message from other content If it is, the metadata 75 (reference metadata) for the event data acquired by the metadata matching unit 552 is acquired by referring to the metadata 75, and is described in the related metadata and the received cooperation message. A reply message creation unit 554 that creates a reply message describing the event data and the identification ID of the transmission source content and transmits the reply message to the cooperative message transmission unit 56 is configured.

  FIG. 5B is a diagram illustrating a configuration of the metadata processing unit 65 in the video content cooperation component 6. The configuration and the function of each unit are the same as the metadata processing unit 55 in the HTML document cooperation component 5 except that the target is video content.

  FIG. 6 is a diagram showing a configuration of the inter-component communication unit 4 according to the embodiment of the present invention. The inter-component communication unit 4 determines whether the cooperation message transmitted from the HTML document cooperation component 5 and the video content cooperation component 6 or the message reception unit 41 that receives a reply message, and whether the received message is a cooperation message or a reply message. In the case of a cooperative message, the content management table 13 of the content registration unit 1 is referred to obtain information on each content currently registered in the system. In the case of a reply message, it is described in the reply message. The content ID acquisition unit 42 that acquires information related to the transmission source content of the cooperation message and the message transmission unit 43 that transmits a cooperation message or a reply message to the content indicated by each ID acquired by the content ID acquisition unit 42 Structure It is.

  Next, the operation of the system will be described. The operation of the system is realized by content registration, content linkage, metadata editing, reply message transmission / reception, after occurrence of a linkage operation, and deletion of postscript metadata.

≪Content registration≫
The content registration process will be described with reference to the flowchart of FIG. 7 using an HTML document and video content as examples. First, as shown in FIG. 8A, the content registration unit 1 drops an HTML document file icon on the desktop of the system into the window of the browser unit 3 so that the HTML document file is stored in the system. be registered. (Step S101). In addition, as a method for canceling registration of content in the system, for example, a method of instructing a file name or URL (Uniform Resource Locator) of the content using a dialog may be considered.

  Next, the content registration unit 1 shown in FIG. 2 receives registration of the HTML document at the registration / cancellation operation reception unit 11, and then the content management unit 12 receives information (for example, file name and identification ID) about the HTML document. ) Is registered in the content management table 13 (step S102). The file type notification unit 14 determines the file type (“HTML”) of the HTML document, and notifies the linked component management unit 2 of the determined file type and the identification ID of the HTML document (step S103). Here, the file type of the content is determined by referring to the extension of the file name.

  In the linkage component management unit 2 shown in FIG. 3, the component search unit 21 inquires the linkage component DB 23 for a linkage component corresponding to the file type (“HTML”) received from the file type notification unit 14, and the component distribution unit 22 The corresponding cooperation component, in this case, the HTML document cooperation component 5 is acquired (step S104). The identification ID of the HTML document received from the file type notification unit 14 is written in the acquired content ID of the linked component and transmitted to the browser unit 3 (step S105).

  In the browser unit 3, as shown in FIG. 8B, the HTML document cooperation component 5 received from the cooperation component management unit 2 is attached to the HTML document, and the HTML document is displayed using the HTML document media viewer 7. 3 is displayed (step S107). The actual processing of “granting” provides a logical path between the HTML document media viewer 7 displaying the HTML document and the HTML document cooperation component 5, and communication of messages and data between them is possible. (Step Sl06). Hereinafter, “grant” is used in the same meaning.

  Similarly, when the icon of the video content on the desktop is dropped in the window on the browser unit 3, the video content is displayed on the browser unit 3 through the same processing as the case of the HTML document described above. The video content cooperation component 6 is added to the video content.

≪Content collaboration≫
A process for linking an HTML document and video content will be described with reference to the flowcharts of FIGS. 9A and 9B as appropriate. In addition, A attached | subjected to the flowchart of Fig.9 (a) and FIG.9 (b) has shown that a process continues.

  First, as shown in FIG. 8B, a certain image (“Wcoat.gif”) in the HTML document is clicked (step S201). At this time, the event reception unit 52 of the HTML document cooperation component 5 shown in FIG. 4A performs event information (“OnClick (Wcoat.gif)”) generated on the HTML document media viewer 7 as shown in FIG. Is obtained from the event output unit 71 (step S202), and the event name (“Click”) and event data (“Wcoat.gif”) are obtained from the event information based on the cooperation script 51 (step S203). The linkage script shown in FIG. 10 describes a method for acquiring an event name (ENname) and event data (EDdata) from received event information (OnClick ()) as a method for processing event information.

  Next, as shown in FIG. 11, the event / method conversion unit 54 refers to the cooperation rule 53 and converts the event name (“Click”) into the cooperation method name (“Search”) (step S204). Here, in the cooperation rule shown in FIG. 11, an event name to be processed in the event element, a cooperation method name in which a cooperation message is described in the method element, and a control function name to be executed as a cooperation operation in the action element are described.

  Then, the metadata reference unit 551 of the metadata processing unit 55 refers to the metadata 75 held in the HTML document and acquires metadata (cooperative metadata) corresponding to the event data (“Wcoat.gif”) ( Step S205). Here, as shown in FIG. 12, “white coat, company A” is acquired. In FIG. 12, the metadata describes the corresponding metadata (Ometa) for each event data (eventD) acquired from the event information. Here, a plurality of metadata can be described for one event data.

  Next, in the cooperation message transmission unit 56, the event data (“Wcoat.gif”) acquired by the event reception unit 52, the cooperation method (“Search”) acquired by the event / method conversion unit 54, and the metadata processing unit 55 A cooperation message (“Search, Wcoat.gif, white” describing the identification ID (“shop.html”) of the HTML document stored in the content ID 50 in the obtained cooperation metadata (“white coat”, “A company”). (Coat, Company A, shop.html) is created and transmitted to the inter-component communication unit 4 (step S206) The event data, linkage method, linkage metadata, and identification ID described in the linkage message are as claimed. This corresponds to an example of “data” described in the range.

  In the inter-component communication unit 4, the message reception unit 41 receives the cooperation message transmitted from the HTML document cooperation component 5, and the received message indicates whether the message received by the content ID acquisition unit 42 is a cooperation message or a reply message. Is determined based on the format (step S207). Here, since the received message is a linkage message, the content ID acquisition unit 42 refers to the content management table 13 of the content management unit 1 and refers to all content currently registered in the system (here, HTML document and video content). ) Is acquired (step S208). Then, the message transmission unit 43 transmits a cooperation message to the cooperation components (here, the HTML document cooperation component and the video content cooperation component) assigned to the acquired contents of all identification IDs (step S209). The processing when the received message is a reply message will be described later.

  In the HTML document cooperation component 5 in FIG. 4A, the message reception unit 57 receives the cooperation message transmitted from the inter-component communication unit 4, and the cooperation method (“Search”) described in the cooperation message, Event data (“Wcoat.gif”) and cooperative metadata (“white coat, company A”) are acquired. Next, the metadata matching unit 552 of the metadata processing unit 55 searches the metadata 75 (see FIG. 12) held in the HTML document, and the event data acquired by the message receiving unit 57 in the metadata 75, Alternatively, a place where the cooperation metadata is described is searched (step S210). Then, when the described location is detected, event data described in the detected location is acquired (step S211). Here, since the HTML document is the source content of the cooperative message, the location referred to when the cooperative message is transmitted is detected, and “Wcoat.gif” is acquired. At this time, if the metadata 75 does not detect the location where the event data or the linkage metadata is described, the process ends.

  Next, as shown in FIG. 11, the method / function conversion unit 58 converts the cooperation method name (“Search”) acquired by the message reception unit 57 into the control function name (“Search”) based on the cooperation rule 53. Conversion is performed (step S212). Then, as shown in FIG. 10, the external control execution unit 59 uses the event data (“Wcoat.gif”) acquired by the metadata processing unit 55 based on the cooperation script 51 as an argument to the media / function conversion unit. The control (“funcSearch (“ Wcoat.gif ”)”) indicated by the control function name (“Search”) acquired in 58 is executed (step S213). Thereafter, the event input unit 72 of the HTML document media viewer 7 receives the control information and executes a process indicated by the control information. Here, as shown in FIG. 8C, the character string “Wcoat.gif” described in the content 73 is searched for and highlighted (step S214).

  Similarly, in the video content cooperation component 6 of FIG. 4B, the message reception unit 67 receives the cooperation message transmitted from the inter-component communication unit 4, and the cooperation method (“Search” described in the cooperation message is received. "), Event data (" Wcoat.gif "), and linked metadata (" white coat, company A "). Next, the metadata matching unit 652 of the metadata processing unit 65 searches the metadata 85 (see FIG. 13) held by the video content, and the event data acquired by the message receiving unit 67 in the metadata 85, Alternatively, a place where the cooperation metadata is described is searched (step S210). Then, when the described location is detected, event data described in the detected location is acquired (step S211). Here, in the metadata 85, a location where the linked metadata “white coat” is described is detected, and event data “20.0” of the detected location is acquired.

  Next, as shown in FIG. 14, the method / function conversion unit 68 converts the cooperation method name (“Search”) acquired by the message reception unit 67 into the control function name (“Play”) based on the cooperation rule 63. Conversion is performed (step S212). Then, as shown in FIG. 15, the external control execution unit 69 uses the event data (“20.0”) acquired by the metadata processing unit 65 based on the cooperation script 61 as an argument to the media / function conversion unit. The control (“funcPlay (20.0)”) indicated by the control function name (“Play”) acquired in 68 is executed (step S213). Thereafter, the event input unit 82 of the video content viewer 8 receives the control information and executes the process indicated by the control information (step S214). Here, the video content 83 is reproduced from 20 sec. For example, as shown in FIG. 8C, an actor A wearing a white coat is shown in the 20 sec scene.

≪Edit metadata≫
Metadata editing that is performed when a cooperation message is received will be described. The metadata editing is performed by the metadata processing unit of the HTML document cooperation component 5 or the video content cooperation component 6 in the above-described metadata cooperation.

  First, in the HTML document cooperation component 5, the metadata for the event data (“Wcoat.gif”) acquired by the metadata collation unit 552 of the metadata processing unit 55 searching for the metadata 75 (see FIG. 12) of the HTML document. In the data, the cooperation metadata (“white coat, company A”) in the received cooperation message is added. For example, in FIG. 12, since both of the linked metadata (“own court, company A”) are already described in the metadata 75, the linked metadata is not added and the process ends.

  Similarly, in the video content linkage component 6, the metadata collation unit 652 of the metadata processing unit 65 searches the metadata 85 (see FIG. 13) of the video content, and the event data (“ As the metadata for 20.0 "), the cooperation metadata (" White Coat, Company A ") in the received cooperation message is added. For example, in FIG. 13, “A company”, which has not yet been described, is added as new metadata (Ameta in FIG. 16) among the linked metadata (“white coat, A company”) (see FIG. 16) and updated. In the time field (time in FIG. 16), the added date and time are entered.

  By adding the metadata as described above, the union of the metadata conventionally given to the HTML document and the metadata described in the received cooperation message can be made new metadata. However, the metadata held by the content only increases indefinitely only by the cooperation of metadata as described above. Therefore, the time when the metadata was added is entered, and the metadata is deleted based on this time. The details of the process for deleting the postscript metadata using time will be described later.

≪Send and receive reply message≫
FIG. 17A and FIG. 17B are used for the processing of sending a reply message accompanying the reception of the cooperation message and the processing when the cooperation component of the cooperation message transmission source receives the reply message. I will explain. In addition, B attached | subjected to the flowchart of Fig.17 (a) and FIG.17 (b) has shown that a process continues.

  First, in the metadata processing unit 55 of the HTML document cooperation component 5, the reply message creation unit 554 identifies the content ID (described in the cooperation message) of the cooperation message received by the message reception unit 57 and the self content. The ID (stored in the content ID 50) is queried (step S301). Here, both the identification ID of the cooperative message and the identification ID of the self-content are the identification ID of the HTML document 73, that is, since the source of the received cooperative message is itself, the reply message is not transmitted. The process ends (step S302).

  On the other hand, in the metadata processing unit 65 of the video content cooperation component 6, the reply message creation unit 654 identifies the content ID (HTML document identification ID) of the cooperation message received by the message reception unit 67 and the own content. An ID (video content identification ID) is queried (step S301). Here, since the identification IDs are different, that is, since the received cooperative message is transmitted from another cooperative component, the process moves to a reply message creation process.

  First, the metadata 85 is searched, and metadata (“actor A, white coat”) for the event data (“20.0”) acquired by the metadata matching unit 652 is acquired (step S303). Next, the acquired metadata (hereinafter referred to as related metadata), event data (“Wcoat.gif”) described in the received cooperation message, and an identification ID (“shop.html”) of the transmission source content A reply message (“Wcoat.gif, actor A, white coat, shop.html”) is created and transmitted to the cooperative message transmitter 66 (step S304).

  Next, the cooperation message transmission unit 66 creates a reply message in which the identification ID (“movie.avi”) of the video content stored in the content ID 60 is described in the reply message acquired from the metadata collation unit 652. The data is transmitted to the inter-component communication unit 4 (step S305).

  In the inter-component communication unit 4, the message reception unit 41 receives the reply message transmitted from the video content cooperation component 6, and whether the message received by the content ID acquisition unit 42 is a cooperation message or a reply message is formatted in the received message. A determination is made based on (step S306). Here, since the received message is a reply message, the content ID acquisition unit 42 acquires the identification ID (here, the identification ID of the HTML document) of the source content of the cooperation message described in the reply message ( Step S307). Then, the message transmission unit 43 transmits a reply message to the cooperation component (here, the HTML document cooperation component) given to the content of the acquired identification ID (step S308). Here, unlike the case where the cooperation message is transmitted to all the registered contents, the reply message is transmitted only to the transmission source content of the cooperation message.

  In the HTML document cooperation component 5, the message reception unit 57 receives the reply message transmitted from the inter-component communication unit 4, and determines whether the received message is the cooperation message or the reply message in the format of the received message. And determine. If the received message is a reply message, event data (“Wcoat.glf”) and related metadata (“actor A, self-coat”) described in the reply message are acquired, and the metadata processing unit 55 Is transmitted to the metadata editing unit 553 (step S309).

  Next, in the metadata editing unit 553 of the metadata processing unit 55, the part in which the event data received from the message receiving unit 57 in the metadata 75 is described, in this case, the eventD element is the part of “Wcoat.gif”. The related metadata ("Actor A, white coat") received from the message receiving unit 57 is added to the message.Here, among the related metadata, "Actor A", which has not yet been described, is added as new metadata ( 18), for example, the date and time of addition are written in the update time field (time in FIG. 18) (step S310). This is the same as editing metadata in, and has been added to HTML documents by adding metadata. And over motor, the union of the once was metadata described in conjunction message received, it can be a new metadata.

  Here, unlike the cooperation message, the reply message does not include the cooperation method. For this reason, when the reply message is received, processing in the metadata collation unit 552 does not occur. For this reason, processing in the external control execution unit 59 does not occur, and content control associated with reception of a reply message, that is, cooperative operation does not occur. Further, the processing in the reply message transmission unit 554 does not occur, and the reply message is not transmitted again when the reply message is received. This is important in the sense of avoiding an infinite loop of processing.

≪Process after cooperation≫
After the cooperative operation between the HTML document and the video content, the audio content to which the metadata as shown in FIG. 19 is newly displayed on the browser unit 3 and the cooperative operation is performed, particularly the above-described processing The differences are described in detail below.

  For example, when an image (“Wcoat.gif”) in an HTML document is clicked again for a new linkage operation, the HTML document linkage component uses existing metadata (hereinafter, existing metadata, Ometa in FIG. 18). In addition, the metadata added in the previous cooperation operation (hereinafter referred to as additional metadata, Ameta in FIG. 18) is also described in the cooperation message. That is, a cooperation message describing “Search, Wcoat.gif, white coat, company A, actor A, Shop.html” is transmitted.

  Upon receiving this, the audio cooperation component finds “actor A” in the cooperation message as metadata of the event data “10.00” in the content, and reproduces the audio from, for example, 10.00 seconds (FIG. 19). reference). Further, as metadata of the event data “10.00”, cooperation metadata in the cooperation message, here “white coat, company A” is added. Further, a reply message describing the metadata “actor A” of the event data “10.00” as related metadata is transmitted to the HTML document. Here, if an attempt is made to cooperate with the audio content before cooperation with the video content, the HTML document content does not have “actor A” as metadata, and therefore cannot cooperate with the audio content. On the other hand, after the linkage with the video content, “actor A” is acquired as new metadata by the linkage with the video content, so that the linkage with the audio content becomes possible as described above. .

  On the other hand, in the video content cooperation component, the existing metadata (Ometa in FIG. 16) and the postscript metadata (Ameta in FIG. 16) are collated with the event data and the cooperation metadata in the cooperation message. Here, “white coat, actor A, company A” in the cooperation message is found as metadata of the event data “20.0”, and the video is reproduced from 20 seconds. At this time, when the additional write metadata is used in the cooperation operation, the update time of the additional write metadata is updated. Here, the update time of “Company A” is updated. As a result, the update time of the postscript metadata is updated every time it is used in the cooperative operation.

  Also, the HTML document linkage component receives a reply message describing “Actor A” as related metadata from the audio content linkage component, and “white coat, actor A, company A” as related metadata from the video content linkage component. Received as a written reply message. Then, the related metadata in the received reply message is added as new metadata. At this time, if the metadata to be added is already described as the additional metadata, the update time of the additional metadata is updated. Here, the update time of “Actor A” is updated. Here, reply messages are received from both audio content and video content, but each reply message is processed individually, and the update time of “actor A” is updated each time.

≪Deleting postscript metadata≫
Separately set the retention period for postscript metadata, and when creating a linked message or receiving a linked message, calculate the lower limit of the update time from the time and retention period at that time, and among the metadata held by the content, Delete additional metadata that is older than the lower limit calculated by the update time. By doing so, it is possible to automatically delete postscript metadata that has not been used for a certain period of time, thereby enabling efficient management of the metadata. In addition to the above, the timing of deleting the postscript metadata can be considered when a reply message is created or when a reply message is received.

  In addition, when the additional metadata is deleted, when the number of metadata held by the content, especially the number of additional metadata, is managed separately and exceeds the preset number, the additional metadata with the oldest update time It is possible to delete the data in order.

  As described above, in the present embodiment, cooperation with various types of content is realized by dynamically increasing the metadata held by each content by cooperation between the contents. Furthermore, for metadata added with linkage, the update time is managed, and the metadata that has not been used for a certain period of time is automatically deleted, so that the metadata can increase without limit in association with the linkage operation. And manage metadata efficiently.

  The metadata management method in the content cooperation system according to the embodiment of the present invention can be realized by a program on a computer, and can be provided by recording the program on a computer-readable recording medium. Is possible. It is also possible to provide the program through a network.

In the present embodiment, the HTML document and the video are mainly taken up as the content, and the HTML document media viewer, the video content media viewer, the HTML document linkage component, and the video content linkage component are described. The present invention is not limited to this, and can be realized with contents such as voice and text. At that time, the media viewer and the linking component are also suitable for contents such as voice and text.
[Second Embodiment]

In the first embodiment, by explicitly acting on the content, linkage between the content and accompanying increase in metadata occurred, but an event that occurs on the content without being acted on, for example, video content Due to changes in video time, etc., it is possible to generate new linkage between contents and accompanying increase in metadata. Furthermore, a change in content caused by a linkage operation between contents can cause a new linkage between contents and an accompanying increase in metadata.
[Third embodiment]

In the first embodiment, the metadata held by each content is automatically increased along with the cooperation between the contents. However, it may be possible to ask the user separately whether to increase the metadata. For example, before the reply message creation / transmission process and metadata editing process with the occurrence of cooperation, use the dialog to determine whether the content of the generated cooperation is appropriate or inappropriate for each content. Contact the user. Only when the user determines that it is appropriate, metadata editing processing and reply message creation / transmission processing are performed. By doing so, an increase in metadata reflecting the user's intention is realized, and the cooperation between contents can be made more meaningful.
[Fourth Embodiment]

  In the first embodiment, when an event occurs on the content, the metadata held by the content is referred to, and the metadata for the generated event data is acquired. At this time, if there is no description of the generated event data in the metadata possessed by the content, only the event data is described in the cooperation message, and the cooperation metadata is empty. In this way, if the content receives this linkage message, collates with the metadata owned by the content, and can find a description that matches the event data in the metadata, the linkage operation can be executed normally. it can. However, after that, when a reply message is received from the content in which cooperation has occurred, the metadata cannot be added because there is no description of the matching event data in the metadata possessed by itself.

  Therefore, as a fourth embodiment, when there is no description of the event data that has occurred in the metadata possessed by the content, the event data is dynamically described in the metadata, and the metadata held by the content Extend itself.

  For example, in FIG. 8C, when the character “white coat” is clicked and “white coat” is received as the event data, as shown in FIG. 20A, in the metadata of the HTML document content, , A new item having “white coat” in the event data (eventD element) is generated. Then, “white coat” is transmitted as event data, and a cooperation message with empty cooperation metadata is transmitted, for example, to the video content having FIG. 13 as metadata. After that, cooperation occurs in the video content, and a reply message describing “white coat” in the event data and “white coat, actor A” in the related metadata is received from the video content. At this time, in the HTML document, related metadata described in the reply message is added as metadata for the event data “white coat” described in the received reply message. At this time, in order to avoid duplication with the event data, the same related metadata as the event data, here, “white coat” is not described, and only “actor A” is added as metadata (FIG. 20 (b)).

In this way, when “white coat” is received as event data again, a cooperation message in which “white coat” is described in the event data and “actor A” is described in the cooperation metadata is transmitted. Therefore, the range of cooperation can be expanded. Further, by using this embodiment, it is possible to realize creation and extension of the metadata itself possessed by the content through a content cooperation operation. That is, it is possible to reduce the time and effort for the content creator to create the metadata and to create various metadata.
[Fifth Embodiment]

  In the first embodiment, when a new collaborative operation occurs after the metadata possessed by the content increases in association with the collaborative operation, the existing metadata (Ometa in FIGS. 16 and 18) is added to the added metadata. Data (Ameta in FIGS. 16 and 18) was handled equally, but effective collaboration between contents is realized by distinguishing the two.

  This is because the existing metadata is given by the content creator and is therefore highly relevant to the event data. On the other hand, additional metadata is not necessarily highly related to event data as a result of being randomly added in association with a cooperative operation. For this reason, even if cooperation occurs due to the postscript metadata, there is a high possibility that the cooperation itself is completely misplaced. In addition, when adding metadata in association with the occurrence of linkage, if additional metadata is added to the content in which linkage has occurred as well as existing metadata, if the additional metadata itself has low relevance In addition to adding unnecessary metadata, there is a problem that metadata with low relevance increase in a chain.

  Therefore, in the fifth embodiment, as will be described later, by limiting the use of the additional metadata, it is possible to increase the probability that the cooperation will occur due to the presence of the additional metadata while maintaining the accuracy of the cooperation. .

  For example, when creating / transmitting a cooperation message, only existing metadata is described, and additional metadata is not described. The additional write metadata is used only when searching for event data in the cooperation message or metadata matching the cooperation metadata when the cooperation message is received. In particular, the existing metadata is queried first, and the additional metadata is queried only when there is no match in the existing metadata. By doing in this way, it is possible to prevent the cooperation that is different from the examination from occurring due to the postscript metadata.

In addition, when creating / transmitting a reply message, only the existing metadata for the event data used in the cooperation operation is described as related metadata, and the additional metadata is not described. Furthermore, in the linkage operation, if the event data in the received linkage message or the metadata that matches the linkage metadata is not found in the existing metadata but only in the postscript metadata, and the linkage operation is executed, Do not send a reply message. By doing so, it is possible to prevent useless metadata from being added and to prevent an increase in the number of metadata with low relevance.
[Sixth Embodiment]

  In the first embodiment, it is assumed that metadata possessed by content can be referred to and written. However, when considering cooperation with content created by a third party, it may be difficult to write to metadata held in the content. Therefore, in the present embodiment, as shown in FIG. 21, a metadata management database 9 is newly introduced into the system, the metadata possessed by the content is copied into the metadata management database, and the copied metadata is copied. By referencing and writing, it is possible to link with content created by a third party. In the following, processing newly generated with the introduction of the metadata management database 9 will be described with reference to FIG.

  First, registration of a copy of metadata possessed by content in the metadata management database 9 is performed by content registration in the system in the content registration unit 1 (step S102 in FIG. 7). For example, the metadata of the registered content is referred to and a copy thereof is generated in the metadata management database 9. Thereafter, information (file name, URL, etc.) related to the content and ID (identification number, address, etc.) of the copied metadata in the metadata management database 9 are registered in the metadata management table 91.

  Next, the deletion of the copy of the metadata from the metadata management database 9 is performed by releasing the content to the system in the content registration unit 1. For example, first, the content metadata management table 91 is referred to, and the ID of the corresponding metadata (copy) in the metadata management database 9 is acquired based on the file name of the content. Then, the metadata (copy) indicated by the ID is deleted, and the corresponding part is deleted from the content metadata management table 91.

  Here, it is conceivable that the metadata (copy) in the metadata management database 9 is not deleted but kept stored when the content is released in the system. Then, when the same content is registered in the system again, the stored metadata is used. By doing in this way, it becomes possible to use the metadata added with cooperation operation collectively, and cooperation with various contents becomes possible.

  Lastly, it is a process when referring to and writing content metadata when linking content questions, sending and receiving reply messages, editing metadata, and deleting metadata. This is linked to each content. When adding a component, the identification ID of the corresponding metadata (copy) in the metadata management database 9 is written together with the identification ID of the content (step S105 in FIG. 7). Then, when referring to and writing metadata, it is realized by accessing the metadata (copy) in the metadata management database 9 indicated by the metadata identification ID, not the metadata held by the content.

  Note that the metadata management database 9 is not limited to the content cooperation system, and may be outside the content cooperation system and thus on the network.

It is a figure which shows the structure of the content cooperation system which concerns on embodiment of this invention. It is a figure which shows the structure of the content registration part which concerns on embodiment of this invention. It is a figure which shows the structure of the cooperation component management part which concerns on embodiment of this invention. (A) is a figure which shows the structure of the HTML document cooperation component which concerns on embodiment of this invention, and an HTML document media viewer. (B) is a figure which shows the structure of the video content cooperation component which concerns on embodiment of this invention, and a video content media viewer. (A) is a figure which shows the structure of the metadata process part in the HTML document cooperation component which concerns on embodiment of this invention. (B) is a figure which shows the structure of the metadata process part in the video content cooperation component which concerns on embodiment of this invention. It is a figure which shows the structure of the communication part between components which concerns on embodiment of this invention. It is a flowchart which shows the process which registers an HTML document. (A) is a conceptual diagram showing that an HTML file is registered in the system when an icon of the HTML file on the desktop of the system is dropped in the window of the browser unit. (B) is a conceptual diagram showing that an image in an HTML document is clicked. (C) is a conceptual diagram showing an example of processing executed by the HTML document media viewer. (A) (b) is a flowchart which shows the process which cooperates an HTML document and a video content. It is a conceptual diagram which shows the example of the cooperation script in an HTML document cooperation component. It is a conceptual diagram which shows the example of the cooperation rule in an HTML document cooperation component. It is a conceptual diagram which shows the example of the metadata in an HTML document. It is a conceptual diagram which shows the example of the metadata in video content. It is a conceptual diagram which shows the example of the cooperation rule in a video content cooperation component. It is a conceptual diagram which shows the example of the cooperation script in a video content cooperation component. It is a conceptual diagram which shows the example of the metadata after edit in a video content. (A) (b) is a flowchart which shows the process of transmission / reception of a reply message. It is a conceptual diagram which shows the example of the metadata after edit in an HTML document. It is a conceptual diagram which shows the example of the metadata in audio | voice content. It is a conceptual diagram which shows expansion of metadata. It is a conceptual diagram which shows introduction of a metadata management database.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 Content registration part 11 Registration / cancellation operation receiving part 12 Content management part 13 Content management table 14 File type notification part 2 Cooperation component management part 21 Component search part 22 Component distribution part 23 Cooperation component database (DB)
DESCRIPTION OF SYMBOLS 3 Browser part 4 Inter-component communication part 41 Message receiving part 42 Content ID acquisition part 43 Message transmission part 5 HTML document cooperation component 51 Cooperation script 52 Event reception part 53 Cooperation rule 54 Event / method conversion part 55 Metadata processing part 551 Metadata Reference unit 552 Metadata collation unit 553 Metadata editing unit 554 Reply message creation unit 56 Cooperation message transmission unit 57 Cooperation message reception unit 58 Method / function conversion unit 59 External control execution unit 6 Video content cooperation component 61 Cooperation script 62 Event reception unit 63 Coordination rules 64 Event / method conversion unit 65 Metadata processing unit 651 Metadata reference unit 652 Metadata collation unit 653 Metadata editing unit 654 Reply message Creation unit 66 Cooperation message transmission unit 67 Cooperation message reception unit 68 Method / function conversion unit 69 External control execution unit 7 HTML document media viewer 71 Event output unit 72 Event input unit 73 HTML document 74 Data 75 Metadata 8 Video content media viewer 81 Event output part 82 Event input part 83 HTML document 84 Data 85 Metadata 9 Metadata management database (DB)
91 Metadata management table

Claims (18)

In a content collaboration system that realizes collaboration between content by sending and receiving messages,
Equipped with multiple linkage components that send and receive linkage messages and reply messages, and fill in metadata.
A metadata management method for managing metadata attached to content,
A procedure in which the first linkage component transmits a linkage message describing the first data of the first content to the second linkage component;
The second collaboration component assigns the first data of the first content described in the collaboration message received from the first collaboration component to the second content. The procedure to fill it out separately from the data,
The second linkage component uses the second content related to the first data of the first content described in the linkage message received from the first linkage component as the second content. A procedure for acquiring from the second metadata attached to the first metadata, filling in a reply message, and transmitting to the first linkage component;
The first linkage component enters the second data described in the reply message received from the second linkage component separately from the first metadata attached to the first data. A metadata management method characterized by executing the following steps: In the cooperation message transmitted by the first cooperation component,
Filling in metadata corresponding to the first event data of the event that occurred in the first content;
The second linkage component searches the second metadata assigned to the second content for a location that matches the first event data or the metadata in the received linkage message. The metadata management method according to claim 1 , wherein the second content is controlled based on second event data described in the detected location. The metadata described in the cooperation message received by the second cooperation component is used as metadata corresponding to the second event data used when controlling the second content. The metadata management method according to claim 1 or 2 , wherein data is entered. When the second cooperative component controls the first event data described in the cooperative message received from the first cooperative component and the second content in the reply message to be transmitted. Filling in the metadata corresponding to the second event data,
The first cooperation component writes the metadata described in the received reply message in the first metadata as metadata corresponding to the first event data described in the reply message. metadata management method according to any one of claims 1 to 3, characterized in. When the first metadata described in the cooperation message received by the second cooperation component is not written in the second metadata attached to the second content, the first metadata Enter the date and time when the metadata of 1 was entered in the second metadata,
When the second metadata described in the reply message received by the first cooperation component is not written in the first metadata attached to the first content, the second metadata Enter the date and time when the metadata of 2 was entered in the first metadata,
The first metadata is already written in the second metadata, or the second metadata is already written in the first metadata,
If the date and time entered is before the specified date and time,
Delete the first metadata or the second metadata that has already been entered,
If the date and time entered is later than the specified date and time,
Updating the date and time of entry to the date and time when the first metadata or the second metadata is newly entered;
Metadata management method according to any one of claims 1 to 4, characterized in. Deletion of the first metadata or the second metadata is
6. The method of managing metadata according to claim 5 , wherein when the number of metadata exceeds a predetermined value, the entered date and time are executed from old metadata. Display means for inquiring whether to execute entry of the first data in the second metadata and transmission of the reply message based on the cooperation message received by the second cooperation component Display using
Instruction to be executed, only when it is input through the input means, the fill, and the metadata management according to any one of claims 1 to 4, characterized in that to perform said transmission Method. When the first event data or the second event data is not described in the first metadata or the second metadata assigned to the first content or the second content in the first event data or the second event data, said the first metadata or the second metadata of claims 1 to 4, characterized in that to fill dynamically The metadata management method according to any one of the above. The newly entered first metadata or the second metadata is distinguished from the existing first metadata or the second metadata, and the newly entered first metadata. metadata management method according to any one of claims 1 to 4, characterized in that to limit the data or the second metadata applications A metadata management database for managing a copy of the first metadata or the second metadata assigned to the first content or the second content;
When the first linkage component or the second linkage component refers to or writes the first metadata or the second metadata assigned to the first content or the second content the metadata management method according to any one of claims 1 to 9, characterized in that utilizing the first metadata or the copy of the second metadata in the metadata management database . In a content collaboration system that realizes collaboration between content by sending and receiving messages,
Equipped with multiple linkage components that send and receive linkage messages and reply messages, and fill in metadata.
A metadata management device that manages metadata attached to content,
Transmitting the cooperation message describing the first data of the first content to the second cooperation component; and sending the second data described in the reply message received from the second cooperation component A first linkage component that performs distinction and entry from the first metadata assigned to one data;
Entering the first data of the first content described in the cooperation message received from the first cooperation component separately from the second metadata assigned to the second content; The second data related to the first data of the first content described in the cooperation message received from the first cooperation component is added to the second content. 2. The metadata management apparatus comprising: the second cooperation component that is obtained from the second metadata, fills in the reply message, and transmits the reply message to the first cooperation component. The first linkage component that fills in the linkage message with metadata corresponding to first event data of an event that has occurred in the first content;
The part where the first event data or the metadata is described in the received cooperation message is searched from the second metadata attached to the second content, and the detected part is The metadata management apparatus according to claim 11 , further comprising: the second cooperation component that controls the second content based on the second event data described. The metadata described in the received cooperation message is entered in the second metadata as metadata corresponding to the second event data used when controlling the second content. metadata management device according to claim 11 or claim 12, characterized in that it comprises a second linkage component. The first event data described in the cooperation message received from the first cooperation component and the metadata corresponding to the second event data used when controlling the second content, The second cooperation component filling in the reply message to be transmitted;
The first linkage component that fills the metadata described in the received reply message with the first metadata as metadata corresponding to the first event data described in the reply message. metadata management device according to any one of claims 11 to 13, characterized in. When the first metadata described in the received cooperation message is not entered in the second metadata attached to the second content,
Enter the date and time when the first metadata was entered in the second metadata,
The first metadata is already filled in the second metadata, and
If the date and time entered is before the specified date and time,
Delete the first metadata already filled in,
If the date and time entered is later than the specified date and time,
Updating the date and time of entry to the date and time when the first metadata is newly entered; and
When the second metadata described in the received reply message is not written in the first metadata attached to the first content,
Enter the date and time when the second metadata was entered in the first metadata,
The second metadata is already filled in the first metadata, and
If the date and time entered is before the specified date and time,
Delete the second metadata that has already been entered,
If the date and time entered is later than the specified date and time,
The date and time is entered as claimed in any one of claims 11 to 14, characterized in that it comprises a first linkage component for updating the date and time entered newly to said second metadata Metadata management device. A metadata management database for managing a copy of the first metadata or the second metadata assigned to the first content or the second content;
When referring to or writing the first metadata or the second metadata assigned to the first content or the second content, the first metadata in a metadata management database or metadata management device according to any one of claims 11 to 15, characterized in that it comprises a first linkage component or said second coordination components utilizing a copy of the second metadata . The metadata management program which performs the method as described in any one of Claims 1-10 . A computer-readable recording medium having recorded thereon a program for executing the method according to any one of claims 1 to 10.

Images