WO2002048920A9

WO2002048920A9 - Digital asset data type definitions

Info

Publication number: WO2002048920A9
Application number: PCT/US2001/047798
Authority: WO
Inventors: Bruce E Probst; Carl Hixson; Anne Moroney
Original assignee: Time Warner Entertainm Co Lp
Priority date: 2000-12-12
Filing date: 2001-12-12
Publication date: 2003-04-17
Also published as: US8065303B2; EP1360611A2; CA2431341A1; WO2002048920A3; US20090248646A1; US20070208720A1; US20060015489A1; US20030140034A1; AU2002230745A1; WO2002048920A2; US7739307B2; US7209917B2; US7558781B2

Abstract

Data definitions for digital assets, such as, for example, audio, video, photographs, graphics, and electronic documents, are provided that allow these 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 definitions 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, video, and text documents, to be easily and economically stored, retrieved, and tracked.

Data definitions may be written using XML (extensible markup language) . XML is a condensed form of SGML (standard generalized markup language) , which is an information management standard that provides documents that retain formatting, indexing, and linked information -- independent of application and platform. XML and SGML can be 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 typically include content and metadata. Content may be, for example, still photographs, audio recordings, video recordings, combined audio/video recordings, combined audio/still photograph recordings, graphics, etc. Metadata is "information 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 . 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 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 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 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 applications are limited. For example, databases are commonly structured to store only one type of digital asset, such as, for 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, 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. 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 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 .

Summary of the Invention

It is an object of this invention to provide a standardized dictionary of data definitions for disparate types of digital assets.

It is also an object of this invention to provide 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 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 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 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 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 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; 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; 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.

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 or video promotional announcement) , tapes, soundtracks, text, video frames (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 computer as the database, in the database, on a computer 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 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 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 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 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 directed along path 114 to User Home Screen 115 unless the 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. 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. Screen 107 preferably allows 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 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. 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 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 database. However, the subset may be defined as the most recently released assets, most recently produced assets, or any other 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 providing 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 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 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 more 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 may be automatically directed to screen 123 if a small number of asset definitions are the only items the user wishes to view. For instance, if a user performs a complex search and 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 of the summary data directly related to one or more items selected manually or automatically by the user. Preferably, 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, 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 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 120 to allow a user to view search results from a 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 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 devices 209-211 or non-secure recording or printing device 212, as appropriate, via non-secured data transmission line 200.

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 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-l, 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, hard disk 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 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^®, 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. 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 bots or may include regular HTML if a still or active 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 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 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 that apply formatting to complex XML data for presentation in HTML and other formats. XSL can map a single 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 necessary depending on the database) , application 404 sends query 405 to database 305. Database 305 processes query 405 and returns search results 406 to application 404. Application 404 then processes results 406 to create one or more XML files. These XML files are sent by application 404 as data 407 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 by the user.

FIG. 5 shows an example of a display that can be used as 7^.dvanced Search Screen 107. Illustrative display 501 includes interactive features 502, 503, 504, and 505. Display 5θi may alternatively include more or less interactive features as appropriate for a given implementation of the invention. Interactive feature 502, entitled "PLEASE ENTER KEYWORDS TO SEARCH, " accepts user entries of keywords or phrases to be used by XML project applications 303 when forming demand 304. For example, "Oscar belt" may be entered via interactive feature 502 by a user searching for a picture that has metadata containing the descriptj.on, "Oscar Delahoya wearing a championship belt." Interactive feature 503, entitled "PLEASE SELECT ASSET CATEGORY," accepts user entries for the type of asset to retrieve. For example, possible asset types are photos, audio, video, text, any cor/oination 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 demand 304) . Interactive features 505, entitled "DTD," "XML," "XSL," and "XSL SS," allow a user to select a source code format in which to view data instead of viewing a composed video screen or hearing a composed audio output. FIG. 6 shows an example of a display that can be used as Search Results Screen 120. In this example, illustr.cive display 601 indicates at 602 that 4 photo assets, l 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. Alternatively, 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 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 "ORDER CHECKED," is interactive and accepts indications that a user has finished selecting assets and 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 a separate file or document that contains formal definitions of all the 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 contain,?. DTD 700 includes asset element 701, which defines the type of data to be stored for each digital asset. DTD 700 may 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 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 identifier (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 definitional elements for classifying five asset types:

Table 1

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 teclmologies include but not limited to XML, XSL, XSLT, XPATH, DTD Schema->

L0

L5

20

L0

L5

0

>5

L0

L5

20

Example 2 below shows a sample XML document generated as part of a photographic asset search.

Example 2

(filename: sample.xml) is <?xml vorsion- 1.0' standalone='no'?>

<DAL>

<Asset>

<AssetmetadataPID="200000" AssetTitle="Chaos Factor"

Comments- 'Soldiers talking to man"> 2 o </Asr,etmetadata>

<Photo>

<Photometadata Resolution="72 dpi"

Talent-"Unl nown">

</Photometadata> 25 </Photo>

<Content- chaos_l_t.jpg </Conιent>

</Asset>

<Asset>

</Assetmetadata>

<Photo>

</Photo>

< Content>walls_2__t .jpg

</Content>

</Asset> s <Asset>

<AssetmetadataPID="300000" AssetTitle="Sex and the city"

Comments- 'Close up portrait of Sarah JessicaParker">

</Assetmetadata>

</Pho tometadata> </Photo>

<Photo>

<Photometadata Resolution- ' 72 dpi" Talent- 'Ellen Degeneres"> </Photometadata> </Photo> 5 < Content>walls_ 5_t.jpg </Content> </Asset> </DAL>

XSL operates on XML search output. The output from XSL may be either HTML or XML both with CSS . Known 5 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 to convert XML into HTML. A sample command for doing such is: C:>XT sample. xml css.xsl output2.xml. This 0 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 shows a sample HTML document generated by XSL on the XML search, output of Example 2. Example 3c shows a sample XML 5 document, with CSS also generated by XSL on the XML search output of Example 2.

Example 3a

<?xml version="1.0"?> <xsl: stylesheet version- ' 1.0" o xmlns:xsl="http://www.w3.org/1999/XSL/Transform">

<xsl:ten φlate match="/"> <xsl : apply-templates/> </xsl:template>

</xsl:template match="/DAL/Asset"> 5 <TABLE WIDTH="100%" BORDER="l"><TR><TD HEIGHT="288"> PID :<xsl:value-of select- Assetmetadata/@PID/> Asset Title: <xsl:value-of select="Assetmedatada/@AssetTitle"/> Corrιαιents:<xsl:value-of o select="Assetmetadata/@Comments"/>

Resolution:<xsl:value-of select='^,Photo/Photometadata/@Resolution"/> Talent:<xsl:value-of select="Photo/Photometadata/@Talent"/> </TD><TD WTDTH="288" HEIGHT="288"> <xsl:aρply-templates /> 5 </TD></TR> </TABLE> </xsl:template>

</A>

</xsl:template>

</xsl:stylesheet>

5 Example 3b

<HTML>

PID: 200000 o Asset Title:Chaos Factor

Comments:Soldiers talking to man Resolution: 72 dpi Taleni:Unknown </TD><TD WIDTH="288" HEIGHT="288"> 5 <A href="full_chaos_l_t.jpg"><img src="chaos_l_t.jpg" border="0"/></Ax/Px/TD>

</TRx/TABLE>

<TD HEIGHT="288"> 0 PID: 141896

Λ.sset Title:lf walls could talk 2

Comments:Aιι HBO Films trilogy examining the lesbian experience in

America in three different decades

Resolution: 72 dpi Talent:Ellen Degeneres<BR/x/TD>

<TD HEIGHT="288"xB>PID: 300000

Asset Title:Sex and the city

Cornments:Close up portrait of Sarah Jessica Parker Resolution: 72 dpi

Talent:Sarah and cast<BR/x/TD>

<TD WJX>TH="288" HEIGHT="288">

PID: 141896

Asset Title:If walls could talk 2 Con^»ments:An HBO Films trilogy examining the lesbian experience in America in three different decades

Resolution: 72 dpi

Talent:EUen Degeneres<BR/x/TD>

< imgsrc="walls_5_t.jpg" border="0"/></ A> </TD>

</TRx/TABLE>

</HTML>

Example 3c

(filename: css.xmt)

<?xml version=1.0"?> <xsl:stylesheet version- ' 1.0" xmlns;xsl="http://www .w3.org/1999/xsl/transform"> <xsl:te'.uplate match="/"> <xsl: processing-instruction name="xml-stylesheet">type="text/css" href="#photos"

</xsl ^■ piOcessing-instruction>

<xsl:apply-templates select="DAL"/>

</xsl:template> 5 <xsl:template match— '. ">

</xsl:template>

<xsl:template match="DAL ">

{display: block; position:relative;width:100%;height:225px;border:inset3px gray;}

Assetmetadata {display:inline;font-size: 14pt;}

Photo {display:inline;font-size: 12pt;}

Photometadata {display:inline;font-size: 12pt;} 5 Content

{width. 72 px; height:72px;position:relative;display:block;float:left;}

<xsl:for-each select="//Asset">Content[photo<xsl:value-of select="@PID"/> ]

{bac ground-image :url(<xsl : value-of select— ' Content "/>); }

</xsl:for-each> o </style>

<xsl:apply-templates select="Asset"/>

</xsl:template>

<xsl:template match="/DAL/Asset/Content">

</xsl:template>

<xsl:template match="/DAL/Asset">

Asset Title:

<xsl: val αe-of select-" Assetmetadata/@AssetTitle" /> Cojnments:<xsl:value-of select-" Assetmetadata/@Comments" /> 5 Reso⁾ αtion:<xsl:value-of select="Photo/Photometadata/@Resolution" /> Ta^'ient:<xsl : value-of select="Photo/Photometadatal@Talent"/x BR/>

</TD>

</TD>

</TRx/TABLE>

</xsl:template>

<xsl:tcmplate match="/DAL Asset/Content"> <PxA href=="{concat('photo',sibling::asset/content )}">

</A>

</xsl:template> </xsl:stylesheet>

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 independent exchange and repurposing of those assets. One skilled in the art will appreciate that the present invention can be practiced by other than the described embodiments, which are presented for purposes of illustration and not of limitation, and the present invenlion is limited only by the claims which follow.

Claims

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 viovie 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 iovie 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 assets, 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 compr:', sing 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.