WO2001055891A2 - Method of retrieving schemas for interpreting documents in an electronic commerce system - Google Patents
Method of retrieving schemas for interpreting documents in an electronic commerce system Download PDFInfo
- Publication number
- WO2001055891A2 WO2001055891A2 PCT/US2001/002665 US0102665W WO0155891A2 WO 2001055891 A2 WO2001055891 A2 WO 2001055891A2 US 0102665 W US0102665 W US 0102665W WO 0155891 A2 WO0155891 A2 WO 0155891A2
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- schema
- document
- directory
- location
- ldap
- Prior art date
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/02—Banking, e.g. interest calculation or account maintenance
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S707/00—Data processing: database and file management or data structures
- Y10S707/99931—Database or file accessing
- Y10S707/99932—Access augmentation or optimizing
Definitions
- This invention relates to the exchange of electronic documents in an electronic marketplace.
- the invention relates to methods for retrieving schemas which are used to interpret electronic documents used in business to business transactions.
- EDI refers to a set of messages used for business-to-business communication. The messages are compiled into business documents, which are exchanged to facilitate transactions between trading partners. Each organization using EDI typically stores its data in a private format.
- trading partners employing EDI are typically required to contract in advance and develop software programs to map between their private data sets.
- a new translation program is required to format their data in conformance with the other trading partners on the list.
- the EDI approach for supporting a commercial communications standard is to include the union of all universally required features into a global standard.
- EDI effectively includes a messaging standard for each transaction conducted between each set of trading partners.
- the inefficiencies which result from this system include the effort spent in generating a translator for every pair of trading partners and the redundancy inherent in generating original documents to facilitate largely similar transactions.
- This standard should allow document types to evolve in order to facilitate new transactions, while preserving the integrity of the existing document types and the transactions they support. Because the library of document types which are used in such a standard will be shared by all trading partners in the marketplace, these resources should be available throughout the marketplace.
- the invention enables the creation of an electronic marketplace by facilitating the exchange of electronic documents between trading partners.
- Embodiments of the invention include communications standards for the electronic documents which enable trading partners to (1) construct documents which reflect the particular constraints of their transactions and (2) make such documents easily available throughout the marketplace.
- the communications standards employed in this invention optimize the efficiency of the creation and retrieval of the electronic documents, and, as such, the efficiency of the respective transactions.
- commercial transactions between trading partners are conducted via a computer network referred to as a transaction services network.
- the transaction services network is operated by a market maker interested in supporting an electronic marketplace, and the network provides services which facilitate the commercial transactions.
- the transactions are conducted by the exchange of electronic documents between trading partners.
- the transaction services network provides services for facilitating these transactions, such as matching trading partners to conduct certain types of transactions; routing documents between trading partners; providing information about trading partners; and establishing protocols to govern the transactions.
- the trading partners access the transaction services network via private servers which connect to the transaction services network via the Internet.
- the documents supporting the transactions are written in an enhanced form of the Extensible Markup Language, XML.
- XML Extensible Markup Language
- the XML standard is a markup language which allows document writers to define the tags which are used to express document instances.
- the ability to define the tags which are used in a document provides document writers with the facility to convey the semantic content of document instances by use of the tags embedded within the document instances, a feature which is unavailable in earlier generations of markup languages.
- XML document instances are interpreted by the use of schemas which are cited in the document instances; the schemas define a collection of tags which are used to encode the document instances. As a schema may be used to interpret multiple document instances, the schema classifies a document type.
- the document types which are available in the invention support commercial transactions such as purchase orders, purchase order acknowledgements, order status checks, availability checks, price checks, invoices, and invoice acknowledgements.
- XML allows document writers to create schemas as necessary to support novel transactions.
- Embodiments of the invention also support polymorphic XML documents.
- Polymorphism allows a document type to be explicitly defined as an extension of a pre-existing document type. Any document instance of the extending document type will also be a legal instance of the extended document type. As such, polymorphism allows the creation of an extension hierarchy of document types.
- the document instances contain identifiers for the schemas they cite. These identifiers are persistent and location independent. As such, the identifiers enable schemas to be identified irrespective of changes in the configuration of the underlying computer system.
- the location identifiers are Uniform Resource Names (URNs).
- URNs for schemas are resolved to location-specific Uniform Resource Identifiers, or URIs, which indicate the physical locations for the schemas. These physical locations may include HTTP sites, FTP sites, or file locations.
- URNs are resolved to location-specific URIs by the use of a registry which maps URNs to the corresponding location specific URIs.
- the Lightweight Directory Access Protocol, version 3 (LDAP v3) is used to search the registry for the location- specific URI. This protocol provides an efficient tool for searching the registry.
- the URN registry is stored in an LDAP v3 compliant directory server.
- the LDAP compliant directory server may be an x.500 server.
- the URN is converted to an LDAP URL.
- the LDAP URL is used as a key to search the LDAP directory for the location- specific URI.
- the directory server is accessible to any trading partner server or other server on the network which interprets XML documents.
- the use of a central directory server eliminates the need for replicated repositories, thereby lending scalability and consistency to the URN registry.
- the registry may be federated, so that different nodes of the directory reside on separate servers, thereby allowing control over particular URNs to be vested with the parties responsible for the resources identified by the URNs.
- Figure 1 is a schematic depiction of the network layout of the electronic marketplace in an embodiment of the invention.
- Figure 2 illustrates the use of URNs for dynamically linking XML schemas and document instances in an embodiment of the invention.
- Figure 3 illustrates the applications responsible for parsing XML documents in an embodiment of the invention.
- Figure 4 illustrates an LDAP directory tree used to resolve URNs in an embodiment of the invention.
- the invention addresses problems faced in the construction of an electronic marketplace for business to business transactions.
- the electronic marketplace considered by the invention includes a computer network system which facilitates transactions between trading partners; these transactions are conducted by the exchange of electronic documents which correspond to the particular transactions. For example, a purchase order from a seller to a buyer may be conducted by exchanging a PurchaseOrder document between the trading partners which specifies the terms of the transaction.
- the types of commercial transactions supported by the invention can include, but are not limited to, purchase orders, purchase order acknowledgments, order status checks, availability checks, price checks, invoices, invoice acknowledgement, and/or catalog documents.
- Various services are required to facilitate such business to business electronic transactions. For instance, buyers and sellers may be matched to conduct certain types of transactions; documents are routed between trading partners; information about trading partners should be readily available; and protocols should be established to govern the transactions.
- a market system which facilitates commercial transactions should be scalable, as a system flexible enough to support a multitude of transactions should allow for trading partners to be continuously added to the marketplace.
- these services are provided by a network of computers illustrated in figure 1.
- the network providing the services 100 is referred to as a transaction services network 100; the transaction services network is typically operated by a "market maker", i.e., a body which is interested in facilitating an electronic marketplace.
- Buyer sites 102 and seller sites 104 connect to the transaction services network 100 via the Internet.
- the network includes a group of transaction servers 108 which provide various commercial services. Transaction servers 108 may be added to the network as necessary, thereby lending scalability to the transaction services network 100.
- Previous attempts at establishing electronic marketplaces have lacked an adequate standard for communication between trading partners. This deficiency results in the generation of redundant documents, and fails to provide efficient tools for constructing new transactions from old documents. As such, it would be desirable to enforce a communications standards within the marketplace which expedites the modification of existing documents and eliminates redundancy in the collection of documents, while retaining the flexibility to accommodate novel transactions.
- the standard should be flexible and expressive enough to encode any possible transaction between trading partners.
- the standard should also enable the efficient creation of new transactions from old transactions, and thereby eliminate the need to create and interpret redundant messages in the electronic marketplace.
- the transactions are encoded in documents written in markup languages. These documents are exchanged between trading partners to facilitate transactions in the marketplace.
- Documents written in a markup language are interpreted by the use of embedded tags; examples of such languages include HTML and SGML.
- the markup language used to write the electronic documents is an enhanced version of XML.
- Standard XML is a markup language which allows a document writer to define the set of tags which are used to interpret a given document "instance”.
- the collection of tags are defined in a file referred to as a "schema”, and every instance of an XML document is interpreted by reference to the schemas cited by the instance. Because a schema defines a collection of tags which may be used to interpret multiple document instances, a schema is said to define a "document type”.
- an instance of a document type comprises an XML document which cites the respective schema.
- schemas are defined in Document Type Definition files, or DTDs.
- a DTD corresponding to a document type may be external or internal to instances of that document type.
- XML document instances are validated at two levels: each document is checked for (1) conformance to XML syntax and (2) conformance with referenced schemas. The distinction between these levels of conformity can be illustrated by example.
- a specific purchase order document instance of the document type PurchaseOrder Suppose we have a document type PurchaseOrder and an instance of PurchaseOrder that we call PO_Instance. POJnstance would be a specific purchase order sent through the marketplace. If EO ' Instance conforms to a set of general syntactical criteria specified by standard XML we say that POJnstance is "well-formed.” If, in addition,
- POJnstance is correct with respect to PurchaseOrder we say that POJnstance is "valid" with respect to PurchaseOrder.
- Validity is a stricter requirement than well-formedness, as a document instance can be well-formed even though it is not valid with respect to its document type.
- the XML document instances are parsed in an XML Processor.
- the XML Processor is an application which is responsible for understanding well-formed XML syntax and for validating XML documents.
- each transaction server and each trading partner site may have an XML Processor, which allows each server to understand the documents exchanged within the marketplace.
- Standard XML alone, however, is not entirely adequate to facilitate the electronic marketplace.
- standard XML as an e- commerce protocol is that the language does not provide adequate means for checking integrity constraints on data.
- conventional XML does not support polymorphic changes to schemas. As such, schemas must be entirely rewritten to accommodate minor changes to conventional transactions which have pre-existing schemas. The absence of polymorphism results in duplicated effort to create largely redundant schemas. This deficiency can be illustrated by example. Consider a transaction such as a purchase order. Each individual seller in the marketplace is likely to have constraints on purchase orders which are unique to its business, and which should be reflected in any purchase order which it communicates to a buyer.
- the standard XML schemas are extended with enhanced schema languages which support polymorphism and integrity constraints in XML Documents.
- enhanced schema languages which support polymorphism and integrity constraints in XML Documents.
- XML schema languages include Commerce One's SOX language and Microsoft's XDR standard.
- Polymorphism allows a document type to be explicitly defined as an extension of a pre-existing document type. Any document instance of the extending document type will also be a legal instance of the extended document type. As such, polymorphism allows the creation of an extension hierarchy of document types. The extensions mechanism in a schema language should guarantee that document instances will always adhere to criteria that ensure the safe evolution of document types.
- the utility of polymorphic schemas in the electronic marketplace can be illustrated with an example depicted in Figure 2. Note that while the schema language employed in this illustration is the SOX language, the example is equally valid for any enhanced schema language supporting polymorphism in XML. Assume that a group of trading partners have agreed on a schema for the document type PurchaseOrder. The schema corresponding to the document type is the PurchaseOrder.
- sox 200 schema ReferenceOrder. sox 200 references tags from a preexisting library of SOX components in a file called CBL.sox 216; the acronym CBL stands for "Common Business Library.”
- the PurchaseOrder. sox schema 200 includes an identifier 202 for CBL.sox 216.
- CBL.sox 216 includes a tag ⁇ Address> for supporting addresses.
- ⁇ Address> tag has as sub-elements: ⁇ Name> ⁇ Street> ⁇ City> ⁇ PostaICode>
- ⁇ Address> is utilized by document instances of type PurchaseOrder and that a particular trading partner ACME wishes to make a simple extension to the ⁇ Address> element used in PurchaseOrder. sox 200.
- ACME wishes to extend the PurchaseOrder. sox 200 schema to allow the ⁇ Address> element to contain telephone numbers.
- the ⁇ Address> tag may be extended by using the SOX schema language to create a small document type Contact Address, whose corresponding schema ContactAddress.sox 204 extends the CBL.sox 216 definition of ⁇ Address> to include a telephone number.
- the new document type includes an identifier 206 for CBL.sox 216.
- a document instance 208 of type PurchaseOrder incorporates the new ⁇ Address> tag by import statements which reference the schemas ContactAddress.sox 204 and CBL.sox 216 respectively.
- the benefits of polymorphism are apparent from this example: we have changed the ⁇ Address> tag in a new, short document type, while preserving the integrity of the original PurchaseOrder document type. Without support for polymorphism, the new ⁇ Address> tag would require a rewrite of the PurchaseOrder. This would alter a fundamental document type which is an agreed upon standard amongst trading partners, one upon which a number of document instances and transactions are constructed, in order to accommodate a minor change.
- the schemas should have the following characteristics: • The schemas must be available in a generally available repository to enable trading partners to retrieve them dynamically.
- the schema identifiers 202 206 210 212 214 should have globally unique names, aiding their dynamic discovery and loading • When a trading partner receives a document instance, the
- the enhanced schema languages introduce new challenges to the implementation of a document exchange system.
- One of these challenges arises from the fact that the schemas in such languages evolve.
- documents which are written prior to schema modifications should be able link at the time they are parsed to the modified schema.
- the link to the schema in the document instance, which was written prior to the schema change should remain valid.
- polymorphism entails a need for permanent, location independent identifiers for schemas.
- XML entities it is also desirable for XML entities to exhibit modularity, i.e., to allow XML entities to be re-used.
- XML document schema which is well-understood, and which defines tags that may be used in multiple document instances. If such a schema is available, it is desirable to re-use this schema in the multiple instances, rather than re- write it for each instance.
- a schema In order to be used by multiple document instances, it is desirable for a schema to have a universal name, which may be used by any of the document instances. This name should also be persistent, so that document instances referring to the schema remain valid indefinitely. Additionally, it is desirable for such names to be location-independent, so that references to the schemas remain valid even if the schema locations change. Thus the modularity of XML code also suggests a need for persistent, location-independent identifiers for XML entities. F. Identifying Schemas with URNs
- schemas are identified by persistent, location independent names.
- these identifiers include Uniform Resource Names, or URNs.
- Uniform Resource Names are described in RFC 2079.
- URNs are names for resources which may reside on LANs, WANs, or on the Internet. These names are characterized by two signal features:
- URNs are persistent. As explained in RFC 2141, URNs are designed to last indefinitely, irrespective of changes in the configuration of the computer system on which the resources identified by URNs reside. This is in stark contrast to network addresses, IP addresses, or file locations, all of which identify physical locations on a network, and are invalid if the physical locations change.
- URNs are location independent. This also contrasts with network addresses and file locations. A system resource identified by a URN will retain that URN even if its network location changes, which does not hold true for its IP address, LAN address, or file location.
- each schema is identified with a URN. This is illustrated in figure 2.
- the document instance 208 of type PurchaseOrder identifies the schemas PurchaseOrder. sox 200, ContactAddress.sox 204, and CBL.sox 216, by their respective URN identifiers 210, 212, 214.
- ContactAddress.sox 204 identify CBL.sox 216 by its URN identifiers 202 206.
- URNs The syntax of URNs is specified in RFC 2141. They are specified in the following format:
- NID is x-commerceone and the NSS is document:com:commerceone:marketsite:businessservices:P O.sox$1.0
- embodiments of the invention also include a method for resolving URNs to physical locations.
- URNs are mapped to physical locations by converting the URNs to location-specific URIs, or Uniform Resource Identifiers.
- Uniform Resource Identifiers which are described in RFC 2396, may identify physical locations for computer system resources.
- location-specificURIs may take the form of network locations such as HTTP, FTP, or Telnet sites, or file locations within a computer system.
- the present embodiment maps URNs to location-specific URIs, and correspondingly maps permanent, location independent identifiers to actual physical locations.
- mapping should be scalable, in order to facilitate the addition of new schemas and document types to the marketplace, and should allow for easy retrieval and updating, as the network locations of the schemas may change frequently.
- mapping method should enable each server in the marketplace with an XML Processor 302, i.e., buyer sites 102, seller sites 104, transaction servers 108, to access the schemas, and interpret documents.
- XML Processor 302 i.e., buyer sites 102, seller sites 104, transaction servers 108
- the method of URN resolution should also be accessible to each server in the marketplace.
- Embodiments of the invention address these issues by employing a registry for mapping URNs to location-specific URIs.
- the registry resides on a directory service which is accessible by any site in the electronic marketplace, i.e., by any of the trading partner sites or any of the transaction servers within the transaction services network.
- Figure 1 depicts this feature of the electronic marketplace.
- the buyer sites 102, seller sites 104, and the transaction servers 108 all communicate with the URN registry in the Directory Server 1 10. This layout lends scalability to the system, as any transaction servers or trading partner servers may also communicate with the registry.
- An access protocol is needed to retrieve the schema name from the x.500 directory.
- An embodiment of the invention utilizes the Lightweight Directory Access Protocol, or LDAP.
- LDAP v3 protocol is a client-server protocol for performing lookups on a remote directory server.
- the protocol is used to enable the transaction servers and trading partners to retrieve resource locations via the registry.
- Figure 3 depicts the use of LDAP to retrieve schema locations from a directory.
- An Entity Manager 304 receives an XML document instance 300.
- the entity manager is an application which may run on any transaction server or trading partner site: the application manages XML document streams and facilitates the opening and tracking of URI based resources which the XML document system requires or references. The information collected by the
- Entity Manager 304 is passed to an XML Processor 302, which is responsible for understanding well-formed XML syntax. Upon parsing the XML document instance 300, the XML Processor 302 sends a URN for the schema to the Entity Manager 304. The Entity Manager 304 engages an LDAP Lookup Service 306 which searches for a location-specific URI corresponding to the URN in a directory service 308.
- the LDAP compliant directory service 308 used to resolve the URNs comprises an X.500 server.
- the directory service 308 may be any other type of directory service which has functionality similar to LDAP v3.
- the X.500 directory server is described in detail in RFC 2253.
- the directory service stores primary keys as "Distinguished Names", which are commonly referred to as "DN"s.
- a DN is composed of a string of attribute values.
- the types of attributes include: CN Common Name OU Organization Unit Name O Organization Name
- a DN comprises a string of one or more attribute values for the attribute types listed above.
- the attribute types are organized in a tree-based hierarchy, which facilitates the search and retrieval of distinguished names.
- the DN serves as the primary key for retrieving a corresponding location-specific URI from the x.500 directory.
- the URN for that schema Prior to using the DN as a key for retrieving a corresponding location- specific URI for a schema, the URN for that schema should be mapped to the DN. This step is performed by use of an LDAP URL.
- the LDAP URL standard is described in RFC 2255. This standard specifies a syntax for converting URNs to Distinguished Names.
- the Entity Manager 304 is responsible for converting the URN to an LDAP URL.
- the Distinguished Names are then available to the LDAP protocol to search LDAP compliant directories.
- the search through the directory is performed by the LDAP Lookup Service 306.
- the schema retrieval procedure outlined above comprises the following steps:
- a PurchaseOrder. sox 200 schema is to be retrieved by an XML Processor 302.
- the URN for PurchaseOrder. sox 200 is specified as : urn::x- commerceone:document:com:commerceone:marketsite:businessservices:PO.sox$l.
- NI x-commerceone
- NSS document:com:commerceone:marketsite:businessservices:PO.sox$1.0
- the Namespace Identifier, or NI for all schemas is "x-commerceone.”
- the Namespace Specific String, or NSS is divided into two parts, one representing the "logical directory” and the other portion representing the version of the document. These two portions of the NSS are delimited by the "$" token.
- the logical directory is given by document:com:commerceone:marketsite:businessservices:PO.sox and the version is given as
- the logical directory is a hierarchical name for the document which is delimited by colons ":". This hierarchy corresponds to the hierarchy in the LDAP directory relative to a Schema Root in reverse order.
- the next step is to convert the URN as specified above into a corresponding LDAP URL.
- the format for a standard LDAP URL, as specified is RFC 2255, is given as follows:
- Figure 4 is an illustration of the directory tree.
- the nodes of the tree correspond to attributes in the DN, and the leaves contain URIs for various schemas.
- the LDAP Lookup Service uses the third "/" as an indication of the host and port, which brings it to the Schema Root Node 400.
- the DN is now traversed in reverse order.
- the path 406 can be seen to correspond directly to the DN specified in the LDAP URL, wherein each attribute "ou” has a corresponding node in the path 406.
- the schema retrieval system described in this example meets the criteria which were established earlier, such as persistence and location-independence, and exhibits a number of virtues which may not be immediately apparent.
- the persistence and location independence of the URN is achieved by the provision of a centralized URN Repository which is easily updated.
- the registry in an embodiment of the invention, is an x.500 directory, with a directory tree as given in Figure 4.
- a physical location for a given resource can be updated simply by updating the corresponding leaf node. For instance, suppose the location of the Purchase Order schema in the example above is changed to http://www.marketsite.net/foo. This can be facilitated simply by replacing the current contents of the leaf node 408 with the new URL. Hence the corresponding URN is persistent, for the URN remains constant even though the old URL is obsolete.
- the URN is also location independent, as the physical location of the resource is at a new network location while the URN has remained constant. Thus, any documents referring to the schema by the URN remain valid under the location change. Maintaining a centralized URN Repository lends scalability, integrity, and flexibility to the schema retrieval system. The provision of a centralized repository eliminates a need for replicated lists of schema locations. This frees memory in the system for other uses. The centralized repository also contributes to the scalability of the system, as any new server added to the system can access schemas simply by accessing the URN Repository.
- An alternative embodiment for the repository includes a federated directory service, in which the individual nodes of the directory service reside on separate servers.
- schemas unique to particular trading partners are stored on sites which are operated by the trading partners. For instance, a particular buyer may modify a PurchaseOrder schema to suit their requirements.
- those nodes of the LDAP tree which lead to a leaf with the URI for the modified PurchaseOrder reside on sites under the control of the buyer.
- This embodiment enables the buyer site to update nodes leading to a particular schema location itself, without going through a central directory service. As such, this embodiment decentralizes the process of updating the Directory Service, while preserving the integrity of the directory and eliminating the need for replicated URN repositories.
Abstract
Description
Claims
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2001555367A JP2003530627A (en) | 2000-01-28 | 2001-01-26 | Method of searching schema for interpreting document in e-commerce system |
EP01903359A EP1250657A2 (en) | 2000-01-28 | 2001-01-26 | Method of retrieving schemas for interpreting documents in an electronic commerce system |
AU2001231187A AU2001231187A1 (en) | 2000-01-28 | 2001-01-26 | Method of retrieving schemas for interpreting documents in an electronic commerce system |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US09/493,954 US6591260B1 (en) | 2000-01-28 | 2000-01-28 | Method of retrieving schemas for interpreting documents in an electronic commerce system |
US09/493,954 | 2000-01-28 |
Publications (2)
Publication Number | Publication Date |
---|---|
WO2001055891A2 true WO2001055891A2 (en) | 2001-08-02 |
WO2001055891A8 WO2001055891A8 (en) | 2002-06-27 |
Family
ID=23962399
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US2001/002665 WO2001055891A2 (en) | 2000-01-28 | 2001-01-26 | Method of retrieving schemas for interpreting documents in an electronic commerce system |
Country Status (5)
Country | Link |
---|---|
US (1) | US6591260B1 (en) |
EP (1) | EP1250657A2 (en) |
JP (1) | JP2003530627A (en) |
AU (1) | AU2001231187A1 (en) |
WO (1) | WO2001055891A2 (en) |
Cited By (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP1296252A1 (en) * | 2001-09-21 | 2003-03-26 | Koninklijke KPN N.V. | A method, computer system, communication network, computer program and data carrier for filtering data |
EP1817735A2 (en) * | 2004-10-19 | 2007-08-15 | Apollo Enterprise Solutions, LLC | System and method for resolving transactions |
US7711676B2 (en) | 2004-11-12 | 2010-05-04 | Sap Aktiengesellschaft | Tracking usage of data elements in electronic business communications |
US7818342B2 (en) | 2004-11-12 | 2010-10-19 | Sap Ag | Tracking usage of data elements in electronic business communications |
US8151003B2 (en) | 2002-02-05 | 2012-04-03 | International Business Machines Corporation | System and method for routing data by a server |
US8660941B2 (en) | 2006-09-26 | 2014-02-25 | Collections Marketing Center, Inc. | Method and system for providing a multi-channel virtual collections center |
US9659326B2 (en) | 1999-03-12 | 2017-05-23 | Collections Marketing Center, Inc. | System and method for debt presentment and resolution |
Families Citing this family (229)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7594167B1 (en) * | 1998-10-16 | 2009-09-22 | Open Invention Network, Llc | System and method for schema evolution in an e-commerce network |
US6125391A (en) * | 1998-10-16 | 2000-09-26 | Commerce One, Inc. | Market makers using documents for commerce in trading partner networks |
US7131069B1 (en) * | 1998-10-22 | 2006-10-31 | Made2 Manage Systems, Inc. | Navigational interface for ERP system |
US7451106B1 (en) * | 1998-11-30 | 2008-11-11 | E-Lynxx Corporation | System and method for competitive pricing and procurement of customized goods and services |
US7062456B1 (en) | 1999-02-09 | 2006-06-13 | The Chase Manhattan Bank | System and method for back office processing of banking transactions using electronic files |
US8044793B2 (en) | 2001-03-01 | 2011-10-25 | Fisher-Rosemount Systems, Inc. | Integrated device alerts in a process control system |
US7451107B1 (en) * | 2000-01-28 | 2008-11-11 | Supply Chain Connect, Llc | Business-to-business electronic commerce clearinghouse |
US7031956B1 (en) * | 2000-02-16 | 2006-04-18 | Verizon Laboratories Inc. | System and method for synchronizing and/or updating an existing relational database with supplemental XML data |
US7213017B2 (en) * | 2000-03-17 | 2007-05-01 | Microsoft Corporation | Systems and methods for transforming query results into hierarchical information |
US6708164B1 (en) * | 2000-03-17 | 2004-03-16 | Microsoft Corporation | Transforming query results into hierarchical information |
US7146422B1 (en) * | 2000-05-01 | 2006-12-05 | Intel Corporation | Method and apparatus for validating documents based on a validation template |
US6732175B1 (en) | 2000-04-13 | 2004-05-04 | Intel Corporation | Network apparatus for switching based on content of application data |
US7593864B2 (en) * | 2000-04-18 | 2009-09-22 | Brian Mark Shuster | Method and apparatus for managing ownership of virtual property |
US7296217B1 (en) * | 2000-05-05 | 2007-11-13 | Timberline Software Corporation | Electronic transaction document system |
US7124132B1 (en) * | 2000-05-17 | 2006-10-17 | America Online, Inc. | Domain specification system for an LDAP ACI entry |
US7788602B2 (en) | 2000-06-06 | 2010-08-31 | Microsoft Corporation | Method and system for providing restricted actions for recognized semantic categories |
US7712024B2 (en) | 2000-06-06 | 2010-05-04 | Microsoft Corporation | Application program interfaces for semantically labeling strings and providing actions based on semantically labeled strings |
US7770102B1 (en) | 2000-06-06 | 2010-08-03 | Microsoft Corporation | Method and system for semantically labeling strings and providing actions based on semantically labeled strings |
US7716163B2 (en) * | 2000-06-06 | 2010-05-11 | Microsoft Corporation | Method and system for defining semantic categories and actions |
US6704736B1 (en) * | 2000-06-28 | 2004-03-09 | Microsoft Corporation | Method and apparatus for information transformation and exchange in a relational database environment |
US7469233B2 (en) * | 2000-07-24 | 2008-12-23 | American Express Travel Related Services Company, Inc. | Method and system for facilitating the anonymous purchase of goods and services from an e-commerce website |
US7047281B1 (en) | 2000-08-08 | 2006-05-16 | Fineground Networks | Method and system for accelerating the delivery of content in a networked environment |
US20020049790A1 (en) * | 2000-08-08 | 2002-04-25 | Ricker Jeffrey M | Data interchange format transformation method and data dictionary used therefor |
AU2001281402A1 (en) * | 2000-08-08 | 2002-02-18 | Fineground Networks | Method and system for parameterized web documents |
US7617114B1 (en) | 2000-08-10 | 2009-11-10 | Wellpoint Inc. | Health care reimbursement |
WO2002015080A2 (en) * | 2000-08-10 | 2002-02-21 | Lumenos | Managing health care resources |
FR2813471B1 (en) * | 2000-08-31 | 2002-12-20 | Schneider Automation | COMMUNICATION SYSTEM FOR AUTOMATED EQUIPMENT BASED ON THE SOAP PROTOCOL |
US7328211B2 (en) | 2000-09-21 | 2008-02-05 | Jpmorgan Chase Bank, N.A. | System and methods for improved linguistic pattern matching |
US6993506B2 (en) | 2000-12-05 | 2006-01-31 | Jgr Acquisition, Inc. | Method and device utilizing polymorphic data in e-commerce |
US8015600B2 (en) | 2000-12-22 | 2011-09-06 | Oracle International Corporation | Employing electronic certificate workflows |
US7349912B2 (en) | 2000-12-22 | 2008-03-25 | Oracle International Corporation | Runtime modification of entries in an identity system |
US6816871B2 (en) * | 2000-12-22 | 2004-11-09 | Oblix, Inc. | Delivering output XML with dynamically selectable processing |
US7085834B2 (en) * | 2000-12-22 | 2006-08-01 | Oracle International Corporation | Determining a user's groups |
US7802174B2 (en) | 2000-12-22 | 2010-09-21 | Oracle International Corporation | Domain based workflows |
US7475151B2 (en) * | 2000-12-22 | 2009-01-06 | Oracle International Corporation | Policies for modifying group membership |
US7415607B2 (en) * | 2000-12-22 | 2008-08-19 | Oracle International Corporation | Obtaining and maintaining real time certificate status |
US7213249B2 (en) * | 2000-12-22 | 2007-05-01 | Oracle International Corporation | Blocking cache flush requests until completing current pending requests in a local server and remote server |
US7380008B2 (en) | 2000-12-22 | 2008-05-27 | Oracle International Corporation | Proxy system |
US6782379B2 (en) * | 2000-12-22 | 2004-08-24 | Oblix, Inc. | Preparing output XML based on selected programs and XML templates |
US7581011B2 (en) * | 2000-12-22 | 2009-08-25 | Oracle International Corporation | Template based workflow definition |
US7937655B2 (en) | 2000-12-22 | 2011-05-03 | Oracle International Corporation | Workflows with associated processes |
US7711818B2 (en) * | 2000-12-22 | 2010-05-04 | Oracle International Corporation | Support for multiple data stores |
US7363339B2 (en) * | 2000-12-22 | 2008-04-22 | Oracle International Corporation | Determining group membership |
US7415669B1 (en) | 2001-02-27 | 2008-08-19 | Open Invention Network | Method and apparatus for viewing electronic commerce-related documents |
US7036072B1 (en) | 2001-12-18 | 2006-04-25 | Jgr Acquisition, Inc. | Method and apparatus for declarative updating of self-describing, structured documents |
US8073967B2 (en) | 2002-04-15 | 2011-12-06 | Fisher-Rosemount Systems, Inc. | Web services-based communications for use with process control systems |
US7720727B2 (en) | 2001-03-01 | 2010-05-18 | Fisher-Rosemount Systems, Inc. | Economic calculations in process control system |
US7240125B2 (en) * | 2001-03-06 | 2007-07-03 | International Business Machines Corporation | Apparatus and method for using a directory service for a user registry |
US7024662B2 (en) | 2001-03-14 | 2006-04-04 | Microsoft Corporation | Executing dynamically assigned functions while providing services |
US7302634B2 (en) * | 2001-03-14 | 2007-11-27 | Microsoft Corporation | Schema-based services for identity-based data access |
US7310687B2 (en) * | 2001-03-23 | 2007-12-18 | Cisco Technology, Inc. | Methods and systems for managing class-based condensation |
US20020143644A1 (en) * | 2001-04-03 | 2002-10-03 | Cafer Tosun | Connection tool for connecting analytical applications to electronic document sources |
US6816865B2 (en) * | 2001-04-18 | 2004-11-09 | International Business Machines Corporation | Process for data driven application integration for B2B |
US7373349B2 (en) * | 2001-04-18 | 2008-05-13 | International Business Machines Corporation | Process for data driven application integration for B2B |
US7778816B2 (en) | 2001-04-24 | 2010-08-17 | Microsoft Corporation | Method and system for applying input mode bias |
US20020165975A1 (en) * | 2001-05-07 | 2002-11-07 | Michael Abbott | Dynamic mapping of communication protocols |
US8700781B2 (en) * | 2001-06-12 | 2014-04-15 | Verizon Business Global Llc | Automated processing of service requests using structured messaging protocols |
US20020188688A1 (en) * | 2001-06-12 | 2002-12-12 | Bice Richard S. | Automated message handling system and process |
US7162534B2 (en) * | 2001-07-10 | 2007-01-09 | Fisher-Rosemount Systems, Inc. | Transactional data communications for process control systems |
US7225256B2 (en) | 2001-11-30 | 2007-05-29 | Oracle International Corporation | Impersonation in an access system |
US20030229516A1 (en) * | 2002-02-07 | 2003-12-11 | Christian Nickerson | System and method for rapid claims submission and adjudication |
US7302492B1 (en) * | 2002-04-09 | 2007-11-27 | Cisco Technology, Inc. | Method and apparatus for matching web service in applications using a data object exchange protocol |
US20030233437A1 (en) * | 2002-04-24 | 2003-12-18 | Hiroshi Kitada | Browser, method, and computer program product for managing documents |
US7089491B2 (en) * | 2002-05-03 | 2006-08-08 | Microsoft Corporation | System and method for enhancing XML schemas |
US7707496B1 (en) | 2002-05-09 | 2010-04-27 | Microsoft Corporation | Method, system, and apparatus for converting dates between calendars and languages based upon semantically labeled strings |
US7814025B2 (en) * | 2002-05-15 | 2010-10-12 | Navio Systems, Inc. | Methods and apparatus for title protocol, authentication, and sharing |
US7707066B2 (en) * | 2002-05-15 | 2010-04-27 | Navio Systems, Inc. | Methods of facilitating merchant transactions using a computerized system including a set of titles |
US20030217006A1 (en) * | 2002-05-15 | 2003-11-20 | Stefan Roever | Methods and apparatus for a title transaction network |
US7707121B1 (en) | 2002-05-15 | 2010-04-27 | Navio Systems, Inc. | Methods and apparatus for title structure and management |
US7216163B2 (en) * | 2002-05-15 | 2007-05-08 | Oracle International Corporation | Method and apparatus for provisioning tasks using a provisioning bridge server |
US20060036447A1 (en) * | 2002-05-15 | 2006-02-16 | Stefan Roever | Methods of facilitating contact management using a computerized system including a set of titles |
US7840658B2 (en) | 2002-05-15 | 2010-11-23 | Oracle International Corporation | Employing job code attributes in provisioning |
US20030217094A1 (en) * | 2002-05-17 | 2003-11-20 | Anthony Dean Andrews | Correlation framework |
US7987246B2 (en) * | 2002-05-23 | 2011-07-26 | Jpmorgan Chase Bank | Method and system for client browser update |
US7707024B2 (en) | 2002-05-23 | 2010-04-27 | Microsoft Corporation | Method, system, and apparatus for converting currency values based upon semantically labeled strings |
US7742048B1 (en) | 2002-05-23 | 2010-06-22 | Microsoft Corporation | Method, system, and apparatus for converting numbers based upon semantically labeled strings |
US7827546B1 (en) | 2002-06-05 | 2010-11-02 | Microsoft Corporation | Mechanism for downloading software components from a remote source for use by a local software application |
US7356537B2 (en) | 2002-06-06 | 2008-04-08 | Microsoft Corporation | Providing contextually sensitive tools and help content in computer-generated documents |
US7716676B2 (en) | 2002-06-25 | 2010-05-11 | Microsoft Corporation | System and method for issuing a message to a program |
US9886309B2 (en) | 2002-06-28 | 2018-02-06 | Microsoft Technology Licensing, Llc | Identity-based distributed computing for device resources |
US7209915B1 (en) * | 2002-06-28 | 2007-04-24 | Microsoft Corporation | Method, system and apparatus for routing a query to one or more providers |
US20050038724A1 (en) * | 2002-08-30 | 2005-02-17 | Navio Systems, Inc. | Methods and apparatus for enabling transaction relating to digital assets |
US20050234860A1 (en) * | 2002-08-30 | 2005-10-20 | Navio Systems, Inc. | User agent for facilitating transactions in networks |
US20050246193A1 (en) * | 2002-08-30 | 2005-11-03 | Navio Systems, Inc. | Methods and apparatus for enabling transaction relating to digital assets |
US20050038707A1 (en) * | 2002-08-30 | 2005-02-17 | Navio Systems, Inc. | Methods and apparatus for enabling transactions in networks |
US20040060002A1 (en) * | 2002-09-12 | 2004-03-25 | Microsoft Corporation | Schema-based service for identity-based access to lists |
US7493603B2 (en) * | 2002-10-15 | 2009-02-17 | International Business Machines Corporation | Annotated automaton encoding of XML schema for high performance schema validation |
US7725354B2 (en) * | 2002-11-18 | 2010-05-25 | Sap Aktiengesellschaft | Interface for generating business partners |
US20040103199A1 (en) * | 2002-11-22 | 2004-05-27 | Anthony Chao | Method and system for client browser update from a lite cache |
US8538840B2 (en) * | 2002-12-20 | 2013-09-17 | Siebel Systems, Inc. | Financial services data model |
US7856454B2 (en) | 2002-12-20 | 2010-12-21 | Siebel Systems, Inc. | Data model for business relationships |
US7809698B1 (en) * | 2002-12-24 | 2010-10-05 | International Business Machines Corporation | System and method remapping identifiers to secure files |
US7783614B2 (en) * | 2003-02-13 | 2010-08-24 | Microsoft Corporation | Linking elements of a document to corresponding fields, queries and/or procedures in a database |
US8392298B2 (en) * | 2003-03-04 | 2013-03-05 | Siebel Systems, Inc. | Invoice adjustment data object for a common data object format |
US8473399B2 (en) * | 2003-03-04 | 2013-06-25 | Siebel Systems, Inc. | Invoice data object for a common data object format |
US8489470B2 (en) * | 2003-03-24 | 2013-07-16 | Siebel Systems, Inc. | Inventory location common object |
US7912932B2 (en) * | 2003-03-24 | 2011-03-22 | Siebel Systems, Inc. | Service request common object |
US7904340B2 (en) * | 2003-03-24 | 2011-03-08 | Siebel Systems, Inc. | Methods and computer-readable medium for defining a product model |
US9704120B2 (en) * | 2003-03-24 | 2017-07-11 | Oracle International Corporation | Inventory balance common object |
US8510179B2 (en) * | 2003-03-24 | 2013-08-13 | Siebel Systems, Inc. | Inventory transaction common object |
US20070208577A1 (en) * | 2003-03-24 | 2007-09-06 | Leon Maria T B | Position common object |
WO2004086198A2 (en) | 2003-03-24 | 2004-10-07 | Siebel Systems, Inc. | Common common object |
US20070226037A1 (en) * | 2003-03-25 | 2007-09-27 | Shailendra Garg | Modeling of opportunity data |
US7711550B1 (en) | 2003-04-29 | 2010-05-04 | Microsoft Corporation | Methods and system for recognizing names in a computer-generated document and for providing helpful actions associated with recognized names |
US7571172B2 (en) * | 2003-05-06 | 2009-08-04 | Novell, Inc. | Methods, data stores, data structures, and systems for electronic identity aggregation |
US7739588B2 (en) | 2003-06-27 | 2010-06-15 | Microsoft Corporation | Leveraging markup language data for semantically labeling text strings and data and for providing actions based on semantically labeled text strings and data |
EP1652113A2 (en) * | 2003-07-11 | 2006-05-03 | Computer Associates Think, Inc. | Efficient storage of xml in a directory |
US7774386B2 (en) * | 2003-07-24 | 2010-08-10 | International Business Machines Corporation | Applying abstraction to object markup definitions |
WO2005015361A2 (en) | 2003-08-08 | 2005-02-17 | Jp Morgan Chase Bank | System for archive integrity management and related methods |
US20050065964A1 (en) * | 2003-09-19 | 2005-03-24 | Ziemann David M. | Update of a tree-based database |
US7882132B2 (en) | 2003-10-09 | 2011-02-01 | Oracle International Corporation | Support for RDBMS in LDAP system |
US7904487B2 (en) | 2003-10-09 | 2011-03-08 | Oracle International Corporation | Translating data access requests |
US7480646B2 (en) * | 2003-10-23 | 2009-01-20 | Microsoft Corporation | Type path indexing |
US8732332B2 (en) * | 2003-11-19 | 2014-05-20 | Alcatel Lucent | Content switching with user-defined policies |
US20050177578A1 (en) * | 2004-02-10 | 2005-08-11 | Chen Yao-Ching S. | Efficient type annontation of XML schema-validated XML documents without schema validation |
US7437374B2 (en) * | 2004-02-10 | 2008-10-14 | International Business Machines Corporation | Efficient XML schema validation of XML fragments using annotated automaton encoding |
US8112296B2 (en) * | 2004-05-21 | 2012-02-07 | Siebel Systems, Inc. | Modeling of job profile data |
US7865390B2 (en) * | 2004-05-21 | 2011-01-04 | Siebel Systems, Inc. | Modeling of employee performance result data |
EP1782366A2 (en) | 2004-06-04 | 2007-05-09 | Sap Ag | Consistent set of interfaces derived from a business object |
US8606723B2 (en) | 2004-06-04 | 2013-12-10 | Sap Ag | Consistent set of interfaces derived from a business object model |
US8694397B2 (en) | 2004-06-18 | 2014-04-08 | Sap Ag | Consistent set of interfaces derived from a business object model |
WO2006012160A2 (en) * | 2004-06-25 | 2006-02-02 | Michael Seubert | Consistent set of interfaces derived from a business object model |
US7366974B2 (en) * | 2004-09-03 | 2008-04-29 | Jp Morgan Chase Bank | System and method for managing template attributes |
US20060059210A1 (en) * | 2004-09-16 | 2006-03-16 | Macdonald Glynne | Generic database structure and related systems and methods for storing data independent of data type |
US20090132466A1 (en) * | 2004-10-13 | 2009-05-21 | Jp Morgan Chase Bank | System and method for archiving data |
US7865519B2 (en) * | 2004-11-17 | 2011-01-04 | Sap Aktiengesellschaft | Using a controlled vocabulary library to generate business data component names |
US20060174350A1 (en) * | 2005-02-03 | 2006-08-03 | Navio Systems, Inc. | Methods and apparatus for optimizing identity management |
US20060170759A1 (en) * | 2005-02-03 | 2006-08-03 | Navio Systems Inc. | Methods and apparatus for optimizing digital asset distribution |
US8744937B2 (en) | 2005-02-25 | 2014-06-03 | Sap Ag | Consistent set of interfaces derived from a business object model |
US9201420B2 (en) | 2005-04-08 | 2015-12-01 | Rosemount, Inc. | Method and apparatus for performing a function in a process plant using monitoring data with criticality evaluation data |
US8005647B2 (en) | 2005-04-08 | 2011-08-23 | Rosemount, Inc. | Method and apparatus for monitoring and performing corrective measures in a process plant using monitoring data with corrective measures data |
US8145653B2 (en) * | 2005-04-08 | 2012-03-27 | International Business Machines Corporation | Using schemas to generate application specific business objects for use in an integration broker |
US8458201B2 (en) * | 2005-04-08 | 2013-06-04 | International Business Machines Corporation | Method and apparatus for mapping structured query language schema to application specific business objects in an integrated application environment |
US20060230048A1 (en) * | 2005-04-08 | 2006-10-12 | International Business Machines Corporation | Method and apparatus for object discovery agent based mapping of application specific markup language schemas to application specific business objects in an integrated application environment |
US8135750B2 (en) * | 2005-04-22 | 2012-03-13 | Microsoft Corporation | Efficiently describing relationships between resources |
US7437367B2 (en) * | 2005-04-22 | 2008-10-14 | Microsoft Corporation | Pack URI scheme to identify and reference parts of a package |
US20060259948A1 (en) * | 2005-05-12 | 2006-11-16 | International Business Machines Corporation | Integrated document handling in distributed collaborative applications |
US20060277064A1 (en) * | 2005-06-07 | 2006-12-07 | Cannata Michael C | Method of creating a pricing schedule for use by a pharmaceutical pricing system |
EP1934905A4 (en) * | 2005-09-02 | 2010-08-25 | Ecmarket Inc | Method and system for exchanging business documents |
US8065606B1 (en) | 2005-09-16 | 2011-11-22 | Jpmorgan Chase Bank, N.A. | System and method for automating document generation |
US7992085B2 (en) * | 2005-09-26 | 2011-08-02 | Microsoft Corporation | Lightweight reference user interface |
US7788590B2 (en) | 2005-09-26 | 2010-08-31 | Microsoft Corporation | Lightweight reference user interface |
US7624113B2 (en) * | 2005-11-23 | 2009-11-24 | Sap Ag | Data element naming system and method |
US7647500B2 (en) * | 2005-12-16 | 2010-01-12 | Microsoft Corporation | Synchronous validation and acknowledgment of electronic data interchange (EDI) |
US7599944B2 (en) * | 2005-12-16 | 2009-10-06 | Microsoft Corporation | Electronic data interchange (EDI) schema simplification interface |
US7650353B2 (en) * | 2005-12-16 | 2010-01-19 | Microsoft Corporation | XML specification for electronic data interchange (EDI) |
US9177338B2 (en) * | 2005-12-29 | 2015-11-03 | Oncircle, Inc. | Software, systems, and methods for processing digital bearer instruments |
WO2007078987A2 (en) | 2005-12-29 | 2007-07-12 | Navio Systems, Inc. | Software, systems, and methods for processing digital bearer instruments |
US7703099B2 (en) * | 2006-02-24 | 2010-04-20 | Microsoft Corporation | Scalable transformation and configuration of EDI interchanges |
US7620645B2 (en) * | 2006-02-24 | 2009-11-17 | Microsoft Corporation | Scalable algorithm for sharing EDI schemas |
US7685208B2 (en) * | 2006-02-24 | 2010-03-23 | Microsoft Corporation | XML payload specification for modeling EDI schemas |
US7984373B2 (en) * | 2006-02-24 | 2011-07-19 | Microsoft Corporation | EDI instance based transaction set definition |
US8156148B2 (en) * | 2006-02-24 | 2012-04-10 | Microsoft Corporation | Scalable algorithm for sharing EDI schemas |
US8374931B2 (en) | 2006-03-31 | 2013-02-12 | Sap Ag | Consistent set of interfaces derived from a business object model |
US9621372B2 (en) * | 2006-04-29 | 2017-04-11 | Oncircle, Inc. | Title-enabled networking |
US7814498B2 (en) * | 2006-05-01 | 2010-10-12 | Microsoft Corporation | Loading application resources |
EP2076874A4 (en) | 2006-05-13 | 2011-03-09 | Sap Ag | Consistent set of interfaces derived from a business object model |
US8392364B2 (en) | 2006-07-10 | 2013-03-05 | Sap Ag | Consistent set of interfaces derived from a business object model |
US8566193B2 (en) | 2006-08-11 | 2013-10-22 | Sap Ag | Consistent set of interfaces derived from a business object model |
US20080071887A1 (en) * | 2006-09-19 | 2008-03-20 | Microsoft Corporation | Intelligent translation of electronic data interchange documents to extensible markup language representations |
US20080126386A1 (en) * | 2006-09-20 | 2008-05-29 | Microsoft Corporation | Translation of electronic data interchange messages to extensible markup language representation(s) |
US8402473B1 (en) | 2006-09-28 | 2013-03-19 | Sap Ag | Managing consistent interfaces for demand business objects across heterogeneous systems |
US8104076B1 (en) | 2006-11-13 | 2012-01-24 | Jpmorgan Chase Bank, N.A. | Application access control system |
US10192234B2 (en) | 2006-11-15 | 2019-01-29 | Api Market, Inc. | Title materials embedded within media formats and related applications |
US20080168081A1 (en) * | 2007-01-09 | 2008-07-10 | Microsoft Corporation | Extensible schemas and party configurations for edi document generation or validation |
US20090003583A1 (en) * | 2007-01-12 | 2009-01-01 | Wellpoint, Inc. | Method for enhancing call center performance |
US8301676B2 (en) | 2007-08-23 | 2012-10-30 | Fisher-Rosemount Systems, Inc. | Field device with capability of calculating digital filter coefficients |
US7702401B2 (en) | 2007-09-05 | 2010-04-20 | Fisher-Rosemount Systems, Inc. | System for preserving and displaying process control data associated with an abnormal situation |
US8055479B2 (en) | 2007-10-10 | 2011-11-08 | Fisher-Rosemount Systems, Inc. | Simplified algorithm for abnormal situation prevention in load following applications including plugged line diagnostics in a dynamic process |
US20090157859A1 (en) * | 2007-12-17 | 2009-06-18 | Morris Robert P | Methods And Systems For Accessing A Resource Based On URN Scheme Modifiers |
US8417593B2 (en) | 2008-02-28 | 2013-04-09 | Sap Ag | System and computer-readable medium for managing consistent interfaces for business objects across heterogeneous systems |
US8433585B2 (en) | 2008-03-31 | 2013-04-30 | Sap Ag | Managing consistent interfaces for business objects across heterogeneous systems |
US8364715B2 (en) * | 2008-03-31 | 2013-01-29 | Sap Ag | Managing consistent interfaces for automatic identification label business objects across heterogeneous systems |
US8589263B2 (en) * | 2008-03-31 | 2013-11-19 | Sap Ag | Managing consistent interfaces for retail business objects across heterogeneous systems |
US8370233B2 (en) * | 2008-03-31 | 2013-02-05 | Sap Ag | Managing consistent interfaces for business objects across heterogeneous systems |
US8930248B2 (en) | 2008-03-31 | 2015-01-06 | Sap Se | Managing consistent interfaces for supply network business objects across heterogeneous systems |
US8473317B2 (en) * | 2008-03-31 | 2013-06-25 | Sap Ag | Managing consistent interfaces for service part business objects across heterogeneous systems |
US8413165B2 (en) * | 2008-03-31 | 2013-04-02 | Sap Ag | Managing consistent interfaces for maintenance order business objects across heterogeneous systems |
US8423418B2 (en) * | 2008-03-31 | 2013-04-16 | Sap Ag | Managing consistent interfaces for business objects across heterogeneous systems |
US8577991B2 (en) * | 2008-03-31 | 2013-11-05 | Sap Ag | Managing consistent interfaces for internal service request business objects across heterogeneous systems |
US8566185B2 (en) | 2008-06-26 | 2013-10-22 | Sap Ag | Managing consistent interfaces for financial instrument business objects across heterogeneous systems |
US20090326988A1 (en) * | 2008-06-26 | 2009-12-31 | Robert Barth | Managing consistent interfaces for business objects across heterogeneous systems |
US8671064B2 (en) | 2008-06-26 | 2014-03-11 | Sap Ag | Managing consistent interfaces for supply chain management business objects across heterogeneous systems |
US8645228B2 (en) * | 2008-06-26 | 2014-02-04 | Sap Ag | Managing consistent interfaces for business objects across heterogeneous systems |
US8180810B2 (en) * | 2008-08-21 | 2012-05-15 | International Business Machines Corporation | Interactive generation of integrated schemas |
US8577760B2 (en) * | 2008-11-25 | 2013-11-05 | Sap Ag | Managing consistent interfaces for tax authority business objects across heterogeneous systems |
US8463666B2 (en) * | 2008-11-25 | 2013-06-11 | Sap Ag | Managing consistent interfaces for merchandise and assortment planning business objects across heterogeneous systems |
US20100153297A1 (en) * | 2008-12-12 | 2010-06-17 | Sap Ag | Managing Consistent Interfaces for Credit Portfolio Business Objects Across Heterogeneous Systems |
US20100235469A1 (en) * | 2009-03-11 | 2010-09-16 | Morris Robert P | Method And System For Providing Access To Resources Related To A Locatable Resource |
US8396751B2 (en) | 2009-09-30 | 2013-03-12 | Sap Ag | Managing consistent interfaces for merchandising business objects across heterogeneous systems |
US8412603B2 (en) | 2010-06-15 | 2013-04-02 | Sap Ag | Managing consistent interfaces for currency conversion and date and time business objects across heterogeneous systems |
US8732083B2 (en) | 2010-06-15 | 2014-05-20 | Sap Ag | Managing consistent interfaces for number range, number range profile, payment card payment authorisation, and product template template business objects across heterogeneous systems |
US8417588B2 (en) | 2010-06-15 | 2013-04-09 | Sap Ag | Managing consistent interfaces for goods tag, production bill of material hierarchy, and release order template business objects across heterogeneous systems |
US8515794B2 (en) | 2010-06-15 | 2013-08-20 | Sap Ag | Managing consistent interfaces for employee time event and human capital management view of payroll process business objects across heterogeneous systems |
US8370272B2 (en) | 2010-06-15 | 2013-02-05 | Sap Ag | Managing consistent interfaces for business document message monitoring view, customs arrangement, and freight list business objects across heterogeneous systems |
US8364608B2 (en) | 2010-06-15 | 2013-01-29 | Sap Ag | Managing consistent interfaces for export declaration and export declaration request business objects across heterogeneous systems |
US9135585B2 (en) | 2010-06-15 | 2015-09-15 | Sap Se | Managing consistent interfaces for property library, property list template, quantity conversion virtual object, and supplier property specification business objects across heterogeneous systems |
US9038177B1 (en) | 2010-11-30 | 2015-05-19 | Jpmorgan Chase Bank, N.A. | Method and system for implementing multi-level data fusion |
US8572157B2 (en) | 2011-01-31 | 2013-10-29 | Microsoft Corporation | Configuration based approach to unify web services |
US9927788B2 (en) | 2011-05-19 | 2018-03-27 | Fisher-Rosemount Systems, Inc. | Software lockout coordination between a process control system and an asset management system |
US9292588B1 (en) | 2011-07-20 | 2016-03-22 | Jpmorgan Chase Bank, N.A. | Safe storing data for disaster recovery |
US8775280B2 (en) | 2011-07-28 | 2014-07-08 | Sap Ag | Managing consistent interfaces for financial business objects across heterogeneous systems |
US8725654B2 (en) | 2011-07-28 | 2014-05-13 | Sap Ag | Managing consistent interfaces for employee data replication business objects across heterogeneous systems |
US8560392B2 (en) | 2011-07-28 | 2013-10-15 | Sap Ag | Managing consistent interfaces for a point of sale transaction business object across heterogeneous systems |
US8666845B2 (en) | 2011-07-28 | 2014-03-04 | Sap Ag | Managing consistent interfaces for a customer requirement business object across heterogeneous systems |
US8601490B2 (en) | 2011-07-28 | 2013-12-03 | Sap Ag | Managing consistent interfaces for business rule business object across heterogeneous systems |
US8521838B2 (en) | 2011-07-28 | 2013-08-27 | Sap Ag | Managing consistent interfaces for communication system and object identifier mapping business objects across heterogeneous systems |
US9509704B2 (en) | 2011-08-02 | 2016-11-29 | Oncircle, Inc. | Rights-based system |
US8756274B2 (en) | 2012-02-16 | 2014-06-17 | Sap Ag | Consistent interface for sales territory message type set 1 |
US8762453B2 (en) | 2012-02-16 | 2014-06-24 | Sap Ag | Consistent interface for feed collaboration group and feed event subscription |
US9232368B2 (en) | 2012-02-16 | 2016-01-05 | Sap Se | Consistent interface for user feed administrator, user feed event link and user feed settings |
US9237425B2 (en) | 2012-02-16 | 2016-01-12 | Sap Se | Consistent interface for feed event, feed event document and feed event type |
US8762454B2 (en) | 2012-02-16 | 2014-06-24 | Sap Ag | Consistent interface for flag and tag |
US8984050B2 (en) | 2012-02-16 | 2015-03-17 | Sap Se | Consistent interface for sales territory message type set 2 |
US8521621B1 (en) | 2012-06-28 | 2013-08-27 | Sap Ag | Consistent interface for inbound delivery request |
US9367826B2 (en) | 2012-06-28 | 2016-06-14 | Sap Se | Consistent interface for entitlement product |
US9400998B2 (en) | 2012-06-28 | 2016-07-26 | Sap Se | Consistent interface for message-based communication arrangement, organisational centre replication request, and payment schedule |
US8615451B1 (en) | 2012-06-28 | 2013-12-24 | Sap Ag | Consistent interface for goods and activity confirmation |
US8756135B2 (en) | 2012-06-28 | 2014-06-17 | Sap Ag | Consistent interface for product valuation data and product valuation level |
WO2014000200A1 (en) | 2012-06-28 | 2014-01-03 | Sap Ag | Consistent interface for document output request |
US8949855B2 (en) | 2012-06-28 | 2015-02-03 | Sap Se | Consistent interface for address snapshot and approval process definition |
US9246869B2 (en) | 2012-06-28 | 2016-01-26 | Sap Se | Consistent interface for opportunity |
US9547833B2 (en) | 2012-08-22 | 2017-01-17 | Sap Se | Consistent interface for financial instrument impairment calculation |
US9076112B2 (en) | 2012-08-22 | 2015-07-07 | Sap Se | Consistent interface for financial instrument impairment expected cash flow analytical result |
US9043236B2 (en) | 2012-08-22 | 2015-05-26 | Sap Se | Consistent interface for financial instrument impairment attribute values analytical result |
US10540373B1 (en) | 2013-03-04 | 2020-01-21 | Jpmorgan Chase Bank, N.A. | Clause library manager |
US9191343B2 (en) | 2013-03-15 | 2015-11-17 | Sap Se | Consistent interface for appointment activity business object |
US9191357B2 (en) | 2013-03-15 | 2015-11-17 | Sap Se | Consistent interface for email activity business object |
US11863615B2 (en) | 2022-03-18 | 2024-01-02 | T-Mobile Usa, Inc. | Content management systems providing zero recovery time objective |
Family Cites Families (23)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP1235177A3 (en) | 1993-12-16 | 2003-10-08 | divine technology ventures | Digital active advertising |
US5790677A (en) | 1995-06-29 | 1998-08-04 | Microsoft Corporation | System and method for secure electronic commerce transactions |
US5893109A (en) * | 1996-03-15 | 1999-04-06 | Inso Providence Corporation | Generation of chunks of a long document for an electronic book system |
IL130736A0 (en) * | 1997-01-24 | 2000-06-01 | Extricity Software Inc | A system and method for creating executing and maintaining cross-enterprise processes |
AUPO525497A0 (en) * | 1997-02-21 | 1997-03-20 | Mills, Dudley John | Network-based classified information systems |
US6341353B1 (en) * | 1997-04-11 | 2002-01-22 | The Brodia Group | Smart electronic receipt system |
US6028605A (en) * | 1998-02-03 | 2000-02-22 | Documentum, Inc. | Multi-dimensional analysis of objects by manipulating discovered semantic properties |
US6151624A (en) * | 1998-02-03 | 2000-11-21 | Realnames Corporation | Navigating network resources based on metadata |
US6012098A (en) * | 1998-02-23 | 2000-01-04 | International Business Machines Corp. | Servlet pairing for isolation of the retrieval and rendering of data |
US6154738A (en) * | 1998-03-27 | 2000-11-28 | Call; Charles Gainor | Methods and apparatus for disseminating product information via the internet using universal product codes |
FR2777725B1 (en) * | 1998-04-15 | 2003-02-21 | Franck Jeannin | COMPUTER SYSTEM FOR MANAGING LINKS AND METHOD FOR IMPLEMENTING SUCH SYSTEM |
US6167448A (en) * | 1998-06-11 | 2000-12-26 | Compaq Computer Corporation | Management event notification system using event notification messages written using a markup language |
US6011844A (en) * | 1998-06-19 | 2000-01-04 | Callnet Communications | Point-of-presence call center management system |
US6263332B1 (en) * | 1998-08-14 | 2001-07-17 | Vignette Corporation | System and method for query processing of structured documents |
US7051275B2 (en) * | 1998-09-15 | 2006-05-23 | Microsoft Corporation | Annotations for multiple versions of media content |
US6470317B1 (en) * | 1998-10-02 | 2002-10-22 | Motorola, Inc. | Markup language to allow for billing of interactive services and methods thereof |
US6366934B1 (en) * | 1998-10-08 | 2002-04-02 | International Business Machines Corporation | Method and apparatus for querying structured documents using a database extender |
US6125391A (en) * | 1998-10-16 | 2000-09-26 | Commerce One, Inc. | Market makers using documents for commerce in trading partner networks |
ATE273538T1 (en) * | 1998-10-28 | 2004-08-15 | Verticalone Corp | APPARATUS AND METHOD FOR AUTOMATIC AGGREGATION AND SUPPLY OF ELECTRONIC PERSONAL INFORMATION OR DATA |
US6336214B1 (en) * | 1998-11-10 | 2002-01-01 | International Business Machines Corporation | System and method for automatically generating browsable language grammars |
US6249844B1 (en) * | 1998-11-13 | 2001-06-19 | International Business Machines Corporation | Identifying, processing and caching object fragments in a web environment |
US6393456B1 (en) * | 1998-11-30 | 2002-05-21 | Microsoft Corporation | System, method, and computer program product for workflow processing using internet interoperable electronic messaging with mime multiple content type |
US6381597B1 (en) * | 1999-10-07 | 2002-04-30 | U-Know Software Corporation | Electronic shopping agent which is capable of operating with vendor sites which have disparate formats |
-
2000
- 2000-01-28 US US09/493,954 patent/US6591260B1/en not_active Expired - Lifetime
-
2001
- 2001-01-26 EP EP01903359A patent/EP1250657A2/en not_active Withdrawn
- 2001-01-26 WO PCT/US2001/002665 patent/WO2001055891A2/en not_active Application Discontinuation
- 2001-01-26 AU AU2001231187A patent/AU2001231187A1/en not_active Abandoned
- 2001-01-26 JP JP2001555367A patent/JP2003530627A/en active Pending
Non-Patent Citations (1)
Title |
---|
No Search * |
Cited By (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9659326B2 (en) | 1999-03-12 | 2017-05-23 | Collections Marketing Center, Inc. | System and method for debt presentment and resolution |
EP1296252A1 (en) * | 2001-09-21 | 2003-03-26 | Koninklijke KPN N.V. | A method, computer system, communication network, computer program and data carrier for filtering data |
US8151003B2 (en) | 2002-02-05 | 2012-04-03 | International Business Machines Corporation | System and method for routing data by a server |
EP1817735A2 (en) * | 2004-10-19 | 2007-08-15 | Apollo Enterprise Solutions, LLC | System and method for resolving transactions |
EP1817735A4 (en) * | 2004-10-19 | 2009-07-08 | Apollo Entpr Solutions Llc | System and method for resolving transactions |
EP2474947A1 (en) * | 2004-10-19 | 2012-07-11 | Apollo Enterprise Solutions, Inc. | System and methods for resolving transactions |
US8504468B2 (en) | 2004-10-19 | 2013-08-06 | Apollo Enterprise Solutions, Inc. | System and method for compiling information for resolving transactions |
US8768826B2 (en) | 2004-10-19 | 2014-07-01 | Apollo Enterprise Solutions, Inc. | System for resolving transactions |
US7711676B2 (en) | 2004-11-12 | 2010-05-04 | Sap Aktiengesellschaft | Tracking usage of data elements in electronic business communications |
US7818342B2 (en) | 2004-11-12 | 2010-10-19 | Sap Ag | Tracking usage of data elements in electronic business communications |
US8660941B2 (en) | 2006-09-26 | 2014-02-25 | Collections Marketing Center, Inc. | Method and system for providing a multi-channel virtual collections center |
Also Published As
Publication number | Publication date |
---|---|
AU2001231187A1 (en) | 2001-08-07 |
WO2001055891A8 (en) | 2002-06-27 |
JP2003530627A (en) | 2003-10-14 |
EP1250657A2 (en) | 2002-10-23 |
US6591260B1 (en) | 2003-07-08 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US6591260B1 (en) | Method of retrieving schemas for interpreting documents in an electronic commerce system | |
US9037966B2 (en) | System and method for schema evolution in an E-commerce network | |
US7877682B2 (en) | Modular distributed mobile data applications | |
JP5255605B2 (en) | Registry-driven interoperability and document exchange | |
US7188114B2 (en) | Persistent data storage for metadata related to web service entities | |
US7051032B2 (en) | System and method for providing post HOC access to legacy applications and data | |
US7281211B2 (en) | Automated method, system, and software for transforming data between extensible markup language format and electronic data interchange format | |
US8458201B2 (en) | Method and apparatus for mapping structured query language schema to application specific business objects in an integrated application environment | |
US6658624B1 (en) | Method and system for processing documents controlled by active documents with embedded instructions | |
US8561022B2 (en) | Method and apparatus for viewing electronic commerce-related documents | |
US20020032775A1 (en) | System and method for transmitting and retrieving data via a distributed persistence framework | |
US20090037446A1 (en) | Lightweight Directory Access Protocol (LDAP) Schema Definition Using Extensible Markup Language (XML) | |
US20120278489A1 (en) | Extracting web services from resources using a web services resources programming model | |
WO2000065486A2 (en) | A method of mapping semantic context to enable interoperability among disparate sources | |
US7302492B1 (en) | Method and apparatus for matching web service in applications using a data object exchange protocol | |
Esposito | Applied XML programming for Microsoft. NET | |
JP2003530628A (en) | System and method for deploying a schema in an e-commerce network | |
Cope et al. | UDDI for a manufactured product brokering service | |
Solbrig et al. | Terminology access methods leveraging LDAP resources | |
KR20050059045A (en) | Registry driven interoperability and exchange of documents | |
Pereira et al. | TDWG Life Sciences Identifiers Applicability Statement | |
Pereira et al. | TDWG Life Sciences Identifiers (LSID) Applicability Statement | |
Thomas | Share: document annotation and version control for the Internet |
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 BY BZ CA CH CN CR CU CZ DE DK DM DZ EE 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 PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG US UZ VN YU ZA ZW |
|
AL | Designated countries for regional patents |
Kind code of ref document: A2 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) | ||
AK | Designated states |
Kind code of ref document: C1 Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CR CU CZ DE DK DM DZ EE 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 PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG US UZ VN YU ZA ZW |
|
AL | Designated countries for regional patents |
Kind code of ref document: C1 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 |
|
D17 | Declaration under article 17(2)a | ||
WWE | Wipo information: entry into national phase |
Ref document number: 2001903359 Country of ref document: EP |
|
ENP | Entry into the national phase |
Ref country code: JP Ref document number: 2001 555367 Kind code of ref document: A Format of ref document f/p: F |
|
WWP | Wipo information: published in national office |
Ref document number: 2001903359 Country of ref document: EP |
|
REG | Reference to national code |
Ref country code: DE Ref legal event code: 8642 |
|
WWW | Wipo information: withdrawn in national office |
Ref document number: 2001903359 Country of ref document: EP |