EP1062605A1 - Procede et systeme permettant d'enregistrer des oeuvres de l'esprit et de conceder des licences relatives a ces oeuvres sur un reseau - Google Patents

Procede et systeme permettant d'enregistrer des oeuvres de l'esprit et de conceder des licences relatives a ces oeuvres sur un reseau

Info

Publication number
EP1062605A1
EP1062605A1 EP00904328A EP00904328A EP1062605A1 EP 1062605 A1 EP1062605 A1 EP 1062605A1 EP 00904328 A EP00904328 A EP 00904328A EP 00904328 A EP00904328 A EP 00904328A EP 1062605 A1 EP1062605 A1 EP 1062605A1
Authority
EP
European Patent Office
Prior art keywords
rights
work
user
license
search
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Withdrawn
Application number
EP00904328A
Other languages
German (de)
English (en)
Inventor
Edward P. Murphy
Christopher Burns
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Harry Fox Agency Inc
Original Assignee
Harry Fox Agency Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Harry Fox Agency Inc filed Critical Harry Fox Agency Inc
Publication of EP1062605A1 publication Critical patent/EP1062605A1/fr
Withdrawn legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/10—Protecting distributed programs or content, e.g. vending or licensing of copyrighted material ; Digital rights management [DRM]
    • G06F21/105—Arrangements for software license management or administration, e.g. for managing licenses at corporate level

Definitions

  • This invention relates generally to a method and system for registering works of authorship in an online database and providing licensing information about registered works to individuals who access the online database; and more particularly to a method and system for registering works of authorship with several rights agencies, royalty collecting societies and copyright offices, and simultaneously entering the work into the online database.
  • the online database contains information about the licensing rights sources for various license rights in each territory of the world. Individuals can use the online database to identify a particular work of authorship from among many close variants, analyze the licensing rights necessary for a particular use of the work in a given territory, determine the source of the licensing right needed for their use and forward a request for a license to that source.
  • the method and system can issue a license to the individual for the particular use of a work in the particular territory desired.
  • a major licensing agency which may represent up to 17,000 publishers in the United States, could handle on average more than a thousand requests a day from individuals (or companies) requesting mechanical rights licenses to make mechanical reproductions of song recordings. Furthermore, with the growth of the Internet and online distribution of songs, that volume is expected to increase to 10,000 a day or more over the next few years. Unfortunately, individuals requesting mechanical rights may not know which agency represents a given publisher and may assume that it is a given major licensing agency even when it is not. In this case, that agency must expend resources dealing with requests for licenses of works it does not represent.
  • the Internet represents a new international distribution channel where as many as 100,000 sites are expected to use and distribute music. At the same time the use of music in other multimedia products and services is increasing. If obtaining the appropriate rights to use the music is not made significantly easier than it currently is, the volume of unlicensed distribution will likely increase, and the ability to protect the intellectual property rights of the authors will be in danger.
  • a system and method for easily determining which rights are necessary for a given use of a work which agencies or companies administer and grant those rights and that can format a request for that license right to the appropriate licensing rights sources easily.
  • Such a system would be accessible by publishers and rights sources for entering the appropriate information about a given work, and would be accessible by rights requestors who wished to license the works. Therefore, it is desired to provide an online, Internet based licensing system for accomplishing these goals.
  • a method and system for assisting individuals, recording companies, publishers, multimedia producers, Internet distributors and others in obtaining the appropriate rights to license a work of authorship easily, using an online system and database, and more particularly, a single World Wide Web site, is provided.
  • the Web site is accessible by works publishers who wish to register their works in the system of the invention, and works users who wish to identify and license a work.
  • the method and system of the invention provides an online, multimedia license, registration and tracking system for storing, retrieving and tracking licensing rights sources information, and for registering copyrights and the like for works of authorship in general; and for identifying and licensing multimedia works through the system.
  • the system may be used by multimedia publishers and licensor's to register, store and track multimedia works, and by perspective licensee's (such is CD manufactures, compilation producers and Internet download services) to retrieve information about licensing a multimedia work.
  • the system may be used by music publishers as a one step clearinghouse to enter data about a published musical work and forward in the relevant information to various licensing databases, such as the International Common Works Database (CIS) and registration databases, such as the U.S. Copyright Office at the Library of Congress.
  • Information about the musical work will also be stored in the centralized database of the invention in a digital representation of the work may be archived in the digital sound archive of the invention.
  • the system can send structured email messages containing information about the new work to other agencies, registration services or royalty rights collection societies.
  • a publisher may access to system to update all these databases from a single update screen.
  • a central component of the system of the invention is an Internet based works database which stores information about the work of authorship and includes information about which entities can grant particular licenses for any particular use of the work.
  • the information will generally include a worldwide licensor for each of mechanical rights, synchronization rights, Internet download rights, performance rights and master recording rights, and then list territorial exceptions, such as mechanical rights in Japan or the UK.
  • the information will be provided by the publisher of the work, but each licensing agency can update database records as well.
  • the system allows for online registration of single songs, multiple songs which are part of a single product (such as a cassette, a CD or a movie), and batch file registration allowing a large number of works to be imported using a single file transfer.
  • the system will provide links to additional information about the work provided by the registrant and an example of the work itself.
  • a person or company that wants to use or license a work can search the database over the Internet for the correct data record for that work of authorship, and that record will include information as to which licensing agency has the right to grant a license for the particular use.
  • a user searches for a work by selecting a field of search, such as the title of the work, the author of the work, the physical production of the work such as from a movie, or a book, and enters keywords in the search box. Results of the search are presented in a list, and when the user clicks on the desired title, information about that work is presented which will include which agencies license that work for any particular use in the given territory.
  • the invention includes several major components, each generally linked to a central database of works of authorship, called herein the "WorksDB. " Publishers and authors may enter new works in the WorksDB using a simplified works entry screen on their Internet browser. At the same time, the invention allows the registrant to register the work with the U.S. Copyright Office, with the International Common Works Database, and with other agencies and royalty collecting societies around the world. The invention allows interested users to identify a particular work of authorship by using a simplified look up screen on their Internet browser.
  • the WorksDB provides a searchable database of all copyrighted songs in the American or other repertoire so that the user can determine which work, which version and which arrangement he or she wishes to license.
  • the system of the invention can determine the rights required for a particular use of a particular work by analyzing responses from the requestor to questions presented on a simplified intended use screen shown to the requestor on their Internet browser.
  • the WorksDB service includes an expert system which identifies the usage being proposed and determines which rights are required in a given territory.
  • "moral rights” may also exist, permitting the author of a work to grant or withhold permission to use the work in any specific context. Sometimes several of the possible rights are required for a particular use.
  • the WorksDB service can identify which rights the user will require for the intended use.
  • the WorksDB also includes information about the identity of any particular licensing rights source. For example, different rights are administered by different publishers, agencies and collecting societies in different territories around the world, and individual works may have additional specific and unusual requirements. Based on the territory in which the work is to be produced and distributed, among other information stored in the WorksDB, the WorksDB service uses a data structure to determine which sources need to be contacted by the user to get all the rights that are required for the intended use. The system of the invention can preferably forward the request for a license to the appropriate rights source. Thus, the WorksDB service offers the user the ability to send all the necessary rights requests immediately to the correct licensing rights sources at once.
  • the system prompts the user for the necessary information, formats the request, determines the current address and preferred request format for each of the rights sources involved, and sends the request message to the correct agency. In most cases the message goes out by electronic mail with a copy to the user, but in other cases the request may go by fax or ordinary mail.
  • the system of the invention preferably logs the requests each user has made, and, with the participation of the rights sources, may track whether the request is answered or the license is issued. In a preferred embodiment of the invention, the system may issue a pro forma license, where appropriate. For agencies and publishers who request it, the WorksDB service will evaluate the rights application, assemble the appropriate clauses and conditions required in the license and determine what rate the user will be charged.
  • This pro forma license is forwarded to the requestor, with a copy to the publisher.
  • the requestor may respond to the agency, publisher or other rights source directly with their acceptance, or may contact the rights source through the WorksDB service in order to accept the terms of the pro forma license.
  • the WorksDB service is preferentially accessed over the Internet, and a preferred embodiment of the invention incorporates a central Web site providing links to the various functions, which is available free to all users around the world.
  • the WorksDB service is implemented as an Internet- based Licensing Service described in the attached Appendix 1.
  • the method and system of the invention benefits the licensing rights sources in at least two ways. It is estimated that more than a third of the license requests now received by the largest agencies and publishers cannot be processed either because the information is not complete or correct, or because that agency or publisher is not the appropriate rights source for the work being requested.
  • the WorksDB service eliminates the work associated with unprocessable requests by helping the user create a complete request in the first place, and by sending license requests to the correct licensing source in the second place.
  • the service also benefits the individuals and companies that wish to license a work of authorship.
  • the user of the WorksDB service can create and send a license rights request within minutes, and participating rights sources which incorporate automated licensing systems may respond in as short a time as three minutes.
  • the Internet and particularly the World Wide Web, makes it feasible for thousands of individual publishers and song writers to maintain their works information in a central directory, such as the WorksDB.
  • the WorksDB service takes advantage of this new capability by building and maintaining a system, a protocol, and an administration staff that keeps the database current and accurate.
  • the system and the method of the invention includes a works database containing information about works, including a unique work identifier and licensing sources for individual license rights in individual territories. It also includes means for determining a unique work identifier for a work to be licensed by a user and the appropriate license rights necessary for a particular use of the work in a particular territory. The system and method then matches the unique work identifier and the appropriate license rights for the territory in the database to determine the appropriate licensing sources and generates and transmits a license request to the licensing sources. Accordingly, it is an important object of this invention to provide an online works database accessible by authors or publishers for entering information about their works, including information about licensing rights sources in particular territories for those works, which works database is also accessible by users who wish to request license rights to a work.
  • Another object of the invention is to provide a means for determining the license rights necessary for a particular use of a work in a territory and generating and transmitting a license request to the appropriate licensing rights source; and preferably additionally provide means for generating a pro forma license for that use.
  • Yet another object of the invention is to provide means for registering a work with several international works databases or copyright offices at once by entering registration information about the work in the online works database.
  • Fig. 1 shows an interconnection block diagram depicting an overview of the WorksDB system, in accordance with an embodiment of the present invention
  • Fig. 2 shows a simplified account entry screen for the WorksDB system, in accordance with an embodiment of the invention
  • Fig. 3 shows a simplified work update or entry screen for the WorksDB system, in accordance with an embodiment of the invention
  • Fig. 4 shows a current rights sources screen for the WorksDB system, in accordance with an embodiment of the invention
  • Fig. 5 shows a rights sources modification screen for the WorksDB system, in accordance with an embodiment of the invention
  • Fig. 6 shows a search results table for the WorksDB system, in accordance with an embodiment of the invention
  • Fig. 7 shows a simplified rights request information screen for the WorksDB system, in accordance with an embodiment of the invention.
  • Fig. 8 shows a detailed right request information screen for the WorksDB system, in accordance with an embodiment of the invention.
  • FIG. 1 there is illustrated an interconnection block diagram depicting an overview of the WorksDB system in an embodiment of the invention.
  • the WorksDB system generally indicated at 100 includes several functional elements which may be accessed from a main page 105.
  • main page 105 may typically include a splash 110 or other graphic identifier, news 111 providing information about the status of WorksDB system 100, and optionally, advertisements 112 or other links.
  • Main page 105 includes links allowing a user to find a work of authorship, create a request to license a work of authorship and send it to a rights source, or register a new work.
  • the user When the user clicks the link to register a new work, the user is brought to a register page 115. As will be further described below with reference to Fig. 2, the user is prompted to provide an account ID 116 or, if unavailable, create a new account 117. A new account ID is sent to the user by email, which serves to confirm and verify the email address of the user. Once an account ID is established, the user may register a new work 118 or update the information of an existing work 119.
  • the WorksDB system 100 can forward information about the new work or the updated work to the WorksDB 120, other databases 121, a national copyright office 122 and a digital archive 123. Digital archive 123 contains a digital representation of the work provided by the user upon registration of that work and may also function as a deposit for copyright purposes.
  • Information about works of authorship in the WorksDB will generally include a unique identifier, identifier 126, the title of the work 127, any alternative titles 128, usage notes 129, authors 130, a show, movie or other place in which the work was featured 131, the publisher and catalog 132, and any international standard registry numbers 133 which may be appropriate.
  • a user searching for a particular work will typically enter some or only incomplete information in any given field, and will typically only provide a title 127, alternative title 128 or the show or movie in which the work was featured 131.
  • the WorksDB system 100 will return a work search result table, for example the work search result table of Fig. 6 displaying the results of a search for songs containing the word "God father" in its title. As shown in Fig. 6, additional information about the search result works is provided in the table to help the user find the exact song and version being looked for.
  • the work search result table also optionally includes links provided by the publisher or other entity that entered the work into the WorksDB system 100, to additional information, such as, in the example of musical works and songs, a sample of the work 134, information about the work from the publishers web site 135, a discography 136, the lyrics 137, and the score 138.
  • additional information such as, in the example of musical works and songs, a sample of the work 134, information about the work from the publishers web site 135, a discography 136, the lyrics 137, and the score 138.
  • not all entries in the work search result table will include links to each of these sources of further information.
  • different links to additional information will be appropriate.
  • a link providing information as to the exposure and camera equipment used, or to a thumbnail graphical image of the photograph may be provided. While many search techniques are well-known in the art and may be used in the system of the invention, it has been found that the searching design described in Appendix 2 is well-suited to meet the objectives.
  • the user may request a license for the work by clicking on the appropriate link and going to the request page 140. If available, the user can provide their user ID 141, or request a new user ID 142. The new user ID is forwarded to the user by email in order to verify and confirm the email address of the user.
  • a user ID is provided, the user it brought to a rights analysis page, as shown in Fig. 7 and described in further detail below.
  • the rights analysis page as shown in Fig. 7 will allow the user to select from a comprehensive list of rights appropriate to that work, the license rights to be requested 143 and provide other basic information about the use of the work. Depending on the rights requested, additional questions will be presented to the user seeking the information pertinent to the particular rights to be requested.
  • WorksDB system 100 also includes a license request assembly function which first identifies the appropriate rights required for the use intended by the user 150, and then identifies the appropriate sources for those rights 151.
  • WorksDB system 100 can transmit the license request to the licensing rights source 152 and store a record of the request 153 for confirmation and archival purposes.
  • WorksDB system 100 can use information generated by the request assembly function to create a pro forma license 154, determine the rate for that license 155 by reference to information in the WorksDB, send the pro forma license to the user 156 and a copy of the license request to the licensing rights source, and record the transaction 157 in the WorksDB.
  • WorksDB system 100 can provide the appropriate licenses to users who wish to use a work in a simple and efficient manner, in a minimal amount of time.
  • the license request can be sent to the licensing rights source and processed efficiently and without delay because WorksDB system 100 provides all of the information required by the licensing rights source in the request. While many techniques for accomplishing the above objectives will be apparent to those of ordinary skill in the art, one embodiment that is well-suited to provide this functionality is described with reference to Appendix 3.
  • Fig. 2 the simplified works registration is described. Any publisher or other works source with an account ID may register a work. The process requires the publisher to enter information about both the registering organization and the work. Once the work is registered in the WorksDB system, the publisher may choose to register the work with the U.S. Copyright Office as well as other agencies and rights collection societies at the same time. With reference to Fig. 3, the WorksDB system prompts the user to enter a common set of information required by the WorksDB and the CIS Common Works Database. If the user also wishes to register the work with the U.S. Copyright Office, or other registration agency, additional information elements may be required and presented on an additional screen.
  • Fig. 4 shows the default rights sources table for the top 20 music markets. Any entry in this table can be modified for a particular work by the registrant by clicking the change button. In this case, the registrant will be taken to a rights source change page, as shown in Fig. 5.
  • Any publisher may create a new song record in the WorksDB or add licensing rights sources information to the record of an existing work for which he represents 100% of the owners of that work.
  • all changes by any owner are automatically reported by the system to all other owners of that song, and the approval of each may be required before the changes are made.
  • the registrant may elect to send the new song information to other agencies and rights collection societies as well. If this option is elected, the system selects the information appropriate to that agency or society and sends the data as an email message. If appropriate, WorksDB system 100 can present a screen requesting additional information that may be requested by the other agency or rights collection society.
  • the WorksDB system creates and transmits an electronic copyright application directly to the CORDS system.
  • the application is conveyed electronically to the U.S. Copyright Office and any subsequent correspondence occurs exclusively between that office and the registrant as more fully described in Appendix 4.
  • the user may also deposit the work itself in electronic form in the digital archive of WorksDB system 100.
  • the digital copy of the work may consist of a recording in MP3, MIDI or another standard format, or it may be a text file of the lyrics and score.
  • the WorksDB system 100 digital archive includes a secure database of all song information as it is added or amended in order to provide participating publishers with a permanent audit trail of changes to the record.
  • the digital archive includes digital sound recordings submitted to the U.S. Copyright Office, or otherwise provided by the publisher, and may grow to become a major repository of digital music on the Internet.
  • WorksDB system 100 preferably uses public and private key encryption to certify that the registrant is authentic, and that the record of the registration or update of the song information is stored with a date/time stamp and digital signature in a secure format.
  • Publishers may register multiple songs in batches through a predefined transfer of files.
  • the format of that batch is typically as a spreadsheet, or any other data format that can be normally imported, such as txt, csv, or dbf.
  • the first row should include the name of the data element in that column.
  • the original registrant may retrieve a complete record of the information for a song as of that moment, as well as see a history of changes that may have occurred since the original registration.
  • the original registrant may modify this information and elect to have the WorksDB system send those modifications to other databases, agencies or rights collection societies.
  • a person or entity seeking the rights to a musical work may access WorksDB system 100 over the Internet.
  • the user must first identify the work specifically from a catalog of copyrighted works, derivative works and arrangements. Having identified the song from a list of similar titles or multiple arrangements, the system then uses the identifier 126 to access information and rights management instructions.
  • identifier 126 is incorporated into any rights agreement or license generated by participating publishers, and in the future may be used to manage royalty collections and distribution.
  • the user may search individual catalogs within WorksDB system 100, or search all catalogs at the same time.
  • the catalogs are created by WorksDB system 100 to separate very different groups of, for example, music, such as by national repertoires, theatrical productions and music libraries.
  • the user can search the file by writer, title or alternate title, show or movie in which the work appeared, or identifier 126 which is the primary key for each work.
  • WorksDB may be searched by International Standard Recording Code (ISRC) or CAE number, part of the international CIS system for identifying authors and composers.
  • ISRC International Standard Recording Code
  • CAE number part of the international CIS system for identifying authors and composers.
  • the user selects the field to search on, selects the catalog to be searched, enters the text to search for and launches the search.
  • multiple words separated by a space must all occur in that sequence for the song to be selected by the search engine. Multiple words separated by a comma may occur in any sequence or not at all.
  • a search on "Moonlight and Roses” would find only songs where those word appear in the field in that sequence.
  • a search on "moonlight, roses” would find all songs in which either word appeared anywhere in the title.
  • the results are displayed, for example, in groups of 40 songs. Each song is represented by title and alternative title, writers, and the show or movie in which it appeared.
  • links to additional information which may be provided by the registrant, are presented.
  • the additional information may include a 30-second audio sample of the work, lyrics, the score, information from the publisher or a list of recordings (discography) made of this work. Clicking on those links brings the additional information to the screen, or causes the audio sample to be played by the Internet browser.
  • WorksDB system 100 includes help screens associated with all major transactions, leading the user step by step through the licensing process.
  • WorksDB system 100 also includes advertising from related companies, intended to reach the music professional, producer or multimedia director. Selection of the advertisement to be displayed may depend on the catalog being searched, the usage being proposed or another characteristic of the particular transaction.
  • the user may request rights for any work in WorksDB system 100 by clicking on the "License" icon in the results table.
  • WorksDB system 100 prompts the user to indicate what usage is proposed, which market is addressed, and the size of the commercial venture.
  • the User ID entered by the user at the beginning of the licensing process retrieves the organization information entered during the first visit, as well as the account ID number and ASCAP/BMI/SESAC information if appropriate.
  • the selection of the rights requested category will determine the screen next presented to the user.
  • Information about the user includes organization and contact name entered the first time the user uses the system. The next time the user comes to WorksDB system 100, WorksDB system 100 will look for information in a record associated with the User ID. If that information is available, the user will not have to re-enter it. A user who has no User ID is directed to a page where the ID can be set up quickly.
  • the user is prompted to indicate which country or territory the work will be manufactured or produced in, which territory it will be distributed from, and which territory it will be distributed to.
  • the user is prompted to indicate which of five major usage categories apply: 1) Make a new recording (Album, Single, Chip, Music Box or other); 2) Use in broadcast, film or video (Television program, Radio program, Satellite or cable broadcast, Motion picture, Video release, Other multimedia product); 3) Distribute electronically, jukebox or background music (Permit download from Web or online site, Broadcast from Web or online site, Juke box, kiosk or other public interactive player, Restaurant, in-flight or other background music); 4) Perform in public (Theatrical production or aesthetic, School or community production, Opera, symphony or ballet, Nightclub, cabaret or other public performance); and 5) Distribute in printed form (Lyrics only, Lyrics melody and chords, Musical score).
  • a second screen specific to that usage category, gathers additional information required in order to generate the license rights request.
  • the system employs an expert system to evaluate usage categories, commercial conditions, territories involved and applicable rules in order to determine which rights will be required in this case.
  • Such an expert system can be in the form of a data structure, such as a table, or as a rules-based system.
  • the rights analysis system is maintained and updated from time to time to reflect changing laws and commercial practices around the world.
  • WorksDB system 100 looks up the source for those rights in the WorksDB database. For most musical works, for example, the rights are administered by certain major rights organizations around the world. However, song writers and publishers may choose to have certain works or certain rights administered differently or in accordance with special instructions.
  • WorksDB system 100 maintains a database of where the requesting user must apply for any of the rights to a work, in any territory of the world, and provides song writers and publishers with a simple mechanism for creating and maintaining individual instructions particular to any song or group of songs. Once WorksDB system 100 has established the work, the user, the usage proposed, the rights required and the current source of those rights, it assembles a rights request message and presents it to the user for confirmation. If approved, the request is sent to each rights source immediately. Typically, all rights requests are sent by email, in a standard format.
  • WorksDB system 100 will also use other formats. It may, for example, send the request by fax as well, and under certain circumstances by regular mail. Other formats may be developed to convey the rights request in other languages, and to construct alternative email formats to be read by automated licensing systems set up by the licensing rights source.
  • WorksDB system 100 can even prepare a pro forma license, and upon approval by the user, can transmit copy to the licensing rights source.
  • the rights source will provide generic text clauses to be included for any given license request and the system will construct the appropriate license.
  • WorksDB system 100 keeps a record of all rights requests transmitted on behalf of the user, and enables the user to view that request history at any time.
  • WorksDB system 100 may track responses to the license requests and may also participate in the subsequent rights and permissions or licensing activity by constructing pro forma licenses.
  • the method and system of the invention thus described accomplishes the objectives stated above by providing an online, multimedia license, registration and tracking system for storing, retrieving and tracking licensing rights sources information, and for registering copyrights and the like for works of authorship in general; and for licensing multimedia works through the system.
  • the WorksDB service is implemented as the Internet-based Licensing Service of the attached Appendix 1.
  • the Internet-based Licensing System (“IBLS”) and service is designed and developed by a major licensing agency to assist recording companies, multimedia producers, Internet distributors and others in getting the music rights quickly at a single Web site.
  • the IBLS service has six major components:
  • IBLS provides a searchable database of all copyrighted songs in the American and world-wide repertoire so the professional user can determine which work, which version and which arrangement he or she wishes to license.
  • the IBLS service includes an expert system that identifies the usage being proposed and determines which rights are required.
  • music there are mechanical rights needed to make copies, performance rights needed to perform the work in public, synchronization rights to use the work in a movie or commercial, print rights to distribute the lyrics or the score, digital rights to distribute the work on the Internet, grand rights to stage a dramatic performance and master rights to reproduce an existing recording.
  • "moral rights" exist, permitting the song writer to grant or withhold permission to use the work in a specific context. Sometimes several of these rights are required for a particular use.
  • the IBLS service identifies which rights the user will require.
  • the IBLS service offers the user the ability to send all the necessary rights requests immediately to the correct agencies. It prompts the user for the necessary information, formats the request, determines the current address and preferred request format for each of the rights sources involved, and sends the request message. In most cases the message goes out by electronic mail with a copy to the user, but in other cases the request may go by fax or mail.
  • the system logs the requests each user has made in the last 30 days, but typically does not keep track of whether the request is answered or the license is issued.
  • the IBLS service operates as a World Wide Web site on the Internet, available free to all users around the world.
  • the system benefits the major licensing agencies which sponsor it in at least two ways. More than a third of the license requests now received by major licensing agencies cannot be processed (a) because the information is not complete or correct or (b) because that licensing agency is not the appropriate rights source for the work being requested.
  • the IBLS service eliminates the work associated with these unprocessable requests by helping the user create a complete request in the first place, and by sending requests to the correct licensing source.
  • the service also benefits the user. Because of the engineering of the system itself and the availability of proprietary databases and analytical systems, the user should be able to create and send a rights request within a minute, and automated licensing systems may respond in as short a time as three minutes. This especially important for Internet distributors who can now add a new work to their online catalog in minutes. This makes it easier for Internet sites to comply with the copyright law, and lessens the likelihood of non- compliance.
  • Any publisher with a IBLS account may register a work.
  • the process requires the publisher to enter information about both the registering organization and the work.
  • the publisher may choose to register the work with the US Copyright Office as well as other agencies and rights collection societies at the same time. All data entered into the IBLS Registry is maintained permanently in a secure format, offering the publisher a digital archive of his works. A . Information about the work
  • the screen prompts the user to enter a common set of information required by IBLS and the CIS Common Works Database. If the user also wishes to register the work with the US Copyright Office, additional information elements are required.
  • B Rights management information
  • the registrant is prompted to provide information for handling requests for all different rights in all territories. Normally it will be sufficient for the registrant to indicate that the rights should be handled according to standard worldwide practices, but alternatively it is possible for the registrant to specify different sources for all the different rights in all the known territories.
  • Any publisher may create a new song or add rights management information to the record of an existing work for which he represents 100% of the owners.
  • all changes by any owner are automatically reported by the system to all other owners of that song, and their approval is required before the changes are made.
  • the registrant may elect to send the new song information to other agencies and rights collection societies as well. If this option is elected, the system selects the information appropriate to that agency or society and sends the data as an email message.
  • the IBLS creates and transmits an electronic application for US copyright in the CORDS system format.
  • the application is conveyed electronically to the US Copyright Office and subsequent correspondence occurs exclusively between those parties.
  • the work may consist of a recording in MP3, MIDI or another standard format, or it may be a text file of the lyrics and score.
  • the IBLS service includes a secure database of all song information added or amended in order to provide participating publishers with a permanent trail of changes.
  • the digital archive includes digital sound recordings submitted to the US Copyright Office, or otherwise provided by the publisher, and may grow to become a major repository of digital music. G. Batch registration
  • Publishers may register multiple songs in batches through a prearranged transfer of files. This method is intended primarily for initially loading the database. H . Updating an existing record
  • the original registrant may retrieve a complete record of the information for a song as of that moment, as well as see a history of changes that may have occurred since the original registration.
  • the original registrant may modify this information and elect to have the IBLS service send those modifications to other databases, agencies or rights collection societies.
  • the account responsible for maintaining the song record can also view and modify the list of other owners and their shares, although that task may also be performed by the IBLS database manager. If an owner other than the maintaining account wants the information changed, he may contact the IBLS database manager and request the change.
  • a person seeking the rights to a musical work must first identify the work specifically from a library of copyrighted works, derivative works and arrangements. Having identified the song from a list of similar titles or multiple arrangements, the system then uses the Multimedia Identifier (MMI) to access information and rights management instructions. Ultimately the MMI is incorporated into the rights agreement or license, and in the future will be used to manage royalty collections and distribution.
  • MMI Multimedia Identifier
  • the user may search individual libraries within the IBLS service.
  • the libraries are created by IBLS to separate very different groups of music such as national repertoires, theatrical productions and music libraries.
  • the user can search the file by writer, title or alternate title, show or movie in which the work appeared, or MMI which is the primary key for each work.
  • additional keys may be added, such as the capability to search by International Standard Recording Code (ISRC) or CAE number, part of the international CIS system for identifying authors and composers.
  • ISRC International Standard Recording Code
  • CAE number part of the international CIS system for identifying authors and composers.
  • the user selects the field to search on, selects the catalog to be searched, enters the text to search for and launches the search.
  • multiple words separated by a space must all occur in that sequence for the song to be selected by the search engine. Multiple words separated by a comma may occur in any sequence or not at all.
  • a search on "Moonlight and Roses” would find only songs where those word appear in the field in that sequence.
  • a search on "moonlight, roses" would find all songs in which either word appeared anywhere in the title.
  • the results are displayed in groups of 40 songs. Each song is represented by title and alternative title, usage notes, writers, and the show or movie in which it appeared.
  • links to additional information come from a second database.
  • the additional information may include a 30-second audio sample of the work, lyrics, the score, information from the publisher or a list of recordings made of this work. Clicking on those links brings the additional information to the screen, or causes the audio sample to be played by the browser.
  • the IBLS service includes help screens associated with all major transactions, leading the user step by step through the licensing process.
  • the service also includes advertising from related companies, intended to reach the music professional, producer or multimedia director. Selection of the ad to be displayed may depend on the catalog being searched, the usage being proposed or another characteristic of the particular transaction.
  • the user may request rights for any work in the IBLS by clicking on the "License" icon in the results table.
  • the system prompts the user to indicate what usage is proposed, which market is addressed, and the size of the commercial venture.
  • IBLS search system Use of the IBLS search system is free and anonymous, but to request a license for a song, the user has to provide a minimal amount of information and receive a User ID.
  • the service records the organization and contact information last entered by each User and fills in the first licensing request form automatically.
  • a user who has no IBLS User ID is directed to a page where the ID can be set up quickly.
  • the user may be an individual employed by the publisher, or he or she may be an independent contractor.
  • the user is prompted to indicate which country or territory the work will be distributed from, and which territory it will be distributed to.
  • More than one of these categories can be selected for a rights request. Based on the response to this question, a second screen gathers additional information required in order to grant rights. The system may also present a third screen in some circumstances prompting for missing or resolving conflicting information.
  • the system employs a unique and proprietary expert system to evaluate usage categories, commercial conditions, territories involved and applicable rules in order to determine which rights will be required in this case.
  • the rights analysis system is maintained by experts at the major licensing agencies, and is updated from time to time to reflect changing laws and commercial practices around the world.
  • the IBLS service looks up the source for those rights in a proprietary database maintained by the major licensing agencies and by the publishers. For most musical works, the rights are administered by the major rights organizations around the world, but song writers and publishers may choose to have certain works or certain rights administered differently. Some publishers, for example, prefer to have direct control over the use of any work in a commercial or a movie. In other cases, the song writers may choose to handle all rights requests themselves.
  • the IBLS service maintains a proprietary database of where the user must apply for any of the rights to a work, in any territory of the world, and provides song writers and publishers with a simple mechanism for creating and maintaining instructions particular to any song or group of songs.
  • the system Once the system has established the work, the user, the usage proposed, the rights required and the current source of those rights, it assembles a rights request message and presents it to the user for confirmation. If approved, the request is sent to each rights source immediately. Initially all rights requests are sent by email, in a standard format proposed by the developer of the IBLS. As the system develops, it will also use other formats that may be useful to particular rights sources. It will send the request by fax as well, and under certain circumstances by regular mail. Other formats will be developed to convey the rights request in other languages, and to construct alternative email formats to be read automatically by licensing agency's automated licensing systems.
  • the IBLS service keeps a record of all rights requests transmitted on behalf of the user for the past 30 days, and enables the user to view that request history at any time.
  • the IBLS service does not track response to these requests and does not participate in the subsequent rights and permissions or licensing activity.
  • the organization In order to enter or modify a record in the IBLS database, the organization has to apply for and receive an Account ID. This process begins by the organization completing the New Account information and submitting it to the IBLS database manager. An account number is issued along with a passsword and this information is sent to the contact person by email. The IBLS database manager may use this opportunity to verify the information to make sure that it is consistent. Large publishers may choose to create an account for each major imprint or catalog. Accounts also include organizations and individuals who appear as Owners in the song record. The elements of information required for a new account are:
  • Account ID Assigned by the IBLS database manager.
  • Account Master Password The password to be used for all supervisory actions, primarily adding and deleting the regular passwords.
  • Account Passkey The account may have up to six regular passkeys so that access may be granted and withdrawn on an individual basis. The passwords can be changed only by the person gaining access with the master password.
  • Account Manager The name of the person who is primarily responsible for the IBLS data and activities.
  • Account Name Name of the organization.
  • Email The email address to which all IBLS correspondence is sent.
  • Passkeys The Master Account can create or modify up to six passkeys which permit others to enter the IBLS directory and modify or add new songs to the database. Passkeys are seen only by the person who enters with the Master Account Password.
  • the Account also has the option of creating seven separate email addresses to which license requests may be sent, one for each major type of license request.
  • the publisher may direct that for any territory, the rights request for this song be sent to one of these addresses instead of to the normal national agency.
  • Performance address Email address for Performance rights.
  • Grand address Email address for Grand rights.
  • Print address Email address for Print rights.
  • Last update The date on which the last changes were made to this record.
  • Last update ID The passkey of the person who made the last update.
  • the primary database is the IBLS database which contains information about the works themselves. There are several libraries, all of which have the same format. These include the American repertoire, the Italian repertoire, sheet music, music libraries and other collections.
  • the information about a song may exist in several related databases.
  • the primary database is used for fast searching, and contains only those fields on which the user is permitted to search: MMI (the key field), Title, Alt Title, Writers, Arranger, Show/Movie, Publisher and Catalog. Once found, the MMI links the system to a secondary set of data which includes usage notes, links and other administrative information.
  • MMI Multimedia Identifier
  • the MMI number has the following format:
  • Title The title is presented in upper and lower case, in its most common form. Do not bracket the title in quotes. Do not include information about the movie or show in the title field, put it in the movie or show field.
  • Alt Title (optional): The alternate title by which the song may be known.
  • the alt title field may include a translation of the title into another language if it is commonly known by that title. As: title might be "Que Sera Sera", alt title: "What Will Be Will Be” .
  • Show or Movie (optional): The name of the movie, theatrical production, television show or other production in which the work most prominently appeared. This should not include the production credits, the producing studio or distributor; just the title.
  • the IBLS convention is that writers names are given first name first, separated by a comma, in whatever sequence the registering publisher chooses.
  • Arranger (optional): The name of the arranger or arrangers.
  • CAE# (optional): The publisher has the option of identifying the writer also by their CAE Numbers, which identifies the author in the context of an international authority file. The IBLS may also add CAE numbers to songs in the future.
  • the IBLS service has a special provision which allows the registering publisher to link the IBLS record to elements of information stored elsewhere. Six kinds of links are presently permitted. If a link is present, the system shows the user the appropriate link button on the screen. If not, no button is displayed.
  • the links may be entered by the registering publisher, and may point to object on the IBLS server, on the publisher's own server or elsewhere on the Internet. The link can point to a literal URL elsewhere on the Internet, or it can point to a DOI in the DOI directory, which in turn directs the user to the then current location of the file.
  • Link to Audio sample An internet link to the location of the 30-second audio file.
  • the audio file itself should be in MPG3 or some other non-proprietary format for which browser plug-ins are widely available.
  • the link may be a DOI which points through the DOI directory to the then-current location.
  • Link to Additional Info The IBLS has the capability of showing an "Info" button if the record has any information in this field. The publisher should use the field to bring the user to more information about the work, about products or information related to the work, or about any other matter such as the show, the composer or a recent prominent use of the song.
  • Link to Discography The publisher has the option of linking the user to a list of recordings made of this work, and in turn of linking the user to a Web site where these recordings can be purchased.
  • Link to Lyrics The publisher has the option of linking the user to the lyrics of the work. Some publisher may choose to provide the lyrics in a PDF format which cannot be saved or printed. Other publishers may choose to distribute the lyrics freely, or to use this link to sell a lyrics file, or book of lyrics.
  • the registering publisher may offer the user access to the score itself, or to a directory of printed parts.
  • the user has the option of searching on songs that belong to several large groups - American repertoire, Italian repertoire, music libraries, musical theater.
  • the song record contains a field which in turn holds one or more "library” tags.
  • a song that is both American and Italian might have both an A and an I in this field.
  • An Italian- American song that is often performed as a high school musical may have A,I,M.
  • the user selects which "library" to search in, but in fact is choosing which set of works to search within.
  • Account ID The Account ID of the account that is authorized to update this record.
  • Last Update The date on which this song record was last modified.
  • Last Update ID The password used by the person who last modified this record.
  • the song record has several data fields used in the rights request process:
  • This field contains a code that indicates whether the song is licensed by Harry Fox.
  • Rights requests are sent to the national agencies and rights societies around the world, depending on the type of rights required and the territory from which the work will be distributed. But the publisher has the option for any song, in any territory, to have the request sent to himself - to the email address for that rights type which is maintained in the account information. Creating that special instruction is done on the song update screen by selecting the "Change" button for the territory the publisher wishes to change. On the change screen, the publisher may indicate for each type of rights, whether the request should be sent to one of the major agencies, or to the publishers' own email address. Those instructions are stored in the rights source information field.
  • the format for the information is:
  • MMI MMI, TERR, TYPE, RIGHTS, SOURCE, COPY
  • MMI is the Song Identifier
  • TERR is the territory code (See Code Tables)
  • TYPE is the code for the rights type (see Code Tables)
  • RIGHTS is a word describing the rights
  • SOURCE is the agency or society code for the rights source. If the Publisher has indicated that the license should be sent to his own email address, the SOURCE contains the Account/Owner ID.
  • COPY contains the code to indicate whether a copy of the request should be sent to the Publisher.
  • the format of the information is: TYPE, CLAUSE, TEXT, where TYPE is the license type, CLAUSE is the clause to be replaced, and TEXT is the language of the new clause to be used.
  • IBLS IBLS database
  • the publisher In order to add a song to the database, the publisher must have a IBLS account. (See Account ID above.)
  • the user In order to update a song, the user must have a password that is on the key list of the account (publisher) that originally created the record. When the user enters an acceptable password, the account ID is associated with that user for the duration of that session, and the user may update any song that is tagged with that Account ID.
  • the format of that batch is as a Microsoft Excel spreadsheet, or any other data format that can be normally imported into Excel, such as txt, csv, or dbf.
  • the first row should include the name of the data element in that column.
  • the columns should then contain the data elements in the following order, reading from left to right: MMI, Title, Alt title, Show/Movie, Writers, Arrangers, CAE, Usage Note, Link to Audio Sample, Link to Additional information, Link to Discography, Link to Lyrics, Link to Score, Account ID, Publisher, Catalog, HFA License, Rights Source Information.
  • a batch file should not contain more than 50,000 works. If necessary the publisher should create multiple sections files no greater than the 50,000 record limit. The file should be stored on a 100Mbyte ZIP Cartridge and mailed to the IBLS database manager.
  • the IBLS system will send an email message or file to the CWD containing the required information. The elements of information to b sent to the CWD have not been determined.
  • the IBLS will also accommodate updates from third party copyright management systems like Right Track and CounterPoint. The method of updating from these products has not been determined.
  • All IBLS data can be modified by the IBLS database manager. Beyond that, only the original account that created the song record can update the record. Any change to a song that has more than one owner is reported to all the other owners of the song. If there is a disagreement over the change, it is reversed until the owners resolve the disagreement and notify IBLS that the change should take place. L. History of Changes
  • the system gathers into the transaction record (a structure in memory) the following information elements from the Song record (by their associated codes): MMI MMI
  • the system Based on the information entered in the Rights form, the system indicates which uses the requestor has selected.
  • the types of use are:
  • the system Based on the uses planned for the song, the system asks additional questions.
  • the questions are grouped into forms.
  • the system looks at the Uses and Rights Table (below) and determines which forms need to be presented to the user.
  • the information gathered by those forms includes:
  • the forms are assembled sequentially on the page being sent back to the user. Once the user enters the information required by each question, the system gathers that data into the transaction record. Through this two-step process the system acquires all the necessary information about the use planned for this work.
  • the system does two things: (a) it determines which rights the user will require and (b) which publishers or organizations must provide those rights. To determine what rights will be required, the system looks at the rights requirements indicators in the Uses and Rights table. In the actual case the transaction record only contains data rows for those uses that have been indicated. If the element is present or positive, the system concludes that the associated rights will be required. For example, if the user says that he plans to make a record, and provides information specific to the record - such as Audio 500+ - the system looks across the rights indicators and determines that mechanical rights will be required. As a result of this analysis, the system compiles a list of the rights that will be required for this application - e.g. Mechanical, Synch, DPD.
  • the second task is to determine which publishers or organizations must grant those rights, based on the type of rights required and the territory in which the record is manufactured, or where the program is produced, or where the performance will take place, or where the server will be located.
  • the system begins by searching the ownership database, which is structured as follows:
  • the first step of the search is to find the first record in the Ownership database where the MMI in the search matches the MMI in the record. If no MMI is found, the system selects the HFA default record. The rights request well go to the HFA trouble desk. This condition occurs if the user has found a song in the IBLS for which no ownership record has been created. This should not occur.
  • PubID the identity of the publisher.
  • Agent the name of the rights source to which the request will be sent.
  • Email the address to which the request should be sent. In most cases the Email address will be the HFA address.
  • the system looks at the next ownership record to see if there is a match on the MMI. This processis continued until all the ownership records have been examined. If no matches are found at all, the system uses the HFA trouble desk email record.
  • the system has compiled one or more email records. These are added to the transaction structure and reported to the user as part of the Request screen. D . Rights Source Selection
  • the system assembles the elements of a rights request in the following sequence:
  • the result of the rights analysis and rights source selection is the construction of an email message that goes to the selected rights source, with a copy to the requestor.
  • the message consists of the following elements:
  • Cc includes the email address of the requesting organization.
  • Sub j The subject line is constructed as follows: request number, catalog name, territory code, type code and MMI. This permits the organization receiving the request to route the message to folders or forward messages to other organizations based on catalog, territory and rights type.
  • the message consists of one element per line. Elements are included only if they are relevant to the request, although the example here includes them all.
  • Each element consists of two parts: the element name which is the same all the time, and the element value which is the information provided by the requestor.
  • End of Message A general phrase including the name and number of the IBLS person to call if there is any difficulty receiving this message.
  • X-Mailer Microsoft Outlook Express 5.00.0810.800
  • T BookPrice T SongsinBook: T BookMfg : Code BookDist: Code BookWorld: Y/N BookUS: Y/N BookCanada : Y/N BookUK: Y/N BookEuro : Y/N BookAsia: Y/N BookUSSR: Y/N BookME: Y/N BookAfrica: Y/N PerfProducer : T PerfDate: T PerfLocation: Code AudienceAdmission: Y/N ChurchSchool : Y/N Establishment: T Otherlnfo: T
  • This document describes a system that will leverage the Intemet, existing HFA data, and partner ⁇ a ⁇ to create a consumer-oriented business for the HFA
  • This system which is part one of several phases, will allow Intemet users to visit an HFA site and shop for prerecorded music, sheet music and movies.
  • This project phase provides a foundation for the industry-oriented music licensing site scheduled for release later in 1999.
  • the systems in use and proposed by the HFA are primarily database applications.
  • the scope of work outlined here supports extending the delivery of the HFA's existing services over the Intemet. This will require data collection from the HFA's existing AS/400 based systems.
  • This document includes an analysis of the HFA's existing systems and a specification for proposed systems. Analysis of the existing systems was based on documentation of these systems, Interview with HFA staf system users, managers, and domain experts and, work products, reports, and other artifacts used in processes these systems support. This analysis is presented in natural and structured English and a variety of diagrams.
  • the home page of the site will offer the Shortcut search field and a link to...
  • the Search results page will list the songs found and the CDs on which they've been recorded
  • the Song detail page will show all the information available about a song, and offer links to associated information
  • the Shortcut Search control set is a single input field with a "Search" button, meant to take up very little space on the site's home page.
  • the Shortcut search searches only the song titles, and is labelled to make this clear.
  • the Simple Search page lets the user easily search in a specific field of the song data, and gives the user a simple way to constrain the search to only find recent releases.
  • the category list is a set of checkboxes labelled with the song categories available. The user can check one or more to constrain the search to songs in only those categories.
  • the field list is a select control that lets the user select the datum to be searched. It lists every field except “Date”, and defaults to "[All fields]":
  • the search field is an input field into which the user can type the string to be searched for.
  • the Recent release check box lets the user find only songs released in the last N months.
  • the Search button initiates the search and shows the user the Search results page. Advanced search form
  • the Advanced Search form lets the user define a more specific subset of the available songs by using implicit Boolean operations. Separate input fields are entered for each datum in the song record. The user can enter multiple terms in one field to see the union of the sets of songs matching each term in that datum, and enter terms in multiple fields to see the intersection of the sets of songs matching those terms in those data.
  • the Search button initiates the search and shows the user the Search results page.
  • the search results list lets the user identify among the songs that match the search criteria the one they were hoping to find by showing for each matching song its category, writers, publisher and all the recordings on which that song appears. It also lets the user buy sheet music for that song or any of the its recordings.
  • the song's title will be linked to the Song detail page for that song.
  • the song's writers will be listed in a single field.
  • a sheet-music icon will be linked directly to a page at a sales partner's site that will let the user order the sheet music for the song.
  • the name of the artist will be linked to a Search results page that shows all the songs performe by that artist.
  • a sheet-music icon will be linked directly to a page at a sales partner's site that will let the user order the sheet music for this arrangement of the song. Hear recording If this recording is available for download and play over the Internet, an icon will link to the fil
  • the song's writers will be listed in a single field; each writer's name will be linked to a Search results page that lists all songs that writer wrote or collaborated on.
  • the song's publisher will be linked to a Search results page that lists all songs that publisher owns.
  • a sheet-music icon will be linked directly to a page at a sales partner's site that will let the user order the sheet music for the song.
  • a table will list all the albums on which the song appears, with these columns:
  • the name of the artist will be linked to a Search results page that shows all the songs performed by that artist.
  • the name of the album and an adjacent CD icon will be linked directly to a page at a sales partner's site that will let the user purchase the album on CD.
  • a sheet-music icon will be linked directly to a page at a sales partner's site that will let the user order the sheet music for this arrangement of the song.
  • a table will list all the movies in which the Bong appears, with these columns:
  • the name of the movie will be linked td ⁇ earch results page that shows all the songs that appeared in that movie. Opening date Length Buy movie
  • a movie icon will be linked directly to a page at a safes partner's site that will let the user purchase the movie on tape, videodisc, or DND.
  • the name of the show will be linked to a Search results page that shows all the songs that appeared in that show.
  • the name of the product will be linked to a Search results page that shows all the songs that appeared in ads for that product.
  • the name of the manufacturer will be linked to a page that shows all the products from that manufacturer for whose ads songs were licensed; each product on that page will be linked to a
  • Search results page that shows all the songs that appeared in ads for that product.
  • This navigation chart shows the connections from page to page by which the user can traverse the connected queries:
  • This application will be invoked from the Shortcut search, Simple search, Advanced search and Song search results list pages. It produces a "Song search results list" HTML page based on user input.
  • Input can take several different formats. One or more input parameter may be entered. Multiple entries of the same kind of input parameter are also acceptable. Acceptable input parameters are any or all of the following.
  • the input may be a key created by an earlier invocation of this application that allows for continuing a result set.
  • HTML page known as the "Song search results list” listing one-line entries of songs with matching titles and one-line entries of recordings for each song limited to approximately 50 lines of output. Each song will provide a link to purchase sheet music. Additionally each song will provide a link to invoke the Generate song detail page application with the songs' SonglD.
  • Each recording will provide links for generating a page describing the recording in more detail, purchasing the recording and purchasing sheet music as available. Recordings will also have links to playable media, (as available). These will be references that invoke the "Generate playable media reference application”.
  • the page will also contain standard navigation links, (i.e. Home, Refine Search, etc.). Supporting data
  • Shortcut and simple searches will use the Title, TitleSong, Song and Recording tables.
  • Advanced searches based on search complexity, may require access to the same tables and additionally the Lyrics, PlayableMedia, TNShow, MotionPicture and Commercial tables.
  • the database was organized to allow for efficient shortcut and simple searches.
  • the Title table will be searched for partial and complete matches. Based on database platform facilities there is potential for providing near matches.
  • the resulting Title records will be joined with the TitleSong table and those resulting records will be joined with the Song table. Each entry obtained from the Song table will be eligible for producing a line in the output. To generate the complete line a join will be made from the Song.PreferredTitlelD field back to the Title.TitlelD field to obtain the Title.Title field that matches this song.
  • Each resulting Song record will be joined with the Recording table to obtain the list of associated recordings.
  • Each recording entry will be joined with the Title table to obtain the title of publication.
  • a simple search is similar to a Shortcut search but requires additional tests based on the Song.Category and Recording.ReleaseDate fields.
  • This application will be invoked from the Song search results list page. It produces a "Song detail" HTML page based on a song reference.
  • Input will be a single song reference in the form of a SonglD.
  • the page will also contain standard navigation links, (i.e. Home, Refine Search, etc.).
  • the Song table will be searched for an exact SonglD match.
  • the resulting song record will be joined with the Title table to obtain the songs proper title.
  • the Song ID will then be sought in the TVShow, MotionPicture and Commercial tables and the resulting records will be included i the output.
  • the SonglD will then be sought in the Recording table.
  • Each resulting record will join Recording.TitlelD with Title.TitlelD to obtain the proper recording title. This information will be added to the output. Additionally the RecordinglD will be sought in the TVShow, MotionPicture and Commercial tables and the resulting records will be added to the output.
  • This application will be invoked from the Song search results list and Song detail pages. It produces page redirection to a playable media source.
  • Input will be a single recording reference in the form of a RecordinglD and a single integer value corresponding to a bit in the Recording.PlayableMediaAvailable field.
  • HTML redirection page providing access to an Intemet accessible piece of digital playable media.
  • the playable media integer identifier passed in will be algorithmically mapped to a playable media format code.
  • the Recording table will be searched for an exact RecordinglD match.
  • the resulting recording record and playable media format code will be joined with the PlayableMedi table to obtain a PlayableMedia.Reference.
  • the reference which is a URL to the appropriate piece of media, will be wrapped into the HTML redirection page.
  • This application will need to be invoked when CDUniverse makes a new data set available.
  • the application will then update the Recording and PlayableMedia tables to reflect recordings available at HFA partner CDUniverse.
  • Name and location of the CDUniverse data set Name and location of a format code mapping file. Name and location to create a log file.
  • Each record of the CDU data set will be processed in turn.
  • Per CDU record the Title table will be searched for the provided song name.
  • the Recording table will also be searched for an LCC code matching the LCC provided by the CDU data set record. The resulting records will attempt to be joined.
  • a successful join will indicate the correct record in the Recording table to update with the CDU provided availability information. Additionally the RecordinglD of the selected recorded will be used to search for and update the PlayableMedia table with the reference information provided by CDU.
  • the format code mapping file will be used to convert the CDU supplied format codes to codes which are used by the PlayableMedia,Format field. The successful update will be logged as "Successful Update".
  • This application will need to be invoked when JW Pepper makes a new data set available. The application will then update the Recording table to reflect recordings available at HFA partner JW Pepper.
  • Name and location of the JW Pepper data set Name and location to create a log file.
  • Each record of the JWP data set will be processed in turn.
  • Per JWP record the Title table will searched for the provided song name.
  • the Recording table will also be searched for an LCC code matching the LCC provided by the JWP data set record.
  • the resulting records will attem to be joined.
  • a successful join will indicate the correct record in the Recording table to update with the JW provided availability information.
  • the successful update will be logged as "Successful Updat
  • the classified system for this phase will be purchased, installed, and customized. Issues to be solved are the inclusion of HFA templates into the purchased application and the inclusion of the chosen ad server tags.
  • the system will not include the rich subcategory and attribute data model that future efforts will provide in future phases.
  • logs of all activity including posting, modifying, or deleting ads.
  • the logfiles also include the IP addresses of the users performing these activities
  • ⁇ Web-based Control Panel allows the admin to modify or delete any ad, review new ads before they are posted, send out e-mail notices to users whose ads are about to expire, purge old ads, run the Keyword Notify program, view the mailing list, clear the mailing list, and send out mass e-mails to subscribers, all from a point-and-click graphical user interface.
  • ⁇ Admin can define varying expiration dates for ads (this can be set to any number of days)
  • Ad owner can modify or delete at any time
  • Keyword Notify service sends new ads to users that match their pre-defined keywords
  • Customizable ad categories that can easily be defined through a setup variable
  • Customizable ad display including the width of the ad tables, table border size, text and background colors within the ad tables, and the text font. Password protection for ads so that only the original poster can modify or delete
  • This application will need to be invoked an HFA client wishes to forward a song-based request to the HFA.
  • the request will be formed by a cgi application and delivered to the HFA via email.
  • a log file indicating successful and unsuccessful updates to the web supporting database, and an email message with a tab-delimited list will be sent to an HFA email address.
  • search criteria interface will be the same, consisting of:
  • the resulting "hit list" will contain different columns.
  • the CD Universe lCOn will have a link to the CD Universe partner site.
  • the system will log each time a user clicks on such a link.
  • HFA Artist database combines artist names in different ways when they collaborated on a song. For example:
  • the system will also log each time a user clicks on such a link.
  • the Recording Details Link will bring up a page showing the details of the particular song recording. This link will only be enabled for songs that have multiple licenses. The information included will be a subset of the following: 3
  • the #TimeS Recorded column will indicate the number of times the song was recorded. It may also be possible to list the songs in descending order by the number of times recorded. Alternatively, it may be desirable to replace the number by a flag, indicating the most commonly recorded song in the list.
  • the AS CAP column will indicate whether at least one publisher of the song is affiliated to ASCAP.
  • the BMI column will indicate whether at least one publisher of the song is affiliated to BMI.
  • the Active Flag column will indicate whether royalties have been paid on this song in the last 3 years.
  • the CD Universe lCOn will be the same as in the By Song Hit List. No other columns of information will have underlying links.
  • the CD Universe ICOn will be the same as in the By Song Hit List. No other columns of information will have underlying links.
  • the # Son S will show the number of songs / tracks on this album.
  • the # S ⁇ nQS will show the number of songs written by this composer. No columns of information will have underlying links.
  • This algorithm will run on the AS/400 host, given input from the user interface described above.
  • the entire user search string (up to 256 characters) will be set to upper case and compared with the full upper case name in the appropriate file. Only exact matches will be returned.
  • each significant 4 word of the user search string will be used as keys against the appropriate Ordered Search Key file.
  • All n words will be used, then n-1, then n-2, etc.
  • the search will end when either only 1 word remains, or matched are found.
  • the song title "There's no cure like travel, Bon Voyage" would be stored in the ordered keyword file with keys THERE, NO, CURE, LIKE, TRAVEL, BON, VOYAGE.
  • Ordered Word Match is a very fast and accurate search for situations where the user accurately spells and orders the significant search words.
  • each of the first m significant words are used as keys against the Keyword File. All words must be included in a song in order for it to be considered as a match.
  • a song "data dictionary” may also be employed to help determine the fastest path to the match list. It would be populated at time of data conversion with every significant song word. Each record would include the upper case version of the word, then the number of songs in which it appears.
  • love may appear in 200,000 song titles, but “Tuesday” may only appear in 50.
  • Using “love” as the First Word in the above search would result in over 200,000 I O operations.
  • Using “Tuesday” as the First Word would result in at most 100 I/O operations.
  • the search would be performed in the most efficient order.
  • the down-side of this is that the data dictionary would likely contain on the order of 100,000 records.
  • each of the first m significant words are used as keys against the Keyword file.
  • the result of the above search may be:
  • a lower limit may be set on the match percentage.
  • a Phonetic-like code will be generated for each of its words. This code will be used as search keys, and used in a way similar to the AND and OR searches above.
  • this method would use the search string as a beginning characters.
  • each word would be treated as a pattern.
  • This search method is much less efficient, and may be too slow to be practical.
  • search methods will be developed as function modules, allowing them to be used in any permutation.
  • the goal is to have a search engine that can be customized without having to re-code nor recompile anything.
  • Customizing the search engine will be done in two ways: by the user, by a system administration function.
  • the user will have the ability to customize the search. S he may choose any one of :
  • Exact Match If, for example, the user is confident that s he knows the Exact Match full title of a song, s/he might choose this search method. It will result in the fastest possible performance.
  • Exact Match Any Word By choosing this option, the user is indicating that Exact Match, matching songs are those with any of the words matching. then Or Partial Phrase This option allows the user to type in a partial phrase. It Exact Match, will be used as a generic key. For example, a search string then Generic of "Evergr” would match with "Evergreen, Everglade, "
  • the user may click or de-click the check-box of Phonetic Similarity. This options works with the And and Or searches.
  • the system administrator has control over many different parameters of the search algorithm. The idea is that s he may monitor the performance of the site, and modify the search algorithm as necessary without the need for any functions to be changed or recompiled.
  • Insignificant Word List 7 Table of words to be dropped from search strings The, and, it, is Maximum Matches A system variable which sets the maximum number of 25 matching records to be shown on one page. It should be possible to allow the user to continue, looking at the next 25 matches.
  • Match Percent A match below such a percentage would not be 20% minimum considered. This could be used with the OR method, and possibly with the Phonetic method.
  • Minimum Ordered Used by the ordered Word method as the minimum Words number of words to be used.
  • Maximum Ordered Used by the ordered Word method as the maximum Words number of words to be used.
  • Phonetic Search It would be keyed by the upper case word, and would also Phonetic Search have a field to contain a title count. It may also be desirable to include the phonetic code.
  • the index department maintains data files that support licensing activities. These files include records for the song titles that the HFA licenses and records for publishers (The HFA's clients) and licensees.
  • Synchronization The Synchronization department licenses rights to music for use with motion pictures, television, or other applications where music is used in conjunction with moving images.
  • egotiation Handholding The negotiation Space, or Deal Space, will enable users to be more self-sufficient with regard to the arbitration and documentation of licensing.
  • the HFA spends a lot of time coordinating the negotiating of licensing, and collects no fee if the deal is not struck. Some clients only approach the HFA to finalize the license after an agreement is reached, and then HFA collects a fee.
  • the Deal Space should help more licensing processes reach the HFA only when an agreement is made.
  • conflict Resolution A lot of license processing is put on hold when conflicts arise. These conflicts stem from ownership conflicts, etc.
  • the conflict resolution process unlike the negotiation space, is primarily an HFA hands-on faculty, much like a trouble-ticket program, where histories and cases can be traced back in time. This will be a fellow traveler to much of the Index maintenance functionality.
  • HFA Completed License Request is received. HFA determines if the request pertains to a song HFA can license. Otherwise reject Request.
  • HFA determines if it represents any entities with rights to the song.
  • HFA does not represent any of the entities with rights to the song, a "Do Not Represent" or DNR form is sent to the Requestor, most likely a Producer.
  • the system will include data entry fonms supported by software-based form-field validation.
  • Single record entry mode is implemented as an online form with software validation of form-field data.
  • Batch entry mode is implemented as an upload of a document formatted according to pre-defined rules.
  • New records will be queued for review by a human administrator. Therefore, the system will include a display screen for administrators that facilitates reviewing and editing queued records.
  • the system will provide functionality to support conflict-resolution processes triggered by certain Index department tasks.
  • Such conflicts may be discovered automatically by software, or resolved manually by personnel.
  • the system facilitates resolution by personnel with display screens that consolidate and organize conflict-related information.
  • These display screens will be comprised of data generated and stored automatically (such as dates and times), data pulled from indexing databases, and data entered in by personnel responsible for handling such conflicts.
  • One example of an automatically discovered conflict is when the total ownership of a song exceeds 100%.
  • Packaged data includes:
  • the system will provide functionality to support the negotiation of licenses.
  • Licensing negotiations currently involve multiple exchanges of paper documents between HFA and other parties involved in the negotiation. Transferring the bulk of these exchanges onto an electronic system can significantly help the HFA. This is because paper processes involve personnel who are responsible for receiving paper documents and scanning them into a document management system where they are given an identification code. There is no explicit business reason why these documents must exist in hart-copy form until the final license is generated.
  • the system will support licensing-related negotiations by consolidating all pertinent data onto easy-to-use display screens. These display screens replace intermediate document exchange steps between the commencement of negotiations and the generation of licenses that are currently paper-based.
  • These display screens will be comprised of:
  • the system will provide functionality to display model contracts or working copies of contracts. These contracts may be printed out at the user's discretion. This will eliminate the need to print and deliver hard-copy drafts of contracts to involved parties during the negotiation process.
  • the Songfile.com search engine which is live on the internet, provides searches via song, writer, album and artist over the HFA song and license database.
  • the results from the search shows consumer information about the song (or whatever was searched over), including links to partner sites for CD's, sheet music, audio clips, and lyrics.
  • HFA would like to extend this search, for use by authorized users of the professional area of the site, to allow music professionals to also find information on the owner/music publisher for a particular song. Additionally, this will feed into a SIRNET style licensing request form for manufacturers.
  • NMAST Name and Address file
  • Multi-manufacturers Some SIRNET manufacturers are registered as “Multi-manufacturers”. This means that they have a unique, but dummy M-number - and the ability to act on behalf of several other manufacturers. The relationships between multi-manufacturers and their "child” manufacturers is maintained in file “PFMLCHM”:
  • the generated User Names and Passwords will be stored in a database file and accessed by the web-server during user-authentication.
  • this file will be used as the basis for an automatic mass-email to all valid users. Included in the e-mail would be:
  • An account registration form similar to the paper version below (with an additional form field for e-mail address and perhaps web-site) will be provided on the Intemet.
  • the information entered into this form will be passed to the index department to complete the application. This will not be an automatic account registration, simply a request.
  • the professional search will extend the search capabilities of the Intemet songfile.com site by allowing two search criteria.
  • the search options on songfile.com will be duplicated with the first search criteria defaulting to a song search and the secondary part of the search defaulting to a writer search - similar to the current SIRNET offering. If the user fills in both search criteria, then the search engine will do an AND search - which means the results must match both criteria.
  • each of the two parts of the search will be conducted individually, then the results will be cross- referenced to provide the user with the intersection of the two searches.
  • the first search will determine the type of results to be displayed. In the above case, songs are displayed because the first search criteria was by "song".
  • the search results list for songs must be extended to include the Song Code and the Publisher name(s).
  • Each publisher name will be a link to a publisher detail page - descnbed below.
  • a new web page 3 will be designed which shows, for a selected publisher, its contact information, and address. This page will be display only - the users will not be able to change any of the information on the page- Since Harry Fox will be extending their Name and Address file to include e-mail address and web-site, it is possible to mclude this information as well, if desired.
  • the goal is to have these licenses handled by the system in as similar a fashion as possible.
  • a manufacturer can click on the license icon in the upper frame. Then s/he will be guided through a series of Questions to help determine the type of license that s he requires. Then, the user will build a "shopping cart" full of songs by using the professional search functionality 4 . Then, a separate license is required for each song, the user can specify information with each song being requested.
  • the SIRNET license request files be updated to include a ''source of license request" flag. This would allow Harry Fox to distinguish between a request originating from the Extranet versus one received by the SIRNET client-server application.
  • DPD Digital Phono Download
  • licenses are for digitized music files that can be passed around and downloaded via the Intemet (or via computer media like diskettes).
  • DPD is simply one of many different configurations (CD, Cassette, LP, ...) available to the user.
  • the volume of recordings will be restricted (e.g. 500 or less)
  • the DPD configuration will only be available to authenticated manufacturers, not to die general public (i.e. not for 35.50 licenses).
  • HFA offers restricted mechanical licenses to those individuals which want to produce a small volume of mechanical recordings (e.g. 500 or less). These types of licenses will now be handled by the Songfile.com web-application.
  • the user will be guided through a series of questions to help determine the type of license that s he requires. Then, the user will build a "shopping cart" full of songs by using the existing SongFile search functionality 4 . After a user has filled his/her license shopping cart with songs, and after the information they provide for each song recording has been automatically validated, a confirmation page will appear, asking the user to provide their personal 5 and payment information.
  • the user's credit card information will be automatically approved over the web. This typically requires as little as 5-15 seconds, using one of the available payment service providers - discussed below. Upon approval, the user will be immediately notified via a web page.
  • the following Diagram depicts the proposed flow for a user to obtain 35.50 licenses for several songs.
  • the user's credit card information will be automatically approved over the web This typically requires as little as 5-15 seconds, using one of the available payment service providers - discussed below Upon approval, the user will be immediately notified via a web page.
  • the Bank and/or payment service provider offer less expensive transaction fees if the user provides name and address information.
  • the user's e-mail address is also required, so their license can be distributed.
  • SSL pages are sent and received on a separate TCP/IP port - usually 443. License inquiry
  • the user will also have the ability to search for his/her own Ucense requests and Ucenses by providing a date range. Since the user has authenticated his/herself, s/he will be able to see only his/her own Ucense information. In other words, license information will be secured to Harry Fox and the Ucensee.
  • a set of Rights Determination Q&A will ask the user a series of questions - which will determine the rights they are seeking.
  • a Black-box function will take in a list of songs and configurations and, by accessing new and existing database files, will determine if each can be [partially] licensed to the user by Harry Fox.
  • This part of the system will ask the user a set of pre-determined multiple-choice questions.
  • the rights the user requires will be based on their answers to the questions.
  • s/he may be eligible for a restricted mechanical license (35.50 license). Otherwise, s/he must authenticate as a manufacturer.
  • This part of the system will take in a list of songs and configurations and, by accessing new and existing database files, will determine if each can be [partially] licensed to the user by Harry Fox.
  • the user has already selected a set of songs and configurations; no further user mput is required.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Multimedia (AREA)
  • Technology Law (AREA)
  • Computer Hardware Design (AREA)
  • Computer Security & Cryptography (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Storage Device Security (AREA)

Abstract

La présente invention concerne, en général, un système et un procédé qui permettent d'enregistrer en un seul processus des oeuvres de l'esprit dans une base de données en ligne (100) et auprès de plusieurs agences d'octroi de licences, de sociétés de perception de droits de reproduction et de bureaux de droits d'auteur, et de fournir des informations concernant la concession de licences relatives aux oeuvres enregistrées. L'invention permet à des personnes d'identifier une oeuvre de l'esprit particulière parmi de nombreuses variantes proches, d'analyser les droits de licence (143-148) nécessaires à une utilisation précise de l'oeuvre par une personne sur un territoire déterminé, à identifier la source des droits de licence (151) sur ce territoire déterminé et à transmettre une demande de licence à ladite source (152). Enfin, dans un mode de réalisation préféré, l'invention peut délivrer à une personne une licence (154) qui lui permettra d'utiliser une oeuvre souhaitée.
EP00904328A 1999-01-12 2000-01-12 Procede et systeme permettant d'enregistrer des oeuvres de l'esprit et de conceder des licences relatives a ces oeuvres sur un reseau Withdrawn EP1062605A1 (fr)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US11560699P 1999-01-12 1999-01-12
US115606P 1999-01-12
PCT/US2000/000835 WO2000042555A1 (fr) 1999-01-12 2000-01-12 Procede et systeme permettant d'enregistrer des oeuvres de l'esprit et de conceder des licences relatives a ces oeuvres sur un reseau

Publications (1)

Publication Number Publication Date
EP1062605A1 true EP1062605A1 (fr) 2000-12-27

Family

ID=22362399

Family Applications (1)

Application Number Title Priority Date Filing Date
EP00904328A Withdrawn EP1062605A1 (fr) 1999-01-12 2000-01-12 Procede et systeme permettant d'enregistrer des oeuvres de l'esprit et de conceder des licences relatives a ces oeuvres sur un reseau

Country Status (4)

Country Link
EP (1) EP1062605A1 (fr)
AU (1) AU2610300A (fr)
CA (1) CA2323427A1 (fr)
WO (1) WO2000042555A1 (fr)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9336360B1 (en) 2013-03-14 2016-05-10 Kobalt Music Group Limited Analysis and display of a precis of global licensing activities
USD773491S1 (en) 2013-03-15 2016-12-06 Kobalt Music Group Limited Display screen with a graphical user interface
USD773492S1 (en) 2013-03-15 2016-12-06 Kobalt Music Group Limited Display screen with a graphical user interface
USD773490S1 (en) 2013-03-15 2016-12-06 Kobalt Music Group Limited Display screen with a graphical user interface
US10319040B1 (en) 2013-03-14 2019-06-11 Ktech Services Limited Control of the generation and display of royalty administration and rights management data based on the user's rights of access
US11625800B2 (en) 2013-04-29 2023-04-11 B Media Finance Methods and systems for visualizing media rights management

Families Citing this family (23)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2359696A (en) * 1999-10-26 2001-08-29 Michael James Gill Obtaining licenses in order to retrieve music via a radio signal from back catalogues held at broadcasting stations and playing on radio receiving devices
GB2368245A (en) * 2000-10-17 2002-04-24 Mode Internat Ltd Distribution system for digital works with associated metadata
EP1209581A3 (fr) 2000-11-27 2004-05-26 Yamaha Corporation Système de recouvrement d'information et procédé de recouvrement d'information en utilisant un reseau
US7505936B2 (en) 2001-05-11 2009-03-17 Accenture Global Services Gmbh Digital content subscription conditioning system
US7725401B2 (en) * 2001-05-31 2010-05-25 Contentguard Holdings, Inc. Method and apparatus for establishing usage rights for digital content to be created in the future
US7395245B2 (en) * 2001-06-07 2008-07-01 Matsushita Electric Industrial Co., Ltd. Content usage management system and server used in the system
US7895123B1 (en) * 2001-06-12 2011-02-22 Accenture Global Services Limited Digital content publication
US7249139B2 (en) 2001-07-13 2007-07-24 Accenture Global Services Gmbh Secure virtual marketplace for virtual objects and services
US20030046093A1 (en) * 2001-08-30 2003-03-06 Erickson John S. Rights management
EP1468355A4 (fr) * 2002-01-22 2005-11-16 Recording Ind Association America Procede et systeme pour l'identification de sorties et de licences de l'industrie de la musique
JP4424721B2 (ja) * 2003-06-11 2010-03-03 キヤノン株式会社 ライセンス情報発行サーバ
JP4371711B2 (ja) 2003-06-11 2009-11-25 キヤノン株式会社 情報処理装置およびその制御方法、並びに、コンピュータプログラム
US7953083B1 (en) 2006-12-12 2011-05-31 Qurio Holdings, Inc. Multicast query propagation scheme for a peer-to-peer (P2P) network
US8135018B1 (en) 2007-03-29 2012-03-13 Qurio Holdings, Inc. Message propagation in a distributed virtual world
US8116323B1 (en) 2007-04-12 2012-02-14 Qurio Holdings, Inc. Methods for providing peer negotiation in a distributed virtual environment and related systems and computer program products
US8000328B1 (en) 2007-05-22 2011-08-16 Qurio Holdings, Inc. Filtering messages in a distributed virtual world based on virtual space properties
US8433656B1 (en) 2007-06-13 2013-04-30 Qurio Holdings, Inc. Group licenses for virtual objects in a distributed virtual world
US8260728B1 (en) 2008-12-12 2012-09-04 Qurio Holdings, Inc. System and method for influencing behavior in a distributed virtual environment
US20110106673A1 (en) * 2009-04-21 2011-05-05 Music Reports, Inc. Methods and systems for identifying musical compositions in a sound recording and licensing the same
US20110231322A1 (en) * 2010-03-16 2011-09-22 Copyright Clearance Center, Inc. Automated rules-based rights resolution
WO2014026058A1 (fr) * 2012-08-08 2014-02-13 Qbeats Inc. Système de création et de distribution de contenu avec estimation automatique, avant la publication, de valeurs et/ou de lecteurs de réponses à des questions publiées à distance et mettant les résultats à disposition d'éditeurs potentiels de réponses situés à distance
US11062336B2 (en) 2016-03-07 2021-07-13 Qbeats Inc. Self-learning valuation
CN109740773A (zh) * 2019-01-22 2019-05-10 吉林省民航机场集团公司 信息化民用航空器维修信息系统

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
AU2247092A (en) * 1991-05-08 1992-12-21 Digital Equipment Corporation License management system
US5940504A (en) * 1991-07-01 1999-08-17 Infologic Software, Inc. Licensing management system and method in which datagrams including an address of a licensee and indicative of use of a licensed product are sent from the licensee's site
US5715403A (en) * 1994-11-23 1998-02-03 Xerox Corporation System for controlling the distribution and use of digital works having attached usage rights where the usage rights are defined by a usage rights grammar
US5758069A (en) * 1996-03-15 1998-05-26 Novell, Inc. Electronic licensing system
US5805699A (en) * 1996-05-20 1998-09-08 Fujitsu Limited Software copying system
US6006332A (en) * 1996-10-21 1999-12-21 Case Western Reserve University Rights management system for digital media

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See references of WO0042555A1 *

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9336360B1 (en) 2013-03-14 2016-05-10 Kobalt Music Group Limited Analysis and display of a precis of global licensing activities
US10319040B1 (en) 2013-03-14 2019-06-11 Ktech Services Limited Control of the generation and display of royalty administration and rights management data based on the user's rights of access
USD773491S1 (en) 2013-03-15 2016-12-06 Kobalt Music Group Limited Display screen with a graphical user interface
USD773492S1 (en) 2013-03-15 2016-12-06 Kobalt Music Group Limited Display screen with a graphical user interface
USD773490S1 (en) 2013-03-15 2016-12-06 Kobalt Music Group Limited Display screen with a graphical user interface
US11625800B2 (en) 2013-04-29 2023-04-11 B Media Finance Methods and systems for visualizing media rights management

Also Published As

Publication number Publication date
AU2610300A (en) 2000-08-01
CA2323427A1 (fr) 2000-07-20
WO2000042555A1 (fr) 2000-07-20

Similar Documents

Publication Publication Date Title
EP1062605A1 (fr) Procede et systeme permettant d'enregistrer des oeuvres de l'esprit et de conceder des licences relatives a ces oeuvres sur un reseau
WO2000042555A9 (fr) Procede et systeme permettant d'enregistrer des oeuvres de l'esprit et de conceder des licences relatives a ces oeuvres sur un reseau
JP5665273B2 (ja) メディアアイテム及び複合メディアアイテムとの関連付けのためのデータコンテナ及びメタデータセット
US8260713B2 (en) Web-based system providing royalty processing and reporting services
RU2213368C2 (ru) Система интерактивной web-книги (книги сети интернет)
US6697821B2 (en) Content development management system and method
US7092953B1 (en) Apparatus and methods for intellectual property database navigation
CA2278727C (fr) Systeme de distribution d'informations accordant des autorisations en ligne et procede correspondant
US20050246377A1 (en) Method and apparatus for a commercial computer network system designed to modify digital music files
US20070180020A1 (en) System, Method, and Computer Program Product for Internet Tool
CA2361916A1 (fr) Distribution de produits musicaux par internet
CA2569453A1 (fr) Creation et gestion de sites web de communaute d'interet commun
JP2006172447A (ja) 記録媒体とネットワークとの連携装置、再生装置
US20120030230A1 (en) Method and System for Gathering and Pseudo-Objectively Classifying Copyrightable Material to be Licensed Through a Provider Network
KR20020082201A (ko) 디지털 학습 콘텐츠의 생성 촉진 및 제어, 유통 방법
United States. Congress. Office of Technology Assessment Accessibility and integrity of networked information collections
Ginsparg First steps toward electronic research communication
Loghry et al. Managing Selection and Implementation of Electronic Products
Gervais Electronic rights management systems
US20020107700A1 (en) System and process for capturing, storing, maintaining and reporting information regarding databases via the internet
JP2002318892A (ja) コンテンツ提供方法および装置
JP4329228B2 (ja) 楽曲提供システム
Yoon et al. Examination of data citation guidelines in style manuals and data repositories
Tamizhchelvan et al. Digital Object Identifier In Effective Media Library Management-An Indian Perspective.
Farsetti et al. District architecture for networked editions: technical model and metadata

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20001010

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LI LU MC NL PT SE

AX Request for extension of the european patent

Free format text: AL PAYMENT 20001010;LT PAYMENT 20001010;LV PAYMENT 20001010;MK PAYMENT 20001010;RO PAYMENT 20001010;SI PAYMENT 20001010

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION HAS BEEN WITHDRAWN

18W Application withdrawn

Withdrawal date: 20020107