WO2004057464A2 - Modele de schema d'objet de serveur - Google Patents

Modele de schema d'objet de serveur Download PDF

Info

Publication number
WO2004057464A2
WO2004057464A2 PCT/US2003/040739 US0340739W WO2004057464A2 WO 2004057464 A2 WO2004057464 A2 WO 2004057464A2 US 0340739 W US0340739 W US 0340739W WO 2004057464 A2 WO2004057464 A2 WO 2004057464A2
Authority
WO
WIPO (PCT)
Prior art keywords
term
schema
vocabulary
relationship
objects
Prior art date
Application number
PCT/US2003/040739
Other languages
English (en)
Other versions
WO2004057464A3 (fr
Inventor
Breanna Daphne Anderson
Original Assignee
Schemalogic, 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 Schemalogic, Inc. filed Critical Schemalogic, Inc.
Priority to EP03800035A priority Critical patent/EP1581865A2/fr
Priority to CA002510835A priority patent/CA2510835A1/fr
Priority to AU2003299755A priority patent/AU2003299755A1/en
Publication of WO2004057464A2 publication Critical patent/WO2004057464A2/fr
Publication of WO2004057464A3 publication Critical patent/WO2004057464A3/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/451—Execution arrangements for user interfaces
    • G06F9/454—Multi-language systems; Localisation; Internationalisation
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/28—Databases characterised by their database models, e.g. relational or object models
    • G06F16/284—Relational databases
    • G06F16/288—Entity relationship models
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/28—Databases characterised by their database models, e.g. relational or object models
    • G06F16/289—Object oriented databases

Definitions

  • the present invention is related to software, and more specifically to contextualizing schemas using differing relational types.
  • a schema model allows objects to be contextualized by using stored values that are used to localize the object.
  • the values used for localizing each object that is to be localized are stored in a container class element that is associated with the object that is to be localized.
  • the object having localized term values stored in a container class element is related to another object wherein the objects are related using one of a hierarchical term and an entry term relationship.
  • the associated values allow a user to override by redefinition default values presented by a controlled vocabulary system.
  • the user can further relate term objects by using hierarchical term, entry term, and related-term relationships. This arrangement allows users and systems to more effectively re-use standard data definitions.
  • FIGURES 1-3 show components of an exemplary environment in which the invention may be practiced.
  • FIGURE 4 is a schematic diagram of an example Schema Server Object Model, in accordance with the present invention.
  • FIGURE 5 is a schematic diagram showing a conventional vocabulary localization using entry terms.
  • FIGURE 6 is a schematic diagram showing an intrinsic vocabulary localization mechanism using entry terms, in accordance with the present invention.
  • FIGURE 7 is a schematic diagram showing a term relationship of one to many, in accordance with the present invention.
  • FIGURE 8 is a schematic diagram of two example structures that illustrate term relationships.
  • FIGURE 9 is a schematic diagram three classes of term relationship types, in accordance with the present invention.
  • FIGURE 10 is a schematic diagram of an example application of a Schema Server Object Model, in accordance with the present invention.
  • the meaning of "a,” “an,” and “the” includes plural reference, the meaning of “in” includes “in” and “on.”
  • the term “connected” means a direct electrical connection between the items connected, without any intermediate devices.
  • the term “coupled” means either a direct electrical connection between the items connected or an indirect connection through one or more passive or active intermediary devices.
  • Table 1 includes definitions for terms related to the present invention.
  • FIGURES 1-3 show components of an exemplary environment in which the invention may be practiced. Not all of the components may be required to practice the invention, and variations in the arrangement and type of the components may be made without departing from the spirit or scope of the invention.
  • FIGURE 1 shows a plurality of local area networks (“LANs”) 120 and wide area network (“WAN”) 130 interconnected by routers 110.
  • LANs local area networks
  • WAN wide area network
  • a router receives transmitted messages and forwards them to their correct destinations over available routes.
  • a router acts as a link between LANs, enabling messages to be sent from one to another.
  • Communication links within LANs typically include twisted pair, fiber optics, or coaxial cable, while communication links between networks may utilize analog telephone lines, full or fractional dedicated digital lines including Tl, T2, T3, and T4, Integrated Services Digital Networks (ISDNs), Digital Subscriber Lines (DSLs), wireless links, or other communications links known to those skilled in the art.
  • ISDNs Integrated Services Digital Networks
  • DSLs Digital Subscriber Lines
  • computers, such as remote computer 140, and other related electronic devices can be remotely connected to either LANs 120 or WAN 130 via a modem and temporary telephone link.
  • the number of WANs, LANs, and routers in FIGURE 1 may be increased or decreased arbitrarily without departing from the spirit or scope of this invention.
  • Computer-readable media includes any media that can be accessed by a computing device.
  • Computer-readable media may include computer storage media, communication media, or any combination thereof.
  • Communication media typically embodies computer-readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media.
  • modulated data signal means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal.
  • communication media includes wired media such as twisted pair, coaxial cable, fiber optics, wave guides, and other wired media and wireless media such as acoustic, RF, infrared, and other wireless media.
  • a server such as the server shown in FIGURE 2, may provide a WWW site, be a content server, a schema server, an authentication server, etc.
  • FIGURE 2 shows an exemplary server in accordance with aspects of the invention.
  • Server 200 may include many more components than those shown in FIGURE 2.
  • server 200 is connected to WAN/LAN 100, or other communications network, via network interface unit 210.
  • Network interface unit 210 includes the necessary circuitry for connecting server 200 to WAN/LAN 100, and is constructed for use with various communication protocols including the TCP/IP protocol.
  • network interface unit 210 is a card contained within server 200.
  • Server 200 also includes processing unit 212, video display adapter 214, and a mass memory, all connected via bus 222.
  • the mass memory generally includes random access memory (“RAM”) 216, read-only memory (“ROM”) 232, and one or more permanent mass storage devices, such as hard disk drive 228, a tape drive (not shown), optical drive 226, such as a CD- ROM/DVD-ROM drive, and/or a floppy disk drive (not shown).
  • the mass memory stores operating system 220 for controlling the operation of server 200.
  • This component may comprise a general purpose server operating system as is known to those of ordinary skill in the art, such as UNIX, LINUXTM, or Microsoft WINDOWS NT ® .
  • BIOS Basic input/output system
  • BIOS Basic input/output system
  • the mass memory as described above illustrates another type of computer-readable media, namely computer storage media.
  • Computer storage media may include volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information, such as computer readable instructions, data structures, program modules or other data. Examples of computer storage media include RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by a computing device.
  • the mass memory may also store program code and data for providing a WWW site. More specifically, the mass memory may store applications including server application program 230, and programs 234.
  • Server 200 also comprises input/output interface 224 for communicating with external devices, such as a mouse, keyboard, scanner, or other input devices not shown in FIGURE 2.
  • server 200 may further comprise additional mass storage facilities such as optical drive 226 and hard disk drive 228.
  • Hard disk drive 228 is utilized by server 200 to store, among other things, application programs, databases, and program data used by server application program 230. For example, schemas, customer databases, product databases, image databases, and relational databases may be stored.
  • FIGURE 3 depicts several components of client computer 300.
  • Client computer 300 may include many more components than those shown in FIGURE 3. However, it is not necessary that those conventional components be shown in order to disclose an illustrative embodiment for practicing the present invention.
  • client computer 300 includes network interface unit 302 for connecting to a LAN or WAN, or for connecting remotely to a LAN or WAN.
  • Network interface unit 302 includes the necessary circuitry for such a com ection, and is also constructed for use with various communication protocols including the TCP/IP protocol, the particular network configuration of the LAN or WAN it is connecting to, and a particular type of coupling medium.
  • Network interface unit 302 may also be capable of connecting to the Internet through a point- to-point protocol (“PPP") connection or a serial line Internet protocol (“SLIP”) connection as known to those skilled in the art.
  • PPP point- to-point protocol
  • SLIP serial line Internet protocol
  • Client computer 300 also includes BIOS 326, processing unit 306, video display adapter 308, and memory.
  • the memory generally includes RAM 310, ROM 304, and a permanent mass storage device, such as a disk drive.
  • the memory stores operating system 312 and programs 334 for controlling the operation of client computer 300.
  • the memory also includes WWW browser 314, such as Netscape's NAVIGATOR ® or Microsof 's INTERNET EXPLORER ® browsers, for accessing the WWW.
  • Input/output interface 320 may also be provided for receiving input from a mouse, keyboard, or other input device.
  • the memory, network interface unit 302, video display adapter 308, and input/output interface 320 are all connected to processing unit 306 via bus 322. Other peripherals may also be connected to processing unit 306 in a similar manner.
  • aspects of the invention may be embodied on server 200, on client computer 300, or on some combination thereof.
  • programming steps may be contained in programs 334 and/or programs 234.
  • client should be construed to refer to a process or set of processes that execute on one or more electronic device, such as client computer 300 of FIGURE 3.
  • a client is not limited, however, to running on a client computer. It may also run on a server, such as server 200 or be distributed among various electronic devices, wherein each device might contain one or more processes or routines that together constitute a client application.
  • client should be construed, in addition or in lieu of the discussion above, to be a device upon which one or more client processes execute, for example, client computer 300 or server 200.
  • server should be construed to refer to a process or set of processes that execute on one or more electronic devices, such as server 200.
  • a server is not limited to running on a server computer. Rather, it may also execute on what would typically be considered a client computer, such as client computer 300 of FIGURE 3, or be distributed among various electronic devices, wherein each device might contain one or more processes or routines that together constitute a server application.
  • server should be construed, in addition or in lieu of the discussion above, to be a device upon which one or more server processes execute, for example, server 200 or client computer 300.
  • the object model in accordance with the present invention provides specific objects that can be used to model schemas for applications such as database or enterprise applications.
  • the schemas may also be system independent, such as the structure of a web form, a search UI (user interface), or tagging screen.
  • search UI user interface
  • tagging screen a screen that can be used to model schemas for applications such as database or enterprise applications.
  • the same "schema" may exist in multiple systems or instantiations.
  • CMS content management systems
  • CRM customer relationship management systems
  • proprietary systems developed in house.
  • CMS content management systems
  • CRM customer relationship management systems
  • the value of these applications is their ability to collect, store, manage, and retrieve information. Even when these applications have been designed and implemented well most organizations are finding that in order to truly take advantage of the information already collected, they need to be able to share the information between systems. For example, the information in a CRM system is typically far more valuable when it can be used in conjunction with a CMS. h this situation a company can better take advantage of its information assets by using the material in the CMS by targeting appropriate information to individual customers.
  • the general problem at hand is the problem of sharing, managing, and using data from disparate systems. This problem may take many different forms, but in each incarnation the issues of data compatibility, maintenance of data standards, impact analysis, and propagation of schema standards are usually implicated.
  • An object model in accordance with the present invention provides a set of tools, which allows users to:
  • the object model in accordance with the present invention provides a solution to the problem faced by many large organizations.
  • the object model provides flexibility that is apparent in both the schema modeling the object model supports and the ability of the object model that allows for associating context specific information to schema objects.
  • Table 2 describes an object model that provides the following objects that allow for the associating of context specific information to other schema objects:
  • the object model as a whole provides for the modeling of a centralized collection of schema objects, which can allow organizations to more effectively describe their electronic information.
  • the five objects listed above provide the ability to specifically associate context dependent information to the schema definitions. This allows organizations to more effectively share and re-use schema objects across multiple systems
  • Table 3 describes common types of relationships between objects:
  • FIGURE 4 is a schematic diagram of an example Schema Server
  • Schema Object is a super- class of five major Schema Server conceptual objects: Content Class, ElementType, Vocabulary, Term and Vocabulary View. All of these objects have their own specific semantics, but share the common characteristics of being Schema Objects:
  • Schema Objects can be associated with permissions, contracts, changes, and incidents.
  • a Schema Object may have zero-or- more permissions against it. (See "Permission” object described below.) This is a typically a navigable relationship. The list of permissions against any given Schema Object may be extracted from the system.
  • a Schema Object may have one optional Contract.
  • the Contract specifies certain parameters for the Change Management process that is initiated when this Schema Object is involved in a data modifying operation (Add, Update, Delete, Move). If a change is made to a Schema Object that does not have a contract directly associated with it, "Contract Negotiation” logic is invoked to identify the most relevant contract to be used according to special impact analysis logic specified elsewhere. (See “Contract” object below.)
  • a Schema Object may have one optional Change associated with it at any time.
  • the associated Change object represents the current or most recent change transaction against the associated Schema Object and tracks the change state information.
  • the Change object may also store certain Contract conditions as of the initiation of the change process to ensure that subsequent changes to the Contract do not undesirably impact the Change rules.
  • Incident objects typically track every API transaction against a Schema Object.
  • a Schema Object may have zero-or-more incidents associated with it. Incidents can be purged or rolled out of the online system to reduce system bulk if necessary.
  • the system administrator may optionally maintain a complete log of all incidents for all schema objects.
  • Content Classes can be used to abstractly represent virtually any aggregate structure definition.
  • Content Class objects are a sub-class of Schema
  • Schema Object As such, all properties and relationships of Schema Object typically apply to Content Class.
  • Content Classes are, simply, lists of Element Type references.
  • Each reference to an externally defined Element Type definition usually includes optional overriding properties that contextualize the reference in such a way as to refine, restrict or recast without violating the underlying definition or compromise mapability of the Schema Object.
  • a Content Class may be defined as "creatable” which corresponds to the inverse of the conventional Object Oriented concept of "abstract,” which indicates whether the structure definition is (or is not) intended for instantiation, or intended as a conceptual building block for other inherited or aggregating complex structures (such as child content classes or other aggregate content classes).
  • a Content Class may be defined as an "option list” indicating that of the referenced Element Types, only one may appear in any instantiation.
  • Content Class objects are used to define abstract data structure definitions as aggregations of Element Type references. These may be used to describe actual database schemas, Web Forms, Search h terfaces, other data definitions, and the like.
  • Content Class objects are also subject to class inheritance. For example, each Content class other than the root class has one parent. Each content class inherits the elements associated its ancestors. To describe non-essential idiosyncrasies of elements some of the properties of an element can be overridden. (See the Class Element object below).
  • the grant of "owner” permission to a class implicitly grants “owner” permission to its sub-classes. This permission grants the ability to add, update and delete any of these Content Classes (within the constraints of change control collaboration) and grants the permission to grant permissions on these Schema Object to other users.
  • Impact analysis evaluation flows from a class toward its descendent classes (leaf nodes). If a change is made to an Element Type referenced by a Class CI, the descendent classes of CI can be considered impacted. Any users with permissions to any descendent classes can be considered impacted and receive votes on the Change process.
  • Contract negotiation logic typically flows from an impacted Content Class toward the root of the Content Class tree. If, within an individual impact analysis graph, multiple Content Classes are individually impacted by outside Element Type references, the common parent of directly impacted Content Classes is assessed. The contract in force is evaluated as the contract associated with the class closest to the common parent Content Class.
  • Content Classes may have one or more elements associated with them. Elements can be either directly associated with the content class, or inherited from parent content classes. Each relationship between a Content Class and Element Type can be qualified by a Class Element object that provides contextual properties that either override or otherwise alter the interpretation or rules for use of the Element Type definition.
  • a Schema Server typically does not support explicit embedding definitions of sub-elements withm the scope of the encompassing structure (in this case Content Class).
  • the sub-element definitions are typically drawn from a globally visible set of Element Type definitions.
  • the value of this approach for applications is to encourage global visibility and maximize reuse of definitions, while providing for local contextuahzation.
  • Local scope definition of Elements (or Attributes) typically trades off manageability for convenience.
  • All Content Classes other than the built-in root class typically have one parent Content Class. This relationship defines the class inheritance mechanism. Consequently all Content Classes can be organized as a single- inheritance tree.
  • Element Type objects define reusable data component definitions that control or represent corresponding structures in one or more client systems and, as such, are a central part of schema modeling.
  • Element Type objects are flexible objects that represent a set of concepts that are often considered discrete structures by some models (e.g., both XML Elements and Attributes can be modeled as Element Types).
  • Table 6 defines mapping concepts within typical disciplines or models:
  • Element Types commonly define simple, “scalar” data type definitions such as “Title”, “Author”, “PurchaseQuantity”, “SKU”, “DueDate” or “FlowRate” that are expressible as single values of common data types such as integer, string, date-time or floating-point number.
  • Element Types represent a Content Class for purposes of composition within another Content Class.
  • Element Types specify a variety of properties and relationships that Content Classes do not such as cardinality rules, Display Labels etc. Use of "class-Type" Element Types generally simplifies the modeling of complex Content Class structures.
  • Vocabulary-type Element Types model, in an implementation- independent way, a wide range of requirements where an Element Type may only contain a value from a well defined and intentionally controlled list of values.
  • Element Types that are abstracted prototypes for other more concrete Element Type definitions.
  • an Element Type may be called “URLType” and define the basic data, semantic and syntactic rules for representation of an URL including the regular expression rules for an W3C URL string.
  • Other Element Types e.g. "ImageURL” may refer to "URLType” as the basis for their definition rather than the primitive data type "string.” This facilitates centralized definition of certain data rules and definitions and enhances understandability and manageability.
  • Table 7 describes various properties that are associated with Element Type:
  • Object definitions in this model are used to associate concepts with Element Types.
  • Conventional modeling systems that aspire to provide an overarching modeling system such as UML include a similar concept, called "Property.” Also Data Dictionaries or Repositories also frequently provide for a common catalog of data definitions.
  • a globally unique identifier as the primary identifier of Element Types provides for bridging namespaces more effectively.
  • Use of globally unique identifiers enables effective element re-use across systems as well as supporting the notion of class elements.
  • Generalized Valid Rule / Valid Pattern mechanism for defining data validation mechanism provides for both a centralized definition of these rules, open extensibility while not binding to a particular technical implementation of these rules. Identification of a validating set of values (Vocabulary-type Element Type) is done by reference to an external definition and not embedded within the Element Type definition itself. This provides for multiple Element Types sharing the same or variant views of the same domain (e.g., Geography).
  • Element Types include not only machine-readable definitions of data type but human-readable definitions, for management and for-multi-lingual end-user representation (labels and descriptions), in forms and reports. Centralized management of end-user human readable labels and definitions enhances consistent use and understandability of shared information. Manageability through a common namespace, searchability, permissions, bi-directionally navigable relationships and intrinsic change management substantially enhance lifecycle usefulness and reusability of Element Type definitions over conventional approaches.
  • An Element Type can optionally have a one-to-one (1-1) relationship with a Vocabulary. If an Element Type is of type Vocabulary, it may be associated with one Vocabulary. Vocabularies provide a list of allowed values that define the scope of legal values to be assigned to the Element.
  • Element Types Association of the Vocabulary with the Element Type by reference allows the same Vocabulary Domain to be utilized by multiple Element Types fo different purposes (See Vocabulary View below).
  • Element Types define not only a data definition but also can define a semantic use purpose. If the Vocabulary has one or more vocabulary views associated with it, then a vocabulary view may also be associated with the element.
  • the Vocabulary View mechanism provides a useful mechanism to form a subset of a larger vocabulary for specialized purposes. For example, a list of product categories from a products vocabulary including 5000 separate terms is required for the Element Type "ProductCategory.” The Vocabulary "Products” Element Type is specified and the Vocabulary View "AUProductCategories” Element Type is further specified to restrict the values to the desired subset for this application.
  • Element Types may be referenced by zero-or-more Content Classes. In a well-designed system many Element Types can be shared by many Content Classes. This sharing of Element Types encourages data homogeneity, data sharing, and data re-use across systems and is an important part of centralizing the schema modeling process as this is where the elements can be "re-used.”
  • Element Type definition use of a common Element Type definition by multiple systems and structures, is not typically supported by Relational systems (and is poorly supported by UML and XML definitions), particularly with regards to lack of bidirectional navigability and manageability. Impact analysis is not easily accomplished. Embedding of Element, Attribute or property definitions inhibits reuse.
  • the example object model emphasizes and enforces the mechanism of central definition with unique identifiers and bidirectional relationships to provide an optimal condition for Element Type reuse. All relationships to Content Classes can be qualified by Class Element objects to condition and qualify the application of the Element Type.
  • Vocabularies provide a flexible mechanism for describing sets of approved tagging values for Elements.
  • Vocabularies can be, for example, simple lists of terms or complex hierarchies, including: Geographical terms (Regions, countries, States, Cities%), Product Hierarchies, Site navigation hierarchies, Marketing Segmentation taxonomies, Scientific Taxonomies.
  • Vocabularies provide a manageable and implementation independent mechanism for describing a wide variety of finite, controlled and enumerated domain structures that occur frequently in real data management applications.
  • manageability of structures can be provided by incorporation of granular, inherited permission management, impact analysis, contracts and change management to vocabularies. This functionality can provide substantial advantages for large organizations developing and maintaining critical definitions.
  • Intrinsic support for localization can simplify administration and substantially increase the power and usability of vocabularies to power cross- language search and retrieval.
  • Extensible Term Relationship Types can be implemented by taxonomists to design arbitrarily specific and meaningful relationship types that can subsequently be used to analyze, navigate and "subset" vocabularies.
  • Vocabulary views provide a parametrically defined, managed and controlled subset definition mechanism in combination with extensible term relationship types to support the management of common vocabularies that are useful across complex organizations.
  • Vocabulary views (having a 1-to-M relationship) allow users flexibility to present different views or subsets of vocabularies to meet the needs of different contexts.
  • Each vocabulary may have multiple views associated with it.
  • a vocabulary is a collection of relationships between terms. The term relationships themselves actually reference the terms associated with the vocabulary.
  • Terms are the conceptual nodes, represented by individual words or phrases used in vocabularies. In a Schema Server they are much more than just a string. Terms are identified by a lifetime GUID, and include extended internal descriptions and localized translations of term values and descriptions. When used in a vocabulary terms are "related" to each other via "term relationships.” By following these relationships there is a path up to the Root term of the vocabulary. Terms can also be used in multiple vocabularies.
  • the Object Model Term typically inherits all properties of Schema Object, including global Id, Name, Description and workflow properties and change management relationships. Typical properties of the Object Model Term are shown in Table 10:
  • a term value optionally can have a one-to-many (1 - M) relationship. This relationship is used for localization of terms. Not all terms need to have a Term Value (or localized value) but this relationship does allow terms to have different values and descriptions in the context of different languages.
  • FIGURE 5 is a schematic diagram showing a conventional vocabulary localization using entry terms. In accordance with the present invention, this conventional approach is supported but is supplemented with an intrinsic localization mechanism.
  • Term localization is incorporated as an intrinsic property set of the Term object. Management is simplified as the term localizations are carried with the Term wherever it is used (in different Vocabularies). Workflow processes are streamlined as modifications to localizations are managed as properties changes to the tenn. Management of localization processes is enhanced as it is now relatively easy to identify terms within a vocabulary that perhaps have (or have not been) localized in a particular language. Use of localized terms is enhanced as it is now relatively easy to extract a given vocabulary in any language into which it has been localized.
  • FIGURE 6 is a schematic diagram showing an intrinsic vocabulary localization mechanism using entry terms, in accordance with the present invention
  • the localized values are stored as properties of the Term
  • FIGURE 7 is a schematic diagram showing a term relationship of one to many, in accordance with the present invention.
  • each Term Relationship has an Origination 610 and a Destination 620 (parent-child) term associated with it.
  • Origination 610 and a Destination 620 (parent-child) term associated with it.
  • Destination 620 parent-child
  • the bold lines are the actual term relationship objects.
  • “Oregon” and “Washington” are the “Destination” 620 terms
  • “States” is the "Origination” 610 term.
  • Vocabulary Views help to reconcile the need for centralized management of enterprise Vocabularies with the need of individual subscribers to consume subsets of sometimes overwhelmingly large sets of terms.
  • Table 10 shows example properties of Vocabulary Views:
  • Vocabulary Views provide a unique, manageable mechanism that allows for large, complex, aggregate or highly multi-constituent vocabularies in a collaborative environment.
  • Vocabulary Views are defined parametrically and use only pre-defined relationships as the mechanism for sub-setting views. From the standpoint of manageability through impact analysis, this approach is markedly superior to a procedural or even non-procedural query-based method based on term properties.
  • Impact analysis logic can determine whether and which vocabulary views are impacted by vocabulary (term or term relationship) changes
  • Vocabulary Views are managed as SchemaObjects with the conferred values (Permission control, upstream and downstream impacts, voting, replication);
  • a Vocabulary View is provided using a many-to-one relationship (M - 1). Each Vocabulary view typically must refer to no more than one Vocabulary. Vocabulary views allow users flexibility in the way they view, present, or "subset" vocabularies.
  • Vocabulary views may be associated with an element which is of type Vocabulary in a one-to-many (1 - M) relationship. If the vocabulary associated to the element has Vocabulary Views associated with it then a vocabulary view may be associated with the element as well.
  • a vocabulary may have 5000 terms in it, but a list of only product family names could be delivered to the Marketing department, while the list of all products and versions of products could be delivered to the technical support team.
  • Vocabulary views may be referenced by the class element object using a one-to-many (1 - M) relationship. This allows for changing the view of a vocabulary in the context of a content class.
  • Class Elements are objects used to describe and modify the usage of Element Types in the context of a Content Class. Class elements provide an opportunity to override some elements properties in a content class as well as providing for the ability to define further validation and display rules for an element in the context of a Content Class. Table 11 shows example properties of Class Elements:
  • the example Object Model explicitly does not support embedding definitions of sub- elements within the scope of the encompassing structure (in this case Content Class). All sub-element definitions are typically drawn from a globally visible set of Element Typedefinitions. The value of this approach for this application is to encourage global visibility and maximize reuse of definitions, while providing for local contextuahzation. Local scope definition of Elements (or Attributes) trades off manageability for convenience.
  • the Term Relationship object relates two existing Term objects. A collection of these relations (links) between terms constitutes a vocabulary. Each link has an origination term and a destination term. The destination terms is generally treated as a "child" of the origination term. Depending on the TermRelType of the Term Relationship different business rules apply.
  • FIGURE 8 is a schematic diagram of two example structures that illustrate term relationships.
  • Seattle is the Destination term and Washington is the Origination Term.
  • Example 1 shows an invalid tree structure because the term "Washington" is a descendant of itself.
  • Table 12 shows example properties of the Term Relationship object:
  • Each Term Relationship is associated with a vocabulary in a one-to- one relationship. It is possible, when the Term Relationship is of type "Related", that the destination term relationship can refer to a term in a second vocabulary.
  • Each Term Relationship is associated with a Term Relationship Type (TermRelType).
  • TermRelType can have different business rules associated with it, which describe how the Term Relationship can be used in the Vocabulary.
  • Each term relationship typically has a required one to one relationship with both an Origination Term and a Destination Term.
  • Term Value is an object that allows for the "localization" of vocabulary terms. Each Term may have one term value per language. The list of languages can be managed as one of the enumerated lists mentioned below in Table 13. When using this feature, the te ⁇ n "Name” and “description” are typically localized.
  • Table 13 shows example properties of the Term Relationship object:
  • a conventional method for localizing terms in controlled vocabularies is to represent the localized values as separate terms associated to the "preferred term" with a special type of relationship (frequently called an "entry te ⁇ n" relationship).
  • this conventional approach is supported but is supplemented with an intrinsic localization mechanism.
  • Term localization can be incorporated as an intrinsic property set of the Term object. Management is thereby simplified as the term localizations are carried with the Term wherever it is used (e.g., in different Vocabularies). Workflow processes are streamlined as modifications to localizations are managed as properties changes to the term. Management of localization processes is enhanced as it is now relatively easy to identify terms within a vocabulary that have and/or have not been localized in a particular language. Use of localized terms is enhanced as it is relatively easy to extract a given vocabulary in any language into which it has been localized.
  • the Term Value is used when a term is "Localized". Thus, each Term may have multiple values where each value is identified with a particular, defined, context. This context may be a language, but it could also be per system, whatever the user deems necessary.
  • the list of "Contexts” is described in the "Languages” enumerated list.
  • the Term Value is typically used in a one-to-one (1 - 1) relationship.
  • the TermRelType object describes the Term Relationship object. There are typically three classes of Term Relationship Types and each has a different set of business rules associated with it.
  • FIGURE 9 is a schematic diagram three classes of Term Relationship Types, in accordance with the present invention.
  • Hierarchical Term Relationships are the primary relationship type used to construct most Vocabulary relationships. These describe a "parent-child” relationship and are often referred to as “Broader Term-Narrower Term” relationships. Entry Term Relationships (ET) are often referred to as synonym relationships. The Destination term in these relationships is generally an alternate form of the Originating Term. A destination term in an ET relationship cannot then be an Originating term for other terms in a vocabulary.
  • RT Related Term Relationships
  • See Also relationships
  • RT Related Term Relationships
  • HT Transactional Term Relationships
  • an RT relationship could occur between the terms “Seattle” and "Portland”. In this case the relationship could be used to describe Port cities in the Pacific Northwest.
  • the following example gives potential uses of these relationships.
  • Related term-type relationships can span vocabularies. When related terms point from a term in one vocabulary to a term in another vocabulary, the target tenn may not be removed from it's vocabulary as long as the relationship exists
  • Table 14 shows example properties of the TermRelType object:
  • Each Term Relationship is associated with a Term Relationship Type in a one-to-many (1 - M) relationship such that the appropriate business rules, display rules, and usage rules can be applied to the term relationship.
  • Term relationship types are organized in a simple hierarchy.
  • the base set of Term Relationship Type classes are as describe above: HT, ET, and RT.
  • Term relationship types inherit the business rules of their parent type class.
  • Each Parent TennRelType is associated with child TermRelTypes in a one-to-many ( 1 - M) relationship.
  • Schema User is an object that describes users of the system. Each user has a Global Role assigned, which is either Administrator or User. Actual permissions per object are usually described in the Permission object.
  • Table 15 shows example properties of the Schema User object:
  • the change control process determines if there are any users associated with the object and the permissions that Schema User has with regard to the Schema Object.
  • the Permissions object describes the rights the individual user has with regards to the object. One of these rights may be a voting right. If the user has voting rights to the object then there is also a relationship between the Schema User and a Vote object.
  • Permission describes the relationship between a SchemaUser object and a Schema Object.
  • the Permission describes the privileges a user has with regards to the management of a particular object.
  • Table 16 shows example properties of the Schema User object:
  • Permission objects establish relationships between Schema Users and any sub-class of SchemaObject (Content Class, Element Type, Vocabulary, Term, Vocabulary View).
  • the Permissions object is an implementation of a concept commonly refened to as a "access control list" (ACL).
  • ACL access control list
  • Permission objects simplify system management by unifying the concepts of create/update/delete access control and voting rights per the prevailing votes.
  • the concept of Permission objects is navigable bi-directionally, allowing review and management of permissions from a user view, in addition to the view of owners of a specified object.
  • Permissions are viewable and manageable by Administrators on a system basis, including the ability to transfer or alter permissions easily from a system console. Permissions can be proxied to other users when they are temporarily unavailable (e.g., during sickness or vacation).
  • Permissions inherit down vocabulary and content class trees to simplify management of relevant domains of objects. Permissions are used to control and constrain creation and management rights to enhance object reuse of Element Types and Vocabularies. Permission controls are highly granular (apply to single Schema Object defimtions e.g. Term, Element Type compared to the standard methodology of managing access control on full document basis encompassing large sets of schema definitions.
  • Any Schema Object may have a Contract explicitly and immediately associated with it. If a Contract is not immediately associated with it, a Contract- in- force can be identified by the impact analysis logic when an impact is assessed. Each contract typically describes the parameters of the change management process.
  • the relevant contract is identified.
  • the relevant contract is used to determine the voting rights of the users impacted by the change.
  • the Contract also describes the duration of the voting period and other change control rules parameters as specified below in Table 17.
  • Contracts are optionally associated with Schema Objects in a one-to- one (1-1) relationship.
  • the concept of a rigorous, computer-enforceable agreement between the provider and consumer of a resource is extended from the realm of procedural logic to the realm of structural definition.
  • the concept is further extended from enforcing a static agreement about the definition of a resource to the idea that the process of change itself is subject to both customization by the parties and to subsequent enforcement by the agent software.
  • the Change object Before a change is made to any Schema Object managed in the system, it is processed through a consensus-based change control process.
  • the Change object typically maintains information about the change process.
  • the Change object In addition to keeping track of the pending change, the Change object also typically describes the start and end date of the proposed change, the date the change was instantiated, the originator of the change, as well as the type of change proposed and the Change Contract rules that are in force. If the change is accepted then the Schema Object is modified to reflect the change.
  • Table 18 shows example properties of the Change object:
  • the Change object is maintained in a one-to-one (1 -1) relationship with a Schema Object.
  • the Change object is associated with Vote objects in a one-to-many (1 - M) relationship.
  • the change is held in a "Pending" state until the voting round is complete.
  • the change object describes the proposed changes to the object. Upon the completion of the voting round and an approval of the change the changes are accepted and the change is completed.
  • the defined Change management object in concert with Contracts and Votes presents a mechanism that is both simpler to understand and use and simpler to manage and configure, which help foster a collaborative culture that in fact will want to use the mechanism.
  • the Vote object is used to manage the voting by Schema Users on proposed changes to Schema Objects.
  • Table 19 shows example properties of the Vote object:
  • a vote object is associated with a Schema User (who has a vote) in a many-to-one relationship. This is typically implemented as a bi-directionally navigable relationship.
  • each Change object there may be from one to many Schema Users voting on the change as in a one-to-many (1 - M) relationship.
  • Each Schema User can have multiple Changes to vote on.
  • a Schema Object usually has Enumeration objects, which typically include Global User Role, Permission Role, Language, Change State, Work State, and Element Data type.
  • Global User Role is used to regulate the application of business rules. Although two levels are shown in Table 20 below, more levels are possible. Table 20 shows example properties of the Global User Role object:
  • Table 21 shows example properties of the Permission Role object:
  • the Language object is a list of languages and their Local Identifier as discussed above.
  • the Change object may attain certain states that indicate the process of the change.
  • the Change object and its state are related to but distinct from the Schema Object workstate. (Other states are possible.)
  • Table 22 shows example states of the Change State object:
  • the Work State object lists certain states that indicate the status of an object.
  • Table 23 shows example states of the Work State object:
  • Schema Server An example is given to describe a potential use of the Schema Server. The example does not, however, provide an exhaustive discussion of all the ways the tool could be utilized. The example does show certain functionality related to the five schema objects which allow for contexrualizing schemas. These objects include, Class Element Object, Element Value Object, Vocabulary View Object, Term Value Object, and the Term Relationship Type Object. This is accompanied by a Visio diagram, "Object Model Example - corporate Merger.”
  • FIGURE 10 is a schematic diagram of an example application of a Schema Server Object Model, in accordance with the present invention.
  • Schema Server MegaCorp, a theoretical, large corporation, has just acquired a competitor, MiniCorp, a theoretical, small corporation.
  • MiniCorp a theoretical, small corporation.
  • Among the many tasks facing the new organization is the challenging task of bringing the different information technology tools into alignment so that customer and product information can be shared and ultimately integrated.
  • Step 1 - Identify Existing Elements in SchemaServer The data integration team finds that the notion of a customer is fairly similar in the two CRM systems. Using a Schema Server, the team is able to consolidate the common data elements. The consolidation process has many different faces as shown in Table 24:
  • a Content Class called "Customer” has been created and it has the elements listed in the Schema Server Element Name column in Table 1.
  • This Content Class has two child Content Classes called MegaCorpCustomer and the newly added MiniCorpCustomer.
  • MegaCorpCustomer has two child Content Classes called MegaCorpCustomer and the newly added MiniCorpCustomer.
  • Each of these Content Classes inherits the elements associated with the Customer Content Class, hi the Content Class "MiniCorpCustomer" a Class Element object is used to associate the name "First_Name" to the element "FirstName.”
  • Step 2 Identify MiniCorp Elements which do not exist in SchemaServer:

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Software Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Data Mining & Analysis (AREA)
  • Human Computer Interaction (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Devices For Executing Special Programs (AREA)

Abstract

L'invention concerne un modèle de schéma permettant à des objets d'être contextualisés au moyen de valeurs stockées utilisées pour localiser l'objet. Les valeurs utilisées pour localiser chaque objet devant être localisé, sont stockées dans un élément de type conteneur qui est associé à l'objet devant être localisé. L'objet comprenant des valeurs de termes localisées stockées dans un élément de type conteneur est relié à un autre objet; les objets étant reliés au moyen d'une relation hiérarchique de termes ou d'une relation d'entrée de termes. Les valeurs associées permettent à un utilisateur de se surclasser par des valeurs de redéfinition par défaut présentées par un système de vocabulaire commandé. L'utilisateur peut également relier des objets termes par l'intermédiaire de relations hiérarchiques, de relations d'entrée et de relations de termes associées. Ce mode de réalisation permet aux utilisateurs et aux systèmes de réutiliser plus efficacement les définitions de données normalisées.
PCT/US2003/040739 2002-12-18 2003-12-18 Modele de schema d'objet de serveur WO2004057464A2 (fr)

Priority Applications (3)

Application Number Priority Date Filing Date Title
EP03800035A EP1581865A2 (fr) 2002-12-18 2003-12-18 Modele de schema d'objet de serveur
CA002510835A CA2510835A1 (fr) 2002-12-18 2003-12-18 Modele de schema d'objet de serveur
AU2003299755A AU2003299755A1 (en) 2002-12-18 2003-12-18 Schema server object model

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US43453502P 2002-12-18 2002-12-18
US60/434,535 2002-12-18

Publications (2)

Publication Number Publication Date
WO2004057464A2 true WO2004057464A2 (fr) 2004-07-08
WO2004057464A3 WO2004057464A3 (fr) 2006-04-06

Family

ID=32682053

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2003/040739 WO2004057464A2 (fr) 2002-12-18 2003-12-18 Modele de schema d'objet de serveur

Country Status (5)

Country Link
US (2) US20040123234A1 (fr)
EP (1) EP1581865A2 (fr)
AU (1) AU2003299755A1 (fr)
CA (1) CA2510835A1 (fr)
WO (1) WO2004057464A2 (fr)

Cited By (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2013010595A1 (fr) * 2011-07-19 2013-01-24 Ovizio Imaging Systems N.V. Base de données orientée objet et procédé d'amélioration de base de données orientée objet
WO2013011104A1 (fr) * 2011-07-19 2013-01-24 Ovizio Imaging Systems N.V. Base de données d'objets et procédé d'amélioration de base de données d'objets
US9846151B2 (en) 2011-11-21 2017-12-19 Ovizio Imaging Systems NV/SA Sample vial for digital holographic analysis of a liquid cell sample
US9904248B2 (en) 2012-09-20 2018-02-27 Ovizio Imaging Systems NV/SA Digital holographic microscope with fluid systems
US10025271B2 (en) 2011-07-19 2018-07-17 Ovizio Imaging Systems NV/SA Method and system for detecting and/or classifying cancerous cells in a cell sample
US10578541B2 (en) 2012-02-13 2020-03-03 Ovizio Imaging Systems NV/SA Flow cytometer with digital holographic microscope
US11067379B2 (en) 2016-01-19 2021-07-20 Ovizio Imaging Systems NV/SA Digital holographic microscope with electro fluidic system, said electro-fluidic system and methods of use
US11308528B2 (en) * 2012-09-14 2022-04-19 Sdl Netherlands B.V. Blueprinting of multimedia assets
US11386186B2 (en) 2012-09-14 2022-07-12 Sdl Netherlands B.V. External content library connector systems and methods
US11694215B2 (en) 2011-01-29 2023-07-04 Sdl Netherlands B.V. Systems and methods for managing web content

Families Citing this family (55)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8166101B2 (en) 2003-08-21 2012-04-24 Microsoft Corporation Systems and methods for the implementation of a synchronization schemas for units of information manageable by a hardware/software interface system
US7590643B2 (en) 2003-08-21 2009-09-15 Microsoft Corporation Systems and methods for extensions and inheritance for units of information manageable by a hardware/software interface system
US7401104B2 (en) 2003-08-21 2008-07-15 Microsoft Corporation Systems and methods for synchronizing computer systems through an intermediary file system share or device
US8238696B2 (en) * 2003-08-21 2012-08-07 Microsoft Corporation Systems and methods for the implementation of a digital images schema for organizing units of information manageable by a hardware/software interface system
US20050171797A1 (en) * 2004-02-04 2005-08-04 Alcatel Intelligent access control and warning system for operations management personnel
US7316001B2 (en) 2004-06-05 2008-01-01 Graphlogic Inc. Object process graph system
US7493335B2 (en) * 2004-07-02 2009-02-17 Graphlogic Inc. Object process graph relational database interface
US7360209B2 (en) 2004-07-16 2008-04-15 Graphlogic Inc. Object process graph application controller-viewer
US7577649B2 (en) * 2004-07-23 2009-08-18 Sap Ag Engine for validating proposed changes to an electronic entity
US7593916B2 (en) * 2004-08-19 2009-09-22 Sap Ag Managing data administration
US20060047555A1 (en) * 2004-08-27 2006-03-02 Taiwan Semiconductor Manufacturing Company, Ltd. Method and system for re-authorizing workflow objects
US7536676B2 (en) 2004-09-10 2009-05-19 Newalliance Bank Object process graph application controller-viewer
US20060136361A1 (en) * 2004-12-22 2006-06-22 Microsoft Corporation Extensible, customizable database-driven row-level database security
US7979405B2 (en) * 2005-01-14 2011-07-12 Microsoft Corporation Method for automatically associating data with a document based on a prescribed type of the document
US7966286B2 (en) * 2005-02-14 2011-06-21 Microsoft Corporation Hierarchical management of object schema and behavior
US20060184867A1 (en) * 2005-02-17 2006-08-17 Avraham Shpigel Method for reusing definitions in documents and monitoring thereof
US20060242183A1 (en) * 2005-04-25 2006-10-26 Microsoft Corporation Declaratively extended hierarchical configuration system and method
US7653630B2 (en) * 2005-08-24 2010-01-26 Oracle International Corporation Method and apparatus for facilitating privileged object stores in a database
US7818662B2 (en) * 2005-11-04 2010-10-19 Microsoft Corporation Integrating line-of-business application data with documents
US7606813B1 (en) * 2006-09-27 2009-10-20 Emc Corporation Model consolidation in a database schema
US20080091690A1 (en) * 2006-10-13 2008-04-17 International Business Machines Corporation Deriving a Data Model From a Hierarchy Of Related Terms, And Deriving a Hierarchy Of Related Terms From a Data Model
US7725499B1 (en) * 2007-02-01 2010-05-25 Star Ag Semantic architecture for managing information through structured storage and retrieval
US9792563B1 (en) * 2007-03-22 2017-10-17 Workday, Inc. Human resources system development
US7668860B2 (en) * 2007-04-02 2010-02-23 Business Objects Software Ltd. Apparatus and method for constructing and using a semantic abstraction for querying hierarchical data
US9449276B2 (en) * 2007-08-15 2016-09-20 Ca, Inc. Graphical model-driven system for knowledge management tools
US20090055242A1 (en) * 2007-08-24 2009-02-26 Gaurav Rewari Content identification and classification apparatus, systems, and methods
US20090055368A1 (en) * 2007-08-24 2009-02-26 Gaurav Rewari Content classification and extraction apparatus, systems, and methods
US8307008B2 (en) * 2007-10-31 2012-11-06 Microsoft Corporation Creation and management of electronic files for localization project
US20090144241A1 (en) * 2007-12-03 2009-06-04 Chartsource, Inc., A Delaware Corporation Search term parser for searching research data
US8347266B2 (en) * 2007-12-10 2013-01-01 Microsoft Corporation Declarative object identity
US8719693B2 (en) * 2008-02-22 2014-05-06 International Business Machines Corporation Method for storing localized XML document values
US8819564B1 (en) * 2008-02-22 2014-08-26 Google Inc. Distributed discussion collaboration
US8091082B2 (en) * 2008-03-12 2012-01-03 DGN Technologies, Inc. Systems and methods for risk analysis and updating of software
US9317274B2 (en) * 2008-08-06 2016-04-19 Lenovo (Singapore) Pte. Ltd. Apparatus, system and method for integrated customization of multiple disk images independent of operating system type, version or state
US8711148B2 (en) 2008-10-01 2014-04-29 International Business Machines Corporation Method and system for generating and displaying an interactive dynamic selective view of multiply connected objects
US8711147B2 (en) 2008-10-01 2014-04-29 International Business Machines Corporation Method and system for generating and displaying an interactive dynamic graph view of multiply connected objects
US8665274B2 (en) * 2008-10-01 2014-03-04 International Business Machines Corporation Method and system for generating and displaying an interactive dynamic view of bi-directional impact analysis results for multiply connected objects
US8194075B2 (en) * 2008-10-01 2012-06-05 International Business Machines Corporation Method and system for generating and displaying an interactive dynamic list view of multiply connected objects
US8669982B2 (en) * 2008-10-01 2014-03-11 International Business Machines Corporation Method and system for generating and displaying an interactive dynamic culling graph view of multiply connected objects
US8447120B2 (en) * 2008-10-04 2013-05-21 Microsoft Corporation Incremental feature indexing for scalable location recognition
US20100185652A1 (en) * 2009-01-16 2010-07-22 International Business Machines Corporation Multi-Dimensional Resource Fallback
US9069848B2 (en) * 2009-09-29 2015-06-30 International Business Machines Corporation Automatic taxonomy enrichment
US20110145005A1 (en) * 2009-12-10 2011-06-16 Wu Cao Method and system for automatic business content discovery
US9595013B2 (en) * 2009-12-10 2017-03-14 Equinix, Inc. Delegated and restricted asset-based permissions management for co-location facilities
US9811835B2 (en) * 2010-06-18 2017-11-07 Microsoft Technology Licensing, Llc Metadata-enabled dynamic updates of online advertisements
US9946988B2 (en) * 2011-09-28 2018-04-17 International Business Machines Corporation Management and notification of object model changes
US8429197B1 (en) * 2012-02-28 2013-04-23 Symantec Corporation Systems and methods for maintaining group membership records
US9262511B2 (en) * 2012-07-30 2016-02-16 Red Lambda, Inc. System and method for indexing streams containing unstructured text data
US20140100909A1 (en) * 2012-10-03 2014-04-10 Infosys Limited System and method for testing and validation
US9830142B2 (en) * 2013-09-13 2017-11-28 Microsoft Technology Licensing, Llc Automatic installation of selected updates in multiple environments
US9665359B2 (en) 2013-09-13 2017-05-30 Microsoft Technology Licensing, Llc Automatically resolving conflicts after installation of selected updates in a computer system
US20150331875A1 (en) * 2014-05-16 2015-11-19 Syntel, Inc. System and method for validating integrated data recasting objects
US11210457B2 (en) 2014-08-14 2021-12-28 International Business Machines Corporation Process-level metadata inference and mapping from document annotations
US11700221B2 (en) * 2018-05-17 2023-07-11 Honeywell International Inc. Rule-based annotation service in a cloud platform
US20220107923A1 (en) * 2020-10-06 2022-04-07 Servicenow, Inc. Taxonomy Normalization for Applications of a Remote Network Management Platform

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6052525A (en) * 1997-08-14 2000-04-18 International Business Machines Corporation Method of error handling in a framework

Family Cites Families (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6571279B1 (en) * 1997-12-05 2003-05-27 Pinpoint Incorporated Location enhanced information delivery system
US5970490A (en) * 1996-11-05 1999-10-19 Xerox Corporation Integration platform for heterogeneous databases
US6513152B1 (en) * 1997-07-23 2003-01-28 International Business Machines Corporation Object oriented framework mechanism for customization of object oriented frameworks
US6134559A (en) * 1998-04-27 2000-10-17 Oracle Corporation Uniform object model having methods and additional features for integrating objects defined by different foreign object type systems into a single type system
US6381743B1 (en) * 1999-03-31 2002-04-30 Unisys Corp. Method and system for generating a hierarchial document type definition for data interchange among software tools
US6199195B1 (en) * 1999-07-08 2001-03-06 Science Application International Corporation Automatically generated objects within extensible object frameworks and links to enterprise resources
US6418448B1 (en) * 1999-12-06 2002-07-09 Shyam Sundar Sarkar Method and apparatus for processing markup language specifications for data and metadata used inside multiple related internet documents to navigate, query and manipulate information from a plurality of object relational databases over the web
US20040220791A1 (en) * 2000-01-03 2004-11-04 Interactual Technologies, Inc. A California Corpor Personalization services for entities from multiple sources
US6999963B1 (en) * 2000-05-03 2006-02-14 Microsoft Corporation Methods, apparatus, and data structures for annotating a database design schema and/or indexing annotations
US20020049738A1 (en) * 2000-08-03 2002-04-25 Epstein Bruce A. Information collaboration and reliability assessment
US7496534B2 (en) * 2001-03-08 2009-02-24 Olsen Richard B Methods for trade decision making

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6052525A (en) * 1997-08-14 2000-04-18 International Business Machines Corporation Method of error handling in a framework

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
BOCK G: "SchemaServer 2.0 from SchemaLogic" INTERNET ARTICLE, [Online] 25 July 2002 (2002-07-25), XP002363555 Retrieved from the Internet: URL:http://www.ischool.washington.edu/boiko/PastClasses/lis580fa02/readings/PSGroupOnSchemaLogicPublished.pdf> [retrieved on 2005-01-19] *

Cited By (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11694215B2 (en) 2011-01-29 2023-07-04 Sdl Netherlands B.V. Systems and methods for managing web content
WO2013010595A1 (fr) * 2011-07-19 2013-01-24 Ovizio Imaging Systems N.V. Base de données orientée objet et procédé d'amélioration de base de données orientée objet
WO2013011104A1 (fr) * 2011-07-19 2013-01-24 Ovizio Imaging Systems N.V. Base de données d'objets et procédé d'amélioration de base de données d'objets
US10025271B2 (en) 2011-07-19 2018-07-17 Ovizio Imaging Systems NV/SA Method and system for detecting and/or classifying cancerous cells in a cell sample
US9846151B2 (en) 2011-11-21 2017-12-19 Ovizio Imaging Systems NV/SA Sample vial for digital holographic analysis of a liquid cell sample
US10060905B2 (en) 2011-11-21 2018-08-28 Ovizio Imaging Systems NV/SA Liquid medium and sample vial for use in a method for detecting cancerous cells in a cell sample
US10578541B2 (en) 2012-02-13 2020-03-03 Ovizio Imaging Systems NV/SA Flow cytometer with digital holographic microscope
US11308528B2 (en) * 2012-09-14 2022-04-19 Sdl Netherlands B.V. Blueprinting of multimedia assets
US20220138808A1 (en) * 2012-09-14 2022-05-05 Sdl Netherlands B.V. Blueprinting of Multimedia Assets
US11386186B2 (en) 2012-09-14 2022-07-12 Sdl Netherlands B.V. External content library connector systems and methods
US9904248B2 (en) 2012-09-20 2018-02-27 Ovizio Imaging Systems NV/SA Digital holographic microscope with fluid systems
US11067379B2 (en) 2016-01-19 2021-07-20 Ovizio Imaging Systems NV/SA Digital holographic microscope with electro fluidic system, said electro-fluidic system and methods of use

Also Published As

Publication number Publication date
EP1581865A2 (fr) 2005-10-05
US20040123234A1 (en) 2004-06-24
CA2510835A1 (fr) 2004-07-08
WO2004057464A3 (fr) 2006-04-06
US20040181544A1 (en) 2004-09-16
AU2003299755A1 (en) 2004-07-14

Similar Documents

Publication Publication Date Title
WO2004057464A2 (fr) Modele de schema d'objet de serveur
RU2421798C2 (ru) Модель данных для объектно-реляционных данных
US9594778B1 (en) Dynamic content systems and methods
US7673282B2 (en) Enterprise information unification
KR101117945B1 (ko) 분산형 컴퓨팅 시스템을 위한 아키텍쳐 및 분산형 애플리케이션의 자동화된 설계, 배치 및 관리
US7953734B2 (en) System and method for providing SPI extensions for content management system
KR101026606B1 (ko) 시스템용 통합 설계, 배치 및 관리방법, 장치, 시스템 및 컴퓨터 판독가능 기록매체
US7533124B2 (en) Method and system for collaborative ontology modeling
US20040093559A1 (en) Web client for viewing and interrogating enterprise data semantically
MXPA06001984A (es) Sistemas y metodos para conectar con una interfase programas de aplicacion una plataforma de almacenamiento basada en elementos.
WO2005015441A2 (fr) Meta-donnees dynamiques
JP2004280820A (ja) ビジネスソフトウェアアプリケーションをサポートするフレームワーク
Trujillo et al. An engineering process for developing Secure Data Warehouses
Oltmans et al. Preservation functionality in a digital archive
TWI337310B (en) Systems and methods for extensions and inheritance for units of information manageable by a hardware/software interface system
Nebert et al. OGC® Catalogue Services 3.0-General Model, Version 3.0.
JPH03196364A (ja) 探索項構築の制御テーブルの導入方法
Smith Automated validation of trusted digital repository assessment criteria
Heery et al. Metadata schema registries in the partially Semantic Web: the CORES experience
EP1274018A2 (fr) Browser d'instances pour ontologie
Zhu et al. Federated Content Management: Accessing Content from Disparate Repositories with IBM Content Federation Services and IBM Content Integrator
Moore et al. Assessment of RLG trusted digital repository requirements
Chikwanda et al. Call center management systems
Kumar Documentum 6.5 Content Management Foundations
Zhu et al. IBM FileNet P8 Platform and architecture

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A2

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

AL Designated countries for regional patents

Kind code of ref document: A2

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

121 Ep: the epo has been informed by wipo that ep was designated in this application
WWE Wipo information: entry into national phase

Ref document number: 2510835

Country of ref document: CA

WWE Wipo information: entry into national phase

Ref document number: 2003299755

Country of ref document: AU

WWE Wipo information: entry into national phase

Ref document number: 2003800035

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 788/MUMNP/2005

Country of ref document: IN

WWP Wipo information: published in national office

Ref document number: 2003800035

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: JP

WWW Wipo information: withdrawn in national office

Ref document number: JP