WO2001097070A1 - Procede et systeme pour la gestion de liaison - Google Patents

Procede et systeme pour la gestion de liaison Download PDF

Info

Publication number
WO2001097070A1
WO2001097070A1 PCT/US2001/018784 US0118784W WO0197070A1 WO 2001097070 A1 WO2001097070 A1 WO 2001097070A1 US 0118784 W US0118784 W US 0118784W WO 0197070 A1 WO0197070 A1 WO 0197070A1
Authority
WO
WIPO (PCT)
Prior art keywords
link
destination
identifier
source
relation
Prior art date
Application number
PCT/US2001/018784
Other languages
English (en)
Inventor
Dipto Chakravarty
Lynn Mcgonigle
Jack Tam
Edward Jenkins
Maryam Norouzi
Roger Medlin
Ben Dale Harper
Gary Bollinger
Malick Fall
Original Assignee
Artesia Technologies, Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Artesia Technologies, Inc. filed Critical Artesia Technologies, Inc.
Priority to AU2001268314A priority Critical patent/AU2001268314A1/en
Publication of WO2001097070A1 publication Critical patent/WO2001097070A1/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/70—Information retrieval; Database structures therefor; File system structures therefor of video data
    • G06F16/74—Browsing; Visualisation therefor
    • G06F16/748—Hypervideo

Definitions

  • the present invention consists of a method and system for managing links between digital assets. More particularly, it concerns a method and system for managing the relationships, that is, the links themselves, between digital assets of any type. 2. DESCRIPTION OF THE RELATED ART
  • digital assets are intended to include assets of any type which have been digitized. Such assets could be, for example, logos, trademarks, marketing materials, press releases, newspapers, publications of all types, print advertisements, internet advertising, broadcast advertising, and so forth. Digital assets are therefore anything which can be digitized and which has value to a company in a stored electronic form.
  • Vignette Corp. offers a product under the trademark IRM. This product manages relationships between web pages on a web site. Unfortunately, this product does not take into consideration objects of undefined depth. Moreover, it is geared to a particular application.
  • a method and system for digital asset link management Electronic storage is accessed, the electronic storage containing at least one link relation, wherein each link relation includes a source identifier, a destination identifier, and a link type. It is determined, from the source identifier and destination identifier, a corresponding source digital asset and a corresponding destination digital asset. The process of determining includes determining the relation type between the source digital asset and destination digital asset.
  • the source digital assets included in at least a portion of the link relations are destination digital assets in another portion of the link relations.
  • the source identifier and destination identifier each further has a metadata type.
  • FIG. 1 is a block diagram of the system for link management.
  • FIG. 2 illustrates a table of UOIs (units of information).
  • FIG. 3 is an exemplary table of link types.
  • FIG. 4 is an exemplary table of UOI links.
  • FIG. 5 is an exemplary Metadata lookup table.
  • FIG. 6 is an example state diagram illustrating a link life cycle.
  • FIG. 7 is a block diagram illustrating the tool for visualization of a digital asset using the present system.
  • the present invention seeks to solve the problems outlined above by tracking the link relationship between digital assets, and giving the source and destination for each link much less relevance.
  • the link asset management system includes information on UOIs 101, information on link types 103, and storage relating to the UOI links 105.
  • an ancillary Metadata lookup 107 is included.
  • a "UOI” is a unit of information. It refers to an atomic unit of a digital asset, i.e., the smallest unit of information that has value, for example, a logo, text, etc.
  • the UOIs 101 contains unique identifiers corresponding to digital assets, preferably stored as a table.
  • the link types 103 is preferably stored as a table, in order to correlate link types to a description relation between assets. Examples of link types include "brother of ", "container of ".
  • the UOI links 105 contain link relations, i.e., corresponding sources, targets and links (or link types) between each corresponding source and target digital asset.
  • link means a relation between two assets.
  • a “link type” is intended to accommodate industry specific vocabulary; examples include: “a parent of ", "a container of ", “attorney of “.
  • a “relationship” is an independent type of link, URL/URN or a hot spot. Thus each "link type” is a user defined relationship.
  • the Metadata (“MD”) lookup 107 is preferably provided, although it is not necessary. Every UOI in the UOIs 101 references Metadata assets (for example, file type, file format, other attributes, etc. about the data).
  • the MD lookup 107 contains, by Metadata type, the expected attributes of each type of Metadata. These attributes include, for example, that a TIF bit file type has specific Metadata associated therewith.
  • a source value 109 and a destination value 111 are provided from the UOIs 101 to the UOI links 105.
  • the link type 113 is obtained from the link types file 103 and provided to the UOI links 105.
  • the source type and destination type 115, 117 are obtained from the Metadata lookup table 107.
  • the UOIs include information for each UOI on UOI identification
  • the UOIs also preferably includes version 205 and an indication of whether this is the latest version 207.
  • the UOI identification is a unique identifier corresponding to each unit of information.
  • the logical UOI identification 203 is a logical identifier corresponding to the unit of information.
  • UOIb is a destination of UOIc and a source of UOIa.
  • UOIa is determined to have the logical UOI identification of "Diagram”, UOIb identification the logical
  • UOI of "Chapter 1 ", and UOIc identification has a logical UOI identification of "Book”.
  • the link between UOIa and UOIb is "TYPEa”, i.e., "is container of”.
  • "Book” is he container of "Chapter
  • the table minimally contains each unique UOI identification and each corresponding logical UOI identification, in order that the relatively short UOI identification can be stored and the logical UOI identification can be much longer.
  • UOIs 101 Also included in the UOIs 101, preferably, is an indication of the version 205 of each UOI. In this manner, multiple versions can be simultaneously stored. Also, preferably there is an indication of whether that version is in fact the latest version 207. Thus, by searching the UOIs table by UOI identification, one can determine the corresponding logical UOI identification.
  • the link types includes each of the link type codes 301, and the corresponding link type names 303.
  • the link types 103 is in the form of a table.
  • the link type code can be any appropriate code.
  • the link type name preferably takes the format of "is of”.
  • the link type names are preferably determined by the user.
  • link types 103 By reference to the link types 103, one can determine the type of link between the two values.
  • Optionally included information with each of the link types is an indicator of whether the latest version is to be used, a reciprocal link type, any particular behavior, a status, and a description.
  • the version connotes revisions of link participants.
  • the reciprocal link type can best be understood by example. If, for example, the link type is "a parent of", the reciprocal link type is "a child of.”
  • the behavior is the semantic meaning associated with the specific link types.
  • the status is a boolean description such as active versus inactive. The description describes the relationship between the UOI-s.
  • FIG. 4 illustrates the UOI links 105.
  • the UOI links includes a source UOI 401, a destination
  • the source UOI and the destination UOI are stored as UOI identifications, and the link types are stored as link type codes, in a table.
  • the table supports multiple source UOIs corresponding to a single destination UOI and conversely multiple destination UOIs corresponding to a single source 205.
  • each link is stored as a source identification and a destination identification with the link type.
  • the schema is therefore generic in that it will support linking of two digital assets.
  • Optional information stored in the UOIs also includes source type, destination type, sequence number, a flag to indicate use of the latest version, status, and status date.
  • An application program can access the UOI links based on either a source UOI or a destination
  • the application's program may obtain all of the corresponding destinations (or sources) and determine the corresponding link types. Next, by reference to the UOIs the source and destination logical UOI identifications are obtained. Also, by accessing the link types, the link type name is determined. Given a particular source or destination, the application table can then traverse to each next source or destination UOI and/or logical UOI, and can indicate to the user the link type name.
  • UOIb is a destination of UOIc and a source of UOIa.
  • UOIa is determined to have the logical UOI identification of "body .htm”
  • UOIb identification the logical UOI of "charger.bmp”
  • UOIc identification has a logical UOI identification of "main.htm”.
  • the link between UOIa and UOIb is "TYPEa", i.e., "is container of”.
  • body.htm is the container of "charger.bmp".
  • Figure 5 illustrates the Metadata lookup.
  • the Metadata lookup 107 includes a Metadata type
  • Metadata attributes 503 for each Metadata type.
  • Each Metadata type may have associated with it certain attributes. The attributes would be dependent upon the type of the
  • Metadata For example, if the Metadata type is a code for a GIF file, the attributes would be specific to GIF files. Typically, the attributes would include the name of the Metadata type (such as a file type), and category. Category is a taxonomy or classification hierarchy.
  • the Metadata lookup is advantageously implemented as a table and is optionally included. It enhances the efficiency of the system to be able to reference a specific Metadata type and rapidly determine the expected attributes. Nevertheless, although the Metadata lookup table is preferred, it is ancillary and may be omitted.
  • Figure 6 is a state table illustrating a life cycle of a link. At step 601, a link is created.
  • the link may be traversed 603 by the application program. At least two types of traverse may be provided: searching 613 and browsing 611.
  • the search traverse 613 permits a user to search for a specific source, destination or link type.
  • the browse function 611 permits a user, whose application is presently located at a particular link, source or destination to traverse the link forward or backward to linked sources and destinations.
  • a link may also be updated 605.
  • a link may be deleted 607.
  • deletion does not permanently remove the link.
  • a link may be undeleted at 609.
  • purge 615 the link. Providing a separate process for delete and purge permits deletions to occur and then be undeleted if in fact the deletions were not desired.
  • the link type should be defined by name, for example "is parent of", or
  • link creation is an appropriate time to encourage the user to define the reciprocal relation, for example, "is child of” is the reciprocal relation to "is a parent of”. The user could add additional link types to the ongoing database.
  • link types are created, a source and destination asset can be created. If the link types are created, they are added to the link type table 103. As source and destination assets are created, in connection with a particular relationship, the logical UOI identification, UOI identifications are added to the UOI; and the source UOI and the corresponding destination UOI and corresponding link types are added to the UOI link type table 105.
  • Links may be traversed as follows: Reference is made to both Figure 6 and Figure 7.
  • Figure 7 illustrates a sliding window 703 and an exemplary portion of linked assets.
  • the linked assets include the current UOIs 701, the source UOIs at 705a, 705b, and the destination UOI 707a, 707b and
  • the brochure 705a is a parent of the press release 701; and the web page
  • the press release 705b is also the container of the press release 701.
  • the press release itself is container of logo 707a, text
  • the press release 701 is also "source of" ticker 707c.
  • the sliding window 703 is currently located on a press release 701. The sliding window can be moved to anyone of the linked source objects or destination objects corresponding to the press release.
  • the sliding window When located on one of the source objects or destination objects, the sliding window would indicate for that UOI, all of its source and destination links.
  • Update would permit the system to modify the relationships between UOIs. For example, an existing link type between a source and a destination UOI could be replaced with a different link type.
  • a source or destination UOI could be replaced with a changed UOI.
  • the delete function illustrated in Figure 6 provides the capability to unlink the asset from the relationship. Note that the delete function does not delete the asset.
  • the digital asset management life cycle is as follows. In order to create UOIs, a system preferably has a preexisting list of the assets, and assigns to each of the assets a unique identification.
  • assets may be created and added on the fly, and unique identifications added on the fly.
  • UOIs are ingested, imported or loaded.
  • any ancillary Metadata is preferably created and the Metadata table is loaded.
  • each of the digital assets are assigned into the UOI table.
  • the assets are linked and placed into the UOI link table.
  • the currently linked assets may be searched and viewed, as discussed above in the link life cycle.
  • Assets may also be linked during a bulk import.
  • a link selection will be added within the UOIS tag off the XML input file, as show below: DTD modification:
  • RELATED-ASSET one way to uniquely identify the destination asset to which the current asset will be linked. If this tag is used, the value should be a fully qualified path to the current location of the file.
  • PO-REFERENCE a second way to uniquely identify the destination asset to which the current asset will be linked. If this tag is used, the value should match the PO_REFERENCE value, in the UOIS section, of another asset in the same input file.
  • ASSET-ID a third way to uniquely identify the destination asset to which the current asset will be linked. This tag can be used to link assets being imported to assets in the repository.
  • this optional tag may be used to provide a value, which will determine the position of the related assets among other destination assets of the same source asset and relation. If this tag is not used, no sequence is imposed on the destination assets.
  • this optional tag may be used to indicate whether a hard or soft link should be created to the destination asset. If this tag is not used, a hard link will be created by default. This is equivalent to the tag having a value of W.
  • the following rules are advantageously used to guide the creation of relations between asset pairs during bulk import:
  • Links may be created between pairs of assets created during the same bulk import job. Linking new assets to existing repository assets should not be supported through bulk import.
  • Reciprocal relationships may be created automatically. If reciprocal relations are automatically created, they should be created for all relations for which a reciprocal link type has been specified in the
  • LINK_TYPES table via link administration. If there is no reciprocal link type (e.g., value is NULL), no reciprocal relation is created. If reciprocal relations are not to be automatically created, this functionality may still be provided by explicitly including the reciprocal LINK stanza in the import file.
  • Reciprocal relations may then be defined on an as needed basis for each asset pair.
  • each asset pair may have a different link type from the others in the same file.
  • interactive import which preferably assumes the same link type for all asset pairs in the same import job.
  • the foreign key constraints drawn between the UOI_LINKS and the UOIs are optional as the source and destination assets need not be UOIs.
  • the functionality of a "hard” or “soft” link if desired, may be represented in the data model by the USEJLATEST NERSION information in the UOIs.
  • a soft link is recorded with a value of ⁇ ' in this column. The default value is 1ST'.
  • the logic should be implemented via a trigger. Given that, product assembly will be able to use the DEST_VALUE directly and not have to determine the newest version.

Landscapes

  • Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Theoretical Computer Science (AREA)
  • Human Computer Interaction (AREA)
  • Data Mining & Analysis (AREA)
  • Databases & Information Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

L'invention se rapporte à un procédé et à un système pour la gestion de liaisons relatives à des avoirs numériques. Le système repose sur l'utilisation d'éléments d'information qui concernent des unités d'information UOI (101), d'éléments d'information qui concernent des types de liaisons (103), et de moyens de stockage liés aux liaisons UOI (105). Eventuellement, on utilise une table de consultation de métadonnées auxiliaire (107). Une valeur d'origine (109) et une valeur de destination (111) sont établies à partir des UOI (101) et fournies aux liaisons UOI (105). Le type de liaison (113) est établi à partir du fichier des types de liaisons (103) et fourni aux liaisons UOI (105). Eventuellement, le type d'origine (115) et le type de destination (117) sont établis à partir de la table de consultation de métadonnées (107).
PCT/US2001/018784 2000-06-14 2001-06-12 Procede et systeme pour la gestion de liaison WO2001097070A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU2001268314A AU2001268314A1 (en) 2000-06-14 2001-06-12 Method and system for link management

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US59315000A 2000-06-14 2000-06-14
US09/593,150 2000-06-14

Publications (1)

Publication Number Publication Date
WO2001097070A1 true WO2001097070A1 (fr) 2001-12-20

Family

ID=24373581

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2001/018784 WO2001097070A1 (fr) 2000-06-14 2001-06-12 Procede et systeme pour la gestion de liaison

Country Status (2)

Country Link
AU (1) AU2001268314A1 (fr)
WO (1) WO2001097070A1 (fr)

Cited By (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2004036459A2 (fr) * 2002-10-19 2004-04-29 Philips Intellectual Property & Standards Gmbh Systeme et procede de traitement de documents electroniques
FR2886750A1 (fr) * 2005-06-06 2006-12-08 Boozter Technologies Sarl Formant d'enregistrement de donnees et procedes l'utilisant.
US7184170B2 (en) 2002-03-28 2007-02-27 Clariant Finance (Bvi) Limited Method and apparatus for color management
US7660783B2 (en) * 2006-09-27 2010-02-09 Buzzmetrics, Inc. System and method of ad-hoc analysis of data
US8180814B1 (en) 2011-02-16 2012-05-15 Docbert, LLC System and method for file management
US8482762B2 (en) 2002-04-26 2013-07-09 Clariant Finance (Bvi) Limited Method and apparatus for approving color samples
US8973022B2 (en) 2007-03-07 2015-03-03 The Nielsen Company (Us), Llc Method and system for using coherence of biological responses as a measure of performance of a media
US8989835B2 (en) 2012-08-17 2015-03-24 The Nielsen Company (Us), Llc Systems and methods to gather and analyze electroencephalographic data
US9215996B2 (en) 2007-03-02 2015-12-22 The Nielsen Company (Us), Llc Apparatus and method for objectively determining human response to media
US9320450B2 (en) 2013-03-14 2016-04-26 The Nielsen Company (Us), Llc Methods and apparatus to gather and analyze electroencephalographic data
US9351658B2 (en) 2005-09-02 2016-05-31 The Nielsen Company (Us), Llc Device and method for sensing electrical activity in tissue
US9622702B2 (en) 2014-04-03 2017-04-18 The Nielsen Company (Us), Llc Methods and apparatus to gather and analyze electroencephalographic data
US9646013B2 (en) 2011-02-16 2017-05-09 Docbert Llc System and method for file management
US10180986B2 (en) 2005-06-16 2019-01-15 Buzzmetrics, Ltd. Extracting structured data from weblogs

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5303379A (en) * 1987-08-21 1994-04-12 Wang Laboratories, Inc. Link mechanism for linking data between objects and for performing operations on the linked data in an object based system
US5721911A (en) * 1996-06-25 1998-02-24 International Business Machines Corporation Mechanism for metadata for an information catalog system

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5303379A (en) * 1987-08-21 1994-04-12 Wang Laboratories, Inc. Link mechanism for linking data between objects and for performing operations on the linked data in an object based system
US5721911A (en) * 1996-06-25 1998-02-24 International Business Machines Corporation Mechanism for metadata for an information catalog system

Cited By (29)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7184170B2 (en) 2002-03-28 2007-02-27 Clariant Finance (Bvi) Limited Method and apparatus for color management
US8482762B2 (en) 2002-04-26 2013-07-09 Clariant Finance (Bvi) Limited Method and apparatus for approving color samples
WO2004036459A3 (fr) * 2002-10-19 2004-09-30 Philips Intellectual Property Systeme et procede de traitement de documents electroniques
WO2004036459A2 (fr) * 2002-10-19 2004-04-29 Philips Intellectual Property & Standards Gmbh Systeme et procede de traitement de documents electroniques
FR2886750A1 (fr) * 2005-06-06 2006-12-08 Boozter Technologies Sarl Formant d'enregistrement de donnees et procedes l'utilisant.
WO2006131511A1 (fr) * 2005-06-06 2006-12-14 Boozter Technologies Format d'enregistrement de données et procédés l'utilisant
US10180986B2 (en) 2005-06-16 2019-01-15 Buzzmetrics, Ltd. Extracting structured data from weblogs
US11556598B2 (en) 2005-06-16 2023-01-17 Buzzmetrics, Ltd. Extracting structured data from weblogs
US10506941B2 (en) 2005-08-09 2019-12-17 The Nielsen Company (Us), Llc Device and method for sensing electrical activity in tissue
US11638547B2 (en) 2005-08-09 2023-05-02 Nielsen Consumer Llc Device and method for sensing electrical activity in tissue
US9351658B2 (en) 2005-09-02 2016-05-31 The Nielsen Company (Us), Llc Device and method for sensing electrical activity in tissue
US7660783B2 (en) * 2006-09-27 2010-02-09 Buzzmetrics, Inc. System and method of ad-hoc analysis of data
US9215996B2 (en) 2007-03-02 2015-12-22 The Nielsen Company (Us), Llc Apparatus and method for objectively determining human response to media
US8973022B2 (en) 2007-03-07 2015-03-03 The Nielsen Company (Us), Llc Method and system for using coherence of biological responses as a measure of performance of a media
US9646013B2 (en) 2011-02-16 2017-05-09 Docbert Llc System and method for file management
US8180814B1 (en) 2011-02-16 2012-05-15 Docbert, LLC System and method for file management
US9907482B2 (en) 2012-08-17 2018-03-06 The Nielsen Company (Us), Llc Systems and methods to gather and analyze electroencephalographic data
US8989835B2 (en) 2012-08-17 2015-03-24 The Nielsen Company (Us), Llc Systems and methods to gather and analyze electroencephalographic data
US10779745B2 (en) 2012-08-17 2020-09-22 The Nielsen Company (Us), Llc Systems and methods to gather and analyze electroencephalographic data
US10842403B2 (en) 2012-08-17 2020-11-24 The Nielsen Company (Us), Llc Systems and methods to gather and analyze electroencephalographic data
US9215978B2 (en) 2012-08-17 2015-12-22 The Nielsen Company (Us), Llc Systems and methods to gather and analyze electroencephalographic data
US9060671B2 (en) 2012-08-17 2015-06-23 The Nielsen Company (Us), Llc Systems and methods to gather and analyze electroencephalographic data
US11980469B2 (en) 2012-08-17 2024-05-14 Nielsen Company Systems and methods to gather and analyze electroencephalographic data
US9668694B2 (en) 2013-03-14 2017-06-06 The Nielsen Company (Us), Llc Methods and apparatus to gather and analyze electroencephalographic data
US9320450B2 (en) 2013-03-14 2016-04-26 The Nielsen Company (Us), Llc Methods and apparatus to gather and analyze electroencephalographic data
US11076807B2 (en) 2013-03-14 2021-08-03 Nielsen Consumer Llc Methods and apparatus to gather and analyze electroencephalographic data
US9622703B2 (en) 2014-04-03 2017-04-18 The Nielsen Company (Us), Llc Methods and apparatus to gather and analyze electroencephalographic data
US9622702B2 (en) 2014-04-03 2017-04-18 The Nielsen Company (Us), Llc Methods and apparatus to gather and analyze electroencephalographic data
US11141108B2 (en) 2014-04-03 2021-10-12 Nielsen Consumer Llc Methods and apparatus to gather and analyze electroencephalographic data

Also Published As

Publication number Publication date
AU2001268314A1 (en) 2001-12-24

Similar Documents

Publication Publication Date Title
US7590934B2 (en) Meta-document and method of managing
US7685136B2 (en) Method, system and program product for managing document summary information
JP4489994B2 (ja) 話題抽出装置、方法、プログラム及びそのプログラムを記録する記録媒体
US7072983B1 (en) Scheme for systemically registering meta-data with respect to various types of data
JP4990431B2 (ja) 階層状に複式化されたドキュメントからの情報検索
US7991805B2 (en) System for viewing and indexing mark up language messages, forms and documents
US7366729B2 (en) Schema framework and a method and apparatus for normalizing schema
JP5229226B2 (ja) 情報共有システム、情報共有方法、および情報共有プログラム
US20070050467A1 (en) Digital asset management system, including customizable metadata model for asset cataloging and permissioning of digital assets, such as for use with digital images and songs
US20070028162A1 (en) Reusing content fragments in web sites
WO2001097070A1 (fr) Procede et systeme pour la gestion de liaison
WO2007001639A2 (fr) Stockage et utilisation de diapositives de presentation de diapositives
JP2010520549A (ja) データの記憶および管理の方法
MX2007011598A (es) Campos de determinacion para archivos presentables y esquemas de lenguaje de marcacion extensible para bibliografias y citas.
US20050004891A1 (en) Methods and systems for categorizing and indexing human-readable data
US6694357B1 (en) Accessing, viewing and manipulation of references to non-modifiable data objects
US20100218139A1 (en) Search-friendly templates
US20110252313A1 (en) Document information selection method and computer program product
Ferilli et al. Automatic topics identification for reviewer assignment
Carmel et al. XML and information retrieval: a SIGIR 2000 workshop
US20090112720A1 (en) Identifying And Displaying Messages Containing An Identifier
JP2002202973A (ja) 構造化文書管理装置
Ceri et al. WebML application frameworks: a conceptual tool for enhancing design reuse
US8327255B2 (en) Computer program product containing electronic transcript and exhibit files and method for making the same
Kashyap Classified Catalogue Code of Ranganathan: A proposal to make it compatible for developing compute based library information systems

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CZ DE DK DM DZ EC EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE TR BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

122 Ep: pct application non-entry in european phase
NENP Non-entry into the national phase

Ref country code: JP