CA2431341A1 - Digital asset data type definitions - Google Patents

Abstract

Data definitions for digital assets, such as, for example, audio, video, photographs, graphics, and electronic documents, are provided that allow the se different asset types to be stored in a single database. The definitions are preferably in XML and can be used as a standardarized dictionary to more efficiently and economically manage digital assets, thus improving system interoperability between companies or organizations within a company. A digital asset ordering interface, hardware system, software arrangement, and application interface configuration advatageously using these data definitio ns are also provided.

Description

DIGITAL ASSET DATA TYPE DEFINITIONS
Background of the Invention This invention relates to storing, retrieving, and tracking digital data. More particularly, this invention relates to data definitions that allow disparate types of digital assets, such as, for example, photographs, graphics, audio, n~ideo, and text documents, to be easily and economically stored, retrieved, and tracked.
Data definitions may be written using XML
so (extensir;le markup language). xML is a condensed form of SGML (standard generalized markup language), which is an informata_on management standard that provides documents that retain formatting, indexing, and linked information --independent of application and platform. xML and SGML can be z5 used to organize and present information on the World Wide Web.
Many companies maintain or access large libraries of various audio, visual, and textual assets. Such assets typicall.~r include content and metadata. Content may be, for ~o example, still photographs, audio recordings, video recording's, combined audio/video recordings, combined audio/stiil photograph recordings, graphics, etc. Metadata is "info::~mation about information," that is, information used to identify or classify the content. Metadata can include, for example, content titles, version numbers, authors, captions, and other descriptive information relevant to the content.
s Such assets are often stored in disparate repositories and on disparate media (e. g. audio and video cassette tapes, motion picture film, photographic negatives, digital video discs, etc.). Accordingly, a significant amount of time is often required to locate a particular asset to and then deliver a copy of it. For example, it may take several days to locate and manually copy an audio track stored on a reel-to-reel tape located at a creative services or marketing department of a company in California and then have that copy shipped to a business affairs department or is sister company in New York. This process, known as repurposing, is manually intensive and prone to errors.
Furthermore, keeping track of asset usage (e.g., who has asset copies) is also a manually intensive process prone to errors. Accordingly, it can cost thousands or even millions 20 of dollars annually for a company to manage such assets.
In an attempt to reduce these costs, some companies store assets digitally in one or more computer databases.
These assets can then be retrieved electronically using appropriate software applications. However, known z5 applications are limited. For example, databases are commonly structured to store only one type of digital asset, such as, far example, only photographs. The number, size, and formats of record fields used in the database, characters delimiting the end of files, file size of database records, so etc. are all usually customized (and limited) to that one type of asset. Even those few databases that are known to store more than one asset type are also limited with respect to record field definitions and record file size, making them incompatible for use with many other types of digital assets.
35 Such databases are thus impractical for storing a large variety of different types of digital assets.

In sum, storing disparate asset types in a single repository having information and formatting sufficient for identification and retrieval by a single software application or computer platform is not known. Moreover, no standardized definitional dictionary for digital assets is known. Thus, system interoperability between two or more companies or two or more organizations within a company having different types of digital assets is still very difficult.
In view of the foregoing, it would be desirable to so be able to provide a standardized dictionary of data definitions for disparate types of digital assets.
It would also be desirable to be able to provide data definitions for application and platform independent search, retrieval, delivery, and tracking of digital assets.
It would further be desirable to be able to provide data definitions that reduce digital asset search time.
It would still further be desirable to be able to provide data definitions that reduce digital asset delivery time.
2o Summarv of the Invention It is an object of this invention to provide a standardized dictionary of data definitions for disparate types of c'4igital assets.
It is also an object of this invention to provide z5 data definitions for application and platform independent search, retrieval, delivery, and tracking of digital assets.
It is a further object of this invention to provide data definitions that reduce digital asset search time.
It is a still further object of this invention to 3o provide data definitions that reduce digital asset delivery time.
In accordance with this invention, data definitions are provided for digital assets that include a hierarchical structure that reflects the relationships between attributes 35 and categories of content. These definitions, preferably encoded in XML, can be used as a standardized dictionary to create a digital asset library that is easily and economically manageable. The data definitions are applicable to digital~assets of disparate data types and include s metadata identifiers sufficient to uniquely identify those digital assets.
Brief Description of the Drawings The above and other objects and advantages of the invention will be apparent upon consideration of the to following detailed description, taken in conjunction with the accompanying drawings, in which like reference characters refer to like parts throughout, and in which:
FIG. 1 is a flow chart of an interface for ordering digital assets using data definitions according to the 15 invention;
FIG. 2 is a block diagram of an embodiment of a hardware System within which the invention can be used;
FIG. 3 is a block diagram of an embodiment of integrated software according to the invention;
zo FIG. 4 is a block diagram of an embodiment of an application interface configuration according to the invention;
FIG. 5 shows an embodiment of a display screen for asset searching according to the invention;
25 FIG. 6 shows an embodiment of a display screen for search results according to the invention; and FIG. 7 is a high level block diagram showing an embodiment of a document type definition (DTD) for digital assets according to the invention.
so Detailed_Description of the Invention The invention provides data definitions, preferably in XML, for disparate types of digital assets, such as, for example, artwork, logos, photographs, video, graphics, music, still photographs, promotion stills, promos (e. g., an audio 35 or vide~:~ promotional announcement), tapes, soundtracks, text, video fr~~.mes (a single image from a video recording), video clips (a group of images from a video recording), and dailies (unedited and unprocessed video or film typically recorded the previous day). Digital assets include content (i.e., the actual asset data) and metadata. Data definitions of the invention advantageously permit a single database to be used for storing, retrieving, and tracking different types of assets whose contents are preferably stored either on the same corlputer as the database, in the database, on a computer to linked to the database via the same network, or combinations thereof. These data definitions allow, for example, employees, affiliates, and customers to relatively easily and economically replicate or transfer assets between repositories where the assets are located and destinations i5 where the assets are currently needed. Furthermore, electronic records can be created to allows usage of those assets '~o be easily tracked. Thus, the costs associated with managing those assets are significantly reduced.
FIG. 1 shows an interface for searching and 20 ordering digital assets facilitated by the invention. System Home Screen 101 is preferably the first screen a user views when searching for a digital asset (e. g., a video program).
While at Home Screen 101, users may enter search criteria before proceeding to another screen. However, this is 25 alternatively not necessary: From Home Screen 101, the user may proceed in one of the following ways: along path 102 to Login Screen 103, along path 104 to Register Screen 105, along path 106 to Advanced Search Screen 107, along path 108 to Top Picks Screen 109, along path 110 to Latest Releases 3o Screen 111, or along path 112 to Editor's Choice Screen 113.
At Login Screen 103, users login to a secured version of a search system associated with interface 100. A
user entering Login Screen 103 along path 102 is preferably directeca along path 114 to User Home Screen 115 unless the 35 user entered search criteria while viewing Home Screen 101.
In that case, the user is preferably directed to Order Confirmation and Download Screen 117 along path 116.
Similarly, if the user entered Login Screen 103 along path 127, the user is also preferably directed to Order Confirmation and Download Screen 117.
At Register Screen 105, users register to use the system. Users may be assigned or may freely choose a username, password, and any other relevant identifying information. Users may be prompted by Register Screen 105 to enter information deemed relevant or necessary by the system.
so After registering, users are preferably directed along path 118 to User Home Screen 115.
At Advanced Search Screen 107 users enter or are given pre-defined criteria with which the database of the invention can be searched. Soreen 107 preferably allows z5 users to generate advanced search criteria including, but not limited to, searching specific strings, numeric values, fields or combinations of fields containing data, as well as allowing users to define complex or simple search expressions using boolean or other logic, wildcards, multiple search ao criteria, or any other type of search functionality.
Preferably, upon an indication by a user or upon a pre-defined system event (for example, expiration of a timer), a user will be directed along path 119 to Search Results Screen 120.
25 At Top Picks Screen 109, a user can view and select from a subset of assets defined in the database. This subset may be predefined by the user, the system, or.a system administrator. The subset may be defined as the most viewed assets, most searched for assets, most retrieved assets, most 3o popular assets, or top assets based on a criteria defined by a user, the system, or an administrator.
At Latest Releases Screen 111, a user can view and select from a subset of assets in the database. This data is preferably a subset of the most recently added assets in the 35 database. However, the subset may be defined as the most recently released assets, most recently produced assets, or any othar desired subset of data in the database.
At Editor's Choice Screen 113, a user can view and select from a subset of assets defined in the database. This subset is preferably a selection of assets that one or more editors, within the company or organization viewing or providi~zg the database, has selected as being desirable for viewing based on one or more criteria defined by the editors.
At User Home Screen 115, a user can view to personalized or standard information relating to that user's usage of the database. The system may present the user with search possibilities, the ability to view some subset of assets defined in the database, a listing of data that may be useful in some respect, and any other relevant information or functional possibilities. Preferably, upon an indication by a user or upon a pre-defined system event (for example, expiration of a timer), the user is directed along path 122 to Content Detail Screen 123.
At Search Results Screen 120, a user can view and 2o select from a subset of data retrieved in accordance with criteria defined by the user while viewing Advanced Search Screen 107 and possibly in accordance with one or more database enforced criteria. Upon indicating a selection of one or mere assets, a user is directed along path 121 to Content Detail Screen 123.
In addition to being directed along path 121 or 122 as described, a user may be directed along path 124 from any of screens 109, 111, or 113 to Content Detail Screen 123. A
user n?ay be automatically directed to screen 123 if a small 3o number of asset definitions are the only items the user wishes to view. For instance, if a user performs a complex search :~.nd the system finds only one asset satisfying the search criteria, the system may automatically bypass Search Results Screen 120 and display Content Detail Screen 123.
At Content Detail Screen 123, a user can view all or part c~f the summary data directly related to one or more _ g _ items selected manually or automatically by the user.
Preferab:'.y, upon an indication by the user or upon a pre-defined system event (for example, expiration of a timer), a user is directed along path 125 to Order Options Screen 126.
At Order Options Screen 126, a user can view and select from options related to ordering and downloading data for which summary data was viewed while viewing Content Detail Screen 123. These options may include billing, to routing, formatting, data transmission, delivery date, delivery time, and other relevant options. Upon indication by a user or upon a pre-defined system event, the user is directed along path 127 to Login Screen 103 or along path 128 to Order Confirmation And Download Screen 117. Preferably, a user is directed along path 127 when the user has not logged in using Login Screen 103. Alternatively, a user is directed along path 128 when the user had previously logged in via Login Screen 103. In some systems, logging in is not necessary. In other systems, a user that has logged in but ~o has not taken any decisive action (for instance, has not made an indication at Order Options Screen 126 within a specified amount of time after logging in) is directed along path 127.
At Order Confirmation And Download Screen 117 the system preferably displays details and summary information relating to an asset that was ordered by a user. The user is preferably presented with the opportunity to download or retrieve the asset. Such retrieval may be performed either electronically or by using devices (such as printers, tape recorders, compact disc writers, digital video disc writers, or other recording or printing equipment) to convert an asset stored in a database or in an associated or networked computer' memory to a digital or analog item stored in another manner.
Note that any of paths 102, 104, 106, 108, 110, 112, 114, 116, 118, 119, 121, 122, 124, 125, or 128 may be traversed in reverse by users that wish to step backwards in the search and ordering process. Also, securing the search system is not a necessary function of the invention. Note further that all of interface 100 is not necessary for implementing the invention; an interface employing even a very small~subset of interface 100 can benefit from the invention. Moreover, additional process paths and functionality (for instance, paths connecting any of screens 109, 111, 113, 115, and 123 directly to Search Results Screen 1?0 to allow a user to view search results from a io search performed while viewing any of those screens) can be added to interface 100.
In sum, the data definitions of the invention enable systems using interface 100 or similar interfaces to provide satisfactory interactive search and response times to users .
FIG. 2 shows a hardware system 200 that can be used to manage digital data defined with data definitions in accordance with the invention. System 200 preferably includes one or more servers 201, a secure transmission line 202,, at least one secure recording or printing device 203, one or more secure access devices (e. g., laptop 204, computer 205, and workstation 206), at least one firewall 207, one or more non-secure transmission lines 208, one or more non-secure access devices (e. g., computer 209, workstation 210, and laptop 211), and at least one non-secure recording or printing device 212.
One or more servers 201 store all or part of one or more databases. Servers 201 may be accessed via secure transmission line 202 by secure access devices 204-206 or by 3o firewall 207 which has received appropriate indications from non-secure access devices 209-211 via non-secure transmission line 208, Upon receiving appropriate indications from devices 204-206 or firewall 207, servers 201 transmit data to devices 204-206, firewall 207, or recording or printing device 203; as appropriate, via secure transmission line 202.

Upon receiving appropriate indications (based on security criteria), firewall 207 transmits data to non-secure access c~.evices 209-211 or non-secure recording or printing device 212, as appropriate, via non-secured data transmission line 203.
Secure access devices 204-206 and non-secure access devices 209-211 can include laptop computers, desktop computers,. and workstations (as shown), as well as other types of terminals, wireless devices, personal digital to assistants (PDAs), television set-top boxes, other databases, and other digital devices that can receive user indications and can communicate with servers or firewalls.
Severs 201 can be, for example, Sun~ servers using the Solaris° platform, Oracle~ database servers, or any other appropriate server platform. Transmission lines 202 and 208 may use T-1, T-2, or any other appropriate transmission standards. Alternatively, the invention can be practiced with a configuration as simple as a single computer that can do the following: store and query a database in its RAM, ROM, 2o hard ~.~isk drive, compact disc, floppy disk, or other suitable storage medium; display visual or play audio content; and receive user indications.
FIG. 3 shows an embodiment of integrated software according to the invention. Computer 301 (which may be any z5 of secure access devices 204-206, firewall 207, and non secure access devices 209-211) communicates with servers 201.
Project applications 303, which are preferably encoded in XML, transmit a demand 304 for database information to database 305. Database 305 may be, for example, Oracle°, 3o Sybase~, Microsoft Access°, or any other relational or non-relational database package. Database 305 creates preferably XML files 306. An example of an XML file 306 is shown in Example 2 below. XML files 306 are transmitted in HTML format 307a for viewing graphics with a browser 308.
35 Microsoft Internet Explorer~ and Netscape Navigator° are two examples of browsers that may be used. Preferably, format 307a is HTML with cascading style sheets (CSS).
Alternatively, XML files 306 may be transmitted in XML format 307b for use by other applications 309, such as, for example, C, C++, or Java applications that may be for a stand-alone screen, front-end GUI, or Web presentation package. Alternative format 307b may include XML with CSS
for further processing by applications such as search engines or both or may include regular HTML if a still or active to display is the only output requirement. Bots are programs that typically perform repetitive or time consuming tasks on a network (e. g., searching Web sites on the Internet).
Examples of formats 307a and 307b are shown below in Examples 3a-c.
FIG. 4 shows an embodiment of an application interface configuration in accordance with the invention. In this configuration, a user provides search parameters 401 to client application 402, which is active on computer 301.
Client application 402 converts search parameters 401 into a 2o demand 304 for database information. Demand 304 may take the form of an SQL (structured query language) query when database 305 is an SQL-based relational database.
Preferably, however, server 201 processes demand 304 in a server application 404. Server application 404 preferably a5 includes the following modules: an XML parser 414, an XSL
processor 424, and an XML-SQL utility 434. XSL (extensible style sheet language) is a language for specifying style sheets E~hat apply formatting to complex XML data for presentation in HTML and other formats. XSL can map a single so XML element to more than one type of display object (e. g., both an element in a list and an item in a table). A style sheet is a text file containing code to apply semantics such as page layout specifications to an HTML document.
After converting demand 304 to SQL format (if s5 necessary depending on the database), application 404 sends query ~.~05 to database 305. Database 305 processes query 405 and r:~turns search results 406 to application 404.
Applicat:LOn 404 then processes results 406 to create one or more XMi.~ files. These XML files are sent by application 404 as data 417 to XSL style sheet 408. XSL style sheet 408 processes data 407 and returns a response 307 in format 307a or 307b, as appropriate. Client application 402 then converts response 307 into a format that can be heard or viewed bay the user.
FIG. 5 shows an example of a display that can be so used a.~:, 7~dvanced Search Screen 107. Illustrative display 501 includes interactive features 502, 503, 504, and 505.
Display' 501 may alternatively include more or less interactive features as appropriate for a given implementation of the invention. Interactive feature 502, entltleCJ. "PLEASE ENTER KEYWORDS TO SEARCH, " accepts user entries of keywords or phrases to be used by XML project applicati~~ns 303 when forming demand 304. For example, "Oscar bcllt" may be entered via interactive feature 502 by a user sea-.~r:hing for a picture that has metadata containing the 2o descript~.on, "Oscar Delahoya wearing a championship belt."
Interaci_ive feature 503, entitled "PLEASE SELECT ASSET CATEGORY,"
accepts ~.zser entries for the type of asset to retrieve. For example, possible asset types are photos, audio, video, text, any cor.~'nination of these, or any other appropriate asset type. Interactive feature 504, entitled "SEARCH," allows users to submit a search request (i.e., have application 303 form a remand 304). Interactive features 505, entitled "DTD," ~'XML," "XSL," and "XSL SS," allow a user to select a source co~ae format in which to view data instead of viewing a so composed ~~rideo screen or hearing a composed audio output.
FIG. 6 shows an example of a display that can be used as ~~earch Results Screen 120. In this example, illustr<<~ive display 601 indicates at 602 that 4 photo assets, 1 video asset, and 1 audio asset had been found, and shows at 603 a list of photographic assets, that met the criteria. of a demand 304. Illustrative display 601 preferably includes features 604, 605, 606, and 607.
Alternati~sely, display 601 can include more or less features as desired for a given implementation of the invention.
Features 604 interactively accepts user indications of selection or rejection of assets from the displayed list of assets. Features 605 may be interactive (e.g., a button) or static (e.g., just a display). In this example, feature 605 displays an image of the assets associated with the retrieved list items. If feature 605 is interactive, it can accept a so user's selection of an asset to be ordered. Feature 606 displays descriptive information associated with the assets that met the criteria of demand 304. Feature 606, like feature 605, may be interactive to accept user selections of an asset. Feature 607, entitled REORDER CHECKED, ° is interactive and accepts indications that a user has finished selecting assets arid is ready to proceed along path 121 to Content Detail Screen 123.
FIG. 7 shows an embodiment of a document type definition.(DTD) in accordance with the invention. A DTD is 2o a separate file or document that contains formal definitions' of all 'she data elements in a particular type of XML (or HTML
or SGML) document, such as a report or a book. By consulting the DTD for a document, a program called a parser (e.g., XML
parser 414) can work with the markup codes that the document contains. DTD 700 includes asset element 701, which defines the type of data to be stored for each digital asset.
DTD 700 m%~y also include one or more other data elements 702 for other uses. For example, asset element 701 can contain a core set of definitions, while data element 702 can contain 3o additional definitions that augment the core set in cases where such additional definitions are required by a particular user.
Asset element 701 preferably includes asset metadata 703, asset type data 704, and asset content 705.
Asset element 701 may also include additional definitional information as desired. Asset metadata 703 preferably includes the following definitional elements: product identii:ier (ID) (e.g., a video program name), version ID, inventory ID, and ownership rights ID. Asset metadata 703 can also include any subset of these identifiers or any additional identification information.
Asset type data 704 advantageously can include any number of definitional elements relevant to a particular type of asset., Table 1 is a preferred embodiment of asset type data 704 in accordance with the invention, showing to definitional elements for classifying five asset types:
Table 1 ASSET Photo Movie Audio Promo Voiceovers TYPE u~

Metadata Ad Slick Version Music On-Line Announcer edit Agency Rating Stock Airmaster Session # Date Approved Minutes Library EE Master 1 st air # date Arcluve Seconds Sub LibraryTextless Residual . # payment Art DirectorDate CD # Writer/ Production Producer company Black/White AIWA TitleCD Title Duration Agency Box m Type Track Music Telephone Title #

Caption Genre Duration Announcer Fed m#

Character Caption Composer Cut versionsAddress Client Title PublisherGraphics Color Licensor Society Promo Dub Comments Release Shoot Date Material ~ Discard DateRating Original EPIC
I ~ I

Entry Date Foreign Code Trailer Lang.

Storage DateRun Time Title Kill Date Department ColorBW Duration Comments Final art Director Session DAT
DT

Job number Cast Composer Script Licensor Brief PublisherEDL
Synopsis Off site P Version Society Screening storage Format notes PhotographerSynopsis Rights Internet Issues rights I Product ID Product Contract ID (lic.) Poster Art Version Internet ID

Press Kit Contract W ternation ID al Version ID Run code Library Contact Project SAP
Number Resolution Restrictions I Shoot date Talent Title Note that the elements defined in Table 1 are illustrative and thus are neither required nor exclusive of other elements.
Asset content 705 preferably includes one of the following: digitally encoded asset data, a link. to a file containing asset data, or a reference to a location where asset data is digitally stored. Alternatively and less preferable, multiple copies of a digital asset can be referenced or included in asset content 705.
An embodiment of DTD 700 for digital assets, which includes asset element 701, asset metadata 703, asset type data 704, and asset content 705, is shown below in Example 1 in accordance with the invention.
Example 1 <! -DTD FOR DIGITAL ASSETS ->
<! -Digital Library Data Definition ->
<! -Supporting technologies include but not limited to XML, XSL, XSLT, XPATH, DTD
Schema->
<lELEMENT digitalAsset (assetMetadata, movieTitleMetadata?, rightsMetadata, transactionMetadata?, Photo*, Promo*, Audio*, Movie*,)>

<! ELEMENT assetMetadata (#PCDATA)>

L5 <! ATTLIST assetMetadata AssetTitle CDATA #IIVVIPLIED-this asset package has a name-AssetComments CDATA #REQUIRED -comments/description about the asset group-AssetVersion CDATA #REQUIRED -version, major+minor-AssetCreateDate CDATA #REQUIRED -create date-a0 >

<!ELEMENT , movieTitleMetadata (#PCDATA)>

<! ATTLIST movieTitleMetadata PID CDATA #REQUIRED -product id; link to PRIME.PPROD-VD7 CDATA #REQUIRED -PEG--version id; LINK
TO
prime/pversion general-5 RID CDATA #REQUIRED -rights id, for FUTURE
use-Genre CDATA #REQUIRED -PEG genre, may be several genres [ ]
FUT make multiple elements?-Rating CDATA #REQUIRED -PEG MPAA information-movieTitleLong CDATA #REQUIRED -PEG the movie title, full name with all punctuation-movieTitleShort CDATA #REQUIRED -PEG abbreviated movie ~ title, suitable for computer filenames; no blanks, special chars-movieTitleAKA CDATA #IMPLIED -alternate movie name;
different countries-StudioProvider CDATA #IMfLIED -PEG--copyright owner or provider of tape-Director CDATA #REQUIRED -PEG--movie director-Cast CDATA #REQUIRED -PEG cast members, talent [ ] FUT make multiple elements?-SynopsisBrief CDATA #REQUIRED -PEG short description-LO SynopsisLong CDATA #REQUIRED -full description-Languages CDATA #REQUIRED -PEG languages; may be several on many tracks; [ ] FUT make multiple elements?-movieCoirnnents CDATA #REQUIRED -transmission commentary information-movieCreateDate CDATA #REQUIRED -PEG needs year creation date-movieRun Time CDATA #REQUIRED -PEG hh:mm-L5 movieRun Time-StatusCDATA #REQUIRED -estimated or actual-movieRunTimeMinutesCDATA #IMPLIED -RunTime minutes-movieRunTimeSecondsCDATA #IMPLIED -RunTime seconds-Run Code CDATA #IMPLIED -(ex. 2:02 HA)-Run Code Type CDATA #IMPLIED -can include codes indicating type of encoding etc.->.0ColorBW CDATA #IMPLIED -black & white or color-Caption ~ CDATA #IMPLIED -caption or description information-Keywords CDATA #IMPLIED -digital library query data for file retrieval-<!-Riglits Management Structure->

<!ELEMENT rightsMetadata (#PCDATA)>

<! ATTLIST rightsMetadata CID CDATA #REQUIRED-contract id-Amend No ~ CDATA #IMPLIED -contract amendment number-s Ravi ID CDATA #IMPLIED -rights availability window id-Start Date CDATA #IMPLIED -PEG start of availability-End Date CDATA #IMPLIED -PEG end of availability-No of Plays CDATA #IMPLIED -allowed number of plays per agreement-Usage Allowed CDATA #IMPLIED -extra restrictions (ex.
Rewind, pause, fast forward)-o Fee CDATA #IMPLIED -transaction fee-Authorized Zone CDATA #IMPLIED -geography or person-World Wide RightsCDATA #IMPLIED -yes or no-Music Effects CDATA #IMI'LIED-yes or no (ex. train crash, explosion)-Licensor CDATA #IMPLIED -copyright holder-Coypright YeaE~ CDATA #IMPLIED -year of copyright-<!-Transaction Metadata Structure->

<! ELEMENT transactionMetadata (#PCDATA)>

<! ATTLIST transactionMetadata o Trans ID CDATA #REQUIRED-transaction id-Trans Type CDATA #IMPLIED -type of transaction-Trans Date CDATA #IMPLIED -date of transaction-Trans User ID CDATA #IMPLIED -transaction author-;5 <!-Digital Photo Metadata Structure->

<!ELEMENT' Photo (photoMetadata, transactionMetadata)>

<! ELEMENT photoMetadata (#PCDATA)>

<! ATTLIST photoMetadata <!-Baseline Information - Required fields->

BID CDATA #REQUIRED-base ID-Form DigitalAssetCDATA #REQUIRED-photographs, graphics, location stills, or royalty fee-Orig Creation CDATA #REQUIRED-original creation date Date of digital photo asset (date field)-Resolution Type CDATA #REQUIRED

<!-Production Information (extracted from PRIME)->

Filin/Series/ProgramCDATA #IMPLIED -program title associated Title with photograph-0 Orig Broadcast CDATA #IMPLIED -original broadcast date Date of film or series (date field extracted from PRIME)-Orig Broadcast CDATA #IMPLIED -original broadcast season Season of program or series-Orig Release D CDATA #IMPLIED -original release date zte of program or series-Filin/Series CreationCDATA #IMPLIED -original creation date Date of film or series (date field)-Original CopyrightCDATA #IMPLIED -copyright year (date field-Year .5 Film/Series VersiomCDATA #IMPLIED -version control information-Filin/Series OriginCDATA #IMPLIED -origin of filin or series (e.g. HBO
Theatrical)-Description BlurbCDATA #IMPLIED -description information extracted from PRIME-Form Program CDATA #IMPLIED -program type (e.g. Movie)-Genre CDATA #IMPLIED -program style (e.g. Romance, Drama, Comedy)-0 Rating CDATA #IMPLIED -program rating (e.g. R, PG)-FilinSeries DirectorCDATA #IMPLIED -director of film or series-Film/Series WrirerCDATA #IIVVIPLIED-writer of filin or series-FilmlSeries-ProducerCDATA #IMPLIED -producer of film or series-Film/Series Ca,=~CDATA #IMPLIED -film or series cast and Talent talent information-FilinSeries ProductionCDATA #IMPLIED -production executive-Executive Filin/Series Prog~;~xnmingCDATA #IMPLIED -prograg executive-s Executive <!-Photograph Content Information->

Cast/Talent PhotoCDATA #IMPLIED -cast or talent that appear in photograph-Crew Name Photo CDATA #IMPLIED -crew that appear in photograph-Crew Position-PhotoCDATA #IMPLIED -crew position (e.g. Director, Producer, Writer)-L Origin Photo CDATA #IMPLIED -origin of photo (e.g.
o Warner Brothers, United Artist, Sports Illustrated)-Agency CDATA #IMPLIED -creative agency information-Art Director f:iot~rCDATA #IMPLIED -Art Director information-Photographer CDATA #IMPLIED -Photographer information-Requesting DepartmentCDATA #IMPLIED -division requesthig digital content-~5 Request Date CDATA #IMPLIED -date of request for digital asset (date field)-<!-Physical Photograph Information->

Orig Photo ID CDATA #IMPLIED -barcode information from photo label Orig Photo 1V'i~dimnCDATA #IMPLIED -(e.g. negative, print, transparency)-Orig Photo i..ocationCDATA #IMPLIED -location of photo in physical archive-. Orig Photo Ar CDATA #IMPLIED -original archive date o chu ve Date of photo (date field)-Orig Photo Arc:liiveCDATA #IMPLIED -original box number from Box physical file-Number <!-General Infon action->

DID CDATA #IMPLIED -digital asset id. link to Artesia UO!_ID_ ? Shoot Type CDATA #IMPLIED -type of photographic shoot (e.g. gallery, location still, acquisition)-Color CDATA #IMPLIED -color space of digital photo (e.g. black &
white color)-Description CDATA #IMPLIED -description of digital photograph subject matter-Comments CDATA #IMPLIED -general comments-Ready for Rights CDATA #IMPLIED -yes or no-Input Date CDATA #IMPLIED -date of ingestion into Digital Library system (date field)-Input By CDATA #IMPLIED -name of person responsible for uploading asset into Digital Library-Last Updated DateCDATA #IMPLIED -date of last update or modification (date field)-Last Updated By CDATA #IMPLIED -person responsible for last update or modification-<!-Rights Information->

Asset Copyright CDATA #IMPLIED -digital asset year of Year copyright-0 Asset Copyright CDATA #IMPLIED -digital asset copyright Holder holder-Restrictions LegalCDATA #IMPLIED -legal restrictions associated with digital asset-Restrictions PhotographerCDATA #IMPLIED -photographer restrictions associated with digital asset-Restrictions ExclusivesCDATA #IMPLIED -yes or no-Exclusives Held CDATA #IMPLIED -expiration of exclusive Until condition linked to digital asset (date field)-.5 Restrictions LicenseCDATA #IMPLIED -licensing limitations or restrictions Limitations associated to digital asset-Legal Contact CDATA #IMPLIED -legal contact for information regarding digital content usage-Availability Er~dCDATA #IMPLIED -date when digital asset Date is no longer available for usage (date field)-Rights Input Dat,CDATA #IMPLIED -date digital rights entered into Digital Library system (date field)-0 Rights Input By CDATA #IMPLIED -person entering digital rights info into Digital Library system-Rights Last UpdatedCDATA #IMPLIED -date rights information Date was last upgraded or modified (date field)-Rights Last UpdatedCDATA #IMPLIED -person responsible for By last update or modification of rights info-<!-Digital Photograph Information->

Filename CDATA #IMPLIED -name of digital file assigned by scanning technician (e.g. sopranos.jpg)-Format CDATA #IMPLIED -file format (e.g. JPEG, TIFF, PPT)-Physical LocationCDATA #IMPLIED -archival location of original transparency or print-Server Location CDATA #IMPLIED -location of digital asset storage system-Digitizing Date CDATA #IMPLIED -date digital asset was scanned (date field)-Creator CDATA #IMPLIED -name of person creating the digital file (e.g. scanning technician)-L Filesize CDATA #IMPLIED -size of digital file 0 (KB/MB)-Mode CDATA #1MPLIED -color space (e.g. RGB, CMYK, Grayscale)-Height Inches CDATA #IMPLIED -height of digital image (inches)-Width Inches CDATA #IMPLIED -width of digital image (inches) Height Pixels CDATA #IMPLIED -height of digital image (pixels)-L5 Width (Pixesl0 CDATA #IMPLTED -width of digital image (pixels)-Resolution DPI CDATA #IMPLIED -digital image resolution (dots per inch) <!-Digital Audio Metadata Structure->

<!ELEMENT Audio (audioMetadata, transactionMetadata)>

? <!ELEMENT' audioMetadata 0 (#PCDATA)>

<! ATTLIST audioMetadata AID CDATA #REQUIRED -asset id-PID CDATA #REQUIRED -product ID-CID CDATA #REQUIRED -contract id-Title CDATA #IMPLIED -audio title-Music CDATA #IMPLIED -yes or no-Stock CDATA #IMPLIED -yes or no-Stock Library CDATA #IMPLIED -music library information-Stock Sub LibraryCDATA #IMPLIED -audio library tracking information-Stock CD Nbr CDATA #IMPLIED -CD ID number-Stock CD Title CDATA #IMPLIED -CD title information-Stock Track TitleCDATA #IMPLIED -audio track information-Stock Duration CDATA #IMPLIED -length of media section-.0 Stock Composer CDATA #IMPLIED -music composer information-Stock Publisher CDATA #IMPLIED -publishing party (ex.
Warner, etc.)-Stock Society CDATA #IMPLIED -(ex. ASCAP, etc.)-Original CDATA #IMPLIED -yes or no-Original Code CDATA #IMPLIED -x-.5 Original Session CDATA #IMPLIED -date of recording-Date Original ComposerCDATA #IMPLIED -music composer information-Original Publis'serCDATA #IMPLIED -party of publisher (ex.
Warner, etc.)-Original Society CDATA #IMPLIED -x-Rights Issues CDATA #IIVVIPLIED-contract information ~ (ex. Rights, Permissions)-0 Contract Lir:enseCDATA #IMPLIED -yes or no-Internet CDATA #IMPLIED -yes or no-International CDATA #IMPLIED -yes or no-Library Contact CDATA #IMI'LIED -contact person-5 <!-Long Form Movie Metadata Structure->

<!ELEMENT Movie (movie FormatMetadata, TransactionMetadata)>

<!ELEMENT movie FormatMetadata (#PCDATA)>

<! ATTLIST movie FormatMetadata SAP CDATA #IMI'LIED -yes or no; secondary audio program (ex.
Spanisli)-P Version Fomnat CDATA #IMPLIED -refers to the format information (PRIME
Table)-Transmission FormatCDATA #REQUIRED-digital format (ex. MPEG, Quicklime, etc.)-Storage'Capacity CDATA #IMPLIED -storage requirements for digital transmission data-Unit of Measure CDATA #IMPLIED -(ex. Megabytes MB, Gigabytes of GB, Capacity Terabytes TB)-Compression Sta CDATA #REQUIRED-bit rate information-lus , ESP CDATA #REQUIRED-yes or no-Closed Caption CDATA #IMPLIED -yes or no-Sound CDATA #IMPLIED -(ex. Stereo, Mono, Dolby, Dolby Digital, Dolby)-LO >

Example 2 below shows a sample XML document generated as part of a photographic asset search.
Example 2 (filename;: sasnple.xssz~
s5 <?xml vf~rsion='1.0' standalone='no'?>
<D~
<Asset>
<Asset~netadata Pm="200000" AssetTitle="Chaos Factor"
Comments="Soldiers talking to man">
2 0 </As ~etmetadata>
<Photo>
<Photornetadata Resolution="72 dpi"
Talent= "Unl~nown">
</PhotomFtadata>
2 5 </PhOtO>
<Content= ~chaos_l t.jpg </Con~cent:>
</Asset>
<Asset>
<Assetmrtadata PIV=" 141896" AssetTitle="lf walls could talk 2" Comments="An HBO Films trilogy examining the lesbian experience in America in three different decades">
</Assetinetadata>
<Photct>
<Photometadata Resolution="72 dpi" Talent="Ellen Degeneres">
s o </Photometadata>
</Photo>
< Content>walls 2 t .jpg </Content>
</Asset>
Z5 <Asset>
<Assetme~adata PID="300000" AssetTitle="Sex and the city"
Conunents="Close up portrait of Sarah JessicaParker">
</Assetmetadata>
<Photo>
a o <Photometadata Resolution="72 dpi" Talent=Sarah and cast">
</Pho tometadata>
</Pboto>
<Content>sex city 2 t.jpg </Conteut>
z s </Asset>
<Asset>
<Assetmetadata P~=" 141897" AssetTitle="If walls could talk 2" Comments=" An HBO Films trilogy examining the lesbian ea~perience in America in three different decades">
s o </Assetrnetadata >
<Photo>
<Photometadata Resolution="72 dpi" Talent "Ellen Degeneres">
</Photumetadata>
</Photo>
35 < Content>walls_ 5 t.jpg </Content>

</A55E t>
</DAL>
XSL operates on XML search output. The output from XSL may be either HTML or XML both with CSS. Known software engines, such as, for example, a software engine known as XT developed by James Clark (see http://jclark.com/xml/xt.html for more details), can be used ~'o convert XML into HTML. A sample command for doing such is: C:>XT sample.xml css.xsl output2.xml. This to command generates an XML document named output2.xml, which can be displayed using standard browser software.
Example 3a shows a sample XSL script. Example 3b sho~~as a sample HTML document generated by XSL on the XML
search. output of Example 2. Example 3c shows a sample XML
document. with CSS also generated by XSL on the XML search outpu of Example 2.
Example 3a <?xml version=" 1.0"?>
<xslatylesheet version=" 1.0"
2 o xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xslaerr~plate match="/">
<xsl: apply-templates/>
</xsl aemplate>
</xslaemplate match="lDAL/Asset">
<TABLE WIDTH="100%" BORDER--"1"><TR><TD HEIGHT="288">
<B>PII>:<B><xsl:value-of select-Assetmetadata/@PID/><BR/>
<B>Asset Title: <B><xsl:value-of select="Assetmedatada/@AssetTitle"/><BR/>
<B>Corr~ ments:<B><xsl:value-of 3 o select="Assetinetadata/@Comments"/><BR/>
<B>Resolution:<B><xsl:value-of select="Photo/Photometadata/@Resolution"/><BR/>

<B>Talent:<B><xsl:value-of select="P LZOto/Photometadata/@Talent"/><BR/>
</TD><TD WIDTH="288" HEIGHT="288">
<xsl:apply-templates />
</TD></TR>
</TABLE> , </xsl aemplate>
<xsl template match="/DAL/Asset/Content">
<p><A
to href--"{~~oncat('full ',ancestor::Asset/Content)~"><img src=" {ancestor::Asset/Content~" border="0"/>
</A></P>
</xsl aemplate>
</xsl: stylPsheet>
Example 3b <HTML>
<TAB~,E WIDTH=" 100%" BORDER--" 1 "><TR>
<TD HEIGHT="288">
<B> Pm: <B>200000<BR/>
a o <B>Asset Title:<B>Chaos Factor<BR/>
<B>Cornments:<B>Soldiers talking to man<BR/>
<B>Resolution:</B> 72 dpi<BR/>
<B>Talent:<B>TJnknown<BR/>
</TD><r~'D WIDTH="288" HEIGHT="288">
2 s <p><A hre~"full chaos 1 t.jpg"><img src="chaos_1 t.jpg" border="0"/></A></P></TD>
</TR></TABLE>
<TABLF WIDTH="100%" BORDER="1"><TR>
<TD HEIGHT="288">
3 0 <B>PID: <B>141896<BR/>
<B>~~sset Title:<B>lf walls could talk 2<BR/>
<B>Comments:</B>Ail HBO Films trilogy examining the lesbian experience in Americin three different decades<BR/>
<B>Resolution:</B> 72 dpi<BR/>

<B>Talent:<B>Ellen Degeneres<BR/></TD>
<TD W1DTH="288" HEIGHT="288">
<P><A hre~"full walls 2 t.jpg"><img src="walls 2 t.jpg" border="0"/> </A></p></TD>
</TR></TABLE>
<TABLE WIDTH--" 100%" BORDER=" 1"><TR>
<TD HEIGHT="288"><B>pm: <B>300000<BR/>
<B>Asset Title:<B>Sex and the city<BR/>
<B>Cnmments:<B>Close up portrait of Sarah Jessica Parker<BR/>
to <B>Resc~lution:</B> 72 dpi<BR/>
<B>Talent:<B>Sarah and cast<BR/></TD>
<TD WIDTH="288" HEIGHT="288">
<P><A hre~"full sex city_2 t jpg"><img src="sex city 2 t.jpg" border="0" /></ A></P>
</TD></TR></TABLE>
<TABLE WIDTH=" 100%" BORDER=" 1 "><TR>
<TD HEICTHT="288">
<B>PID: <B>141896<BR/>
<B>Asset Title:<B>If walls could talk 2<BR/>
a o <B>ConFments:</B>An HBO Films trilogy examining the lesbian experience in America in three different decades<BR/>
<B>Resolution:<B> 72 dpi<BR/>
<B>Talent:<B>Ellen Degeneres<BR/></TD>
<TD ~~VIDTH="288" HEIGHT="288">
a5 <P><~A href--"full walls 5 t.jpg">
< imgsrc="walls 5 t.jpg" border="0"/></ A></P> </TD>
</TR></TABLE>
</HTML>
Example 3c 3 0 (filename: css.xm~
<?xml version=1.0"?>
<xslarYlesheet version="1.0"
xmlns:xsl="http://www .w3.org/1999/xsl/transform">
<xslae~~uplate match="/">

<xsl: processing-instruction name="xml-stylesheet">type="text/css"
hre~"#photos"
</xsl v processing-instruction>
<xsl:apply-templates select "DAL"/>
</xsl aemplate>
<xslaemplate match=".">
<xsl:copy><xsl:value-of select="."/></xsl:copy>
</xsl aemplate>
<xslaemplate match="DAL ">
<style rd=photos">
so Asset display: blocl~; position:relative;width:100%;height:225px;border:inset3px gray;) Assetmetadata f display:inline;font-size:l4pt;) Photo display:inline;font-size:l2pt;) Photometadata ~display:inline;font-size: l2pt;) ' Content {widtb.'72 px; height:72px;position:relative;display:block;float:left;) <xsl:for-each select="//Asset">Content[photo<xsl:value-of select "@PID"/> ]
~bacliground-image:url(<xsl:value-of select="Content"/>);}
</xsl: fore each>
a o </style>
<xsl:apply-templates select "Asset"/>
</xslaemplate>
<xslaemplate match="/DAL/Asset/Content">
<Content id =" ~concat(Photo', a 5 sibling:: ='rssetmetadata/@PID)~
hre~" ~sibling::Asset/Content} "/>
</xslaemplate>
<xslaemplate match="/DAL/Asset">
<TAB.~,E WIDTH=" 100%" BORDER=" 1 "><TR><TD HEIGHT="288">
3 0 <B>F'ID: </B><xsl:value-of select=Assetmetadata/@PID/><BR/>
<B>Asset Title:</B>
<xsl:val ~.ie-of select "Assetmetadata/@AssetTitle" /><BR/>
<B>Comments:</B><xsl:value-of select="Assetmetadata/@Comments" /><BR/>
35 <B>Resoiution:</B><xsl:value-of select "Photo/Photometadata/@Resolution" />< BR/>

<B>Ta'tent:</B><xsl:value-of select="Photo/Photometadatal@Talent"/>< BR/>
</TD>
<TD W1DTH="288" HEIGHT="288">
<xsl:apply-templates />
</TD>
</TR=~</TABLE>
</xslae~nplate>
<xslar~mplate match="/DAL Asset/Content">
<p>~.A
href-"{concat('photo',sibling::asset/content ))">
<img src=" {ancestor::Asset/Content~" border="0"/>
</A></P>
</xslaemplate>
</xslatylesheet>
Thus it is seen that XML data definitions for digital assets are provided that can be used as a standardized dictionary for application and platform indelaE:ndent exchange and repurposing of those assets. One 2o skilled in the art will appreciate that the present inve:~ztion can be practiced by other than the described embodiments, which are presented for purposes of illustration and not of limitation, and the present invent: ion is limited only by the claims which follow.

Claims (30)

WE CLAIM:

1. A document type definition (DTD) comprising metadata for at least two types of digital assets selected from the group consisting of photographs, audio recordings, video recordings, movies, graphics, and text documents.

2. The document type definition of claim 1 wherein said document type definition is encoded in extensible markup language (XML).

3. The document type definition of claim 1 comprising metadata for photographs and audio recordings.

4. The document type definition of claim 1 comprising metadata for photographs and video recordings.

5. The document type definition of claim 1 comprising metadata for photographs, audio recordings, and video recordings.

6. The document type definition of claim 1 comprising metadata for photographs, audio recordings, and movies.

7. The document type definition of claim 1 comprising metadata for photographs and further comprising a plurality of metadata attributes for said photograph metadata, said photograph metadata attributes comprising:
a definition for black/white;
a definition for color; and a definition for caption.

8. The document type definition of claim 1 comprising metadata for audio recordings and further comprising a plurality of metadata attributes for said audio metadata, said audio metadata attributes comprising:

a definition for music;
a definition for track title; and a definition for duration.

9. The document type definition of claim 1 comprising metadata for audio and further comprising a plurality of metadata attributes for said audio metadata, said audio metadata attributes comprising:
a definition for compact disc (CD) number;
and a definition for CD title.

10. The document type definition of claim 1 comprising metadata for movies and further comprising a plurality of metadata attributes for said movie metadata, said movie metadata attributes comprising:
a definition for title; and a definition for version.

11. The document type definition of claim 1 comprising metadata for movies and further comprising a plurality of metadata attributes for said movie metadata, said movie metadata attributes comprising:
a definition for rating;
a definition for minutes; and a definition for release date.

12. The document type definition of claim 1 comprising metadata for movies and further comprising a plurality of metadata attributes for said movie metadata, said movie metadata attributes comprising:
a definition for run time;
a definition for color; and a definition for synopsis.

13. The document type definition of claim 1 comprising metadata for movies and further comprising a plurality of metadata attributes for said movie metadata, said movie metadata attributes comprising:
a definition for director; and a definition for cast.

14. A document type definition (DTD) comprising metadata for at least three types of digital assets selected from the group consisting of photographs, audio recordings, video recordings, movies, graphics, and text documents.

15. A document type definition (DTD) comprising metadata for photographic digital assets, audio digital asset, promo digital assets, and voiceover digital assets.

16. A document type definition (DTD) comprising:
digital content selected from the group consisting of digitally encoded asset data, a link to a file containing asset data, and a reference to a location where asset data is digitally stored; and metadata for at least three types of digital assets selected from the group consisting of photographs, audio recordings, video recordings, movies, graphics, promos, voiceovers, and text documents.

17. A database comprising:
a first record having a plurality of fields identifying a photograph;
a second record having a plurality of fields identifying a motion picture movie; and a third record having a plurality of fields identifying a musical recording.

18. The database of claim 17 wherein said first record comprises a field identifying the photographer.

19. The database of claim 17 wherein said second record comprises a field identifying the title of said movie.

20. The database of claim 17 wherein said third record comprises a field identifying the composer of said musical recording.

21. A database comprising:
a first record having a plurality of fields identifying a photograph;
a second record having a plurality of fields identifying a movie;
a third record having a plurality of fields identifying an audio recording; and a fourth record having a plurality of fields identifying a voiceover.

22. A database comprising:
a first record having a plurality of fields identifying a photograph;
a second record having a plurality of fields identifying a movie;
a third record having a plurality of fields identifying an audio recording;
a fourth record having a plurality of fields identifying a voiceover; and a fifth record having a plurality of fields identifying a promo.

23. A digital asset library comprising:
a database comprising a plurality of records, one said record identifying a photograph, a second said record identifying a video recording, and a third said record identifying an audio recording; and a document type definition (DTD) comprising definitions for photographs, video recordings, and audio recordings, said DTD corresponding to said database records.

24. A digital asset library comprising:
a database comprising a plurality of records, one said record identifying a photograph, a second said record identifying a video recording, and a third said record identifying an audio recording;
a document type definition (DTD) comprising definitions for photographs, video recordings, and audio recordings, said DTD corresponding to said database records: and digital content comprising a photograph, a video recording, and an audio recording.

25. A digital asset library stored in a computer system, said library comprising:
a database comprising a plurality of records, said records identifying at least two types of digital assets selected from the group consisting of still images, audio recordings, video recordings, movies, graphics, voice-overs, promos, and text documents;
a document type definition (DTD) comprising definitions for said at least two types of digital assets, said DTD corresponding to said database records; and digital content of said at least two types of digital assets.

26. A method of retrieving digital assets from a single digital asset library, said digital assets comprising at least three different types of digital assets selected from the group consisting of still images, video recordings, audio recordings, graphics, promos, voiceovers, and text, said method comprising:
receiving a request for at least one digital asset, said request comprising criteria to which said at least one digital asset is to conform;
accessing a document type definition (DTD) of said digital asset library, said DTD defining data elements for at least three different types of digital assets selected from the group consisting of still images, video recordings, audio recordings, graphics, promos, voiceovers, and text;
searching a database of said digital asset library for said at least one digital asset, said database comprising a plurality of records identifying digital assets of at least three different types selected from the group consisting of still images, video recordings, audio recordings, graphics, promos, voiceovers, and text; and returning a list of at least one digital asset conforming to said criteria.

27. The method of claim 26 wherein said criteria comprises a keyword.

28. The method of claim 26 wherein said criteria comprises a product ID and a version ID.

29. The method of claim 26 wherein said returning a list comprises returning a list of at least three digital assets each conforming to said criteria, each said asset being of a different asset type selected from the group consisting of still images, video recordings, audio recordings, graphics, promos, voiceovers, and text.

30. The method of claim 26 further comprising:
receiving a request for a copy of said at least one digital asset conforming to said criteria;

accessing said at least one digital asset stored in a computer memory device of said digital asset library; and creating a copy of said at least one digital asset in compliance with said request for a copy.