The present invention includes a method and device for updating a self-describing, structured document. A further aspect of the present invention is enabling client-based modification of the document. Additional aspects of the present invention are described in the claims, specification and drawings.
|
1. A method of preparing a response to an xml document received, the method including:
receiving an xml document and detecting its document type;
looking up the document type and offering a user one or more available reply document types to select and generate in draft;
applying a first style sheet to generate the selected draft reply document and building an in-memory tree-based representation of the selected draft reply document;
applying a second style sheet to generate an interface that supports editing of the in-memory draft reply document;
accepting edits, updating the in-memory draft reply document, marshalling it into xml format, and either persisting it for later use or sending it as a reply to the xml document.
7. A method of editing draft xml documents, the method including:
retrieving a draft xml document and detecting its document type;
building an in-memory tree-based representation of the draft document;
applying a first style sheet to generate an interface that supports editing of the in-memory draft document;
accepting edits and updating the in-memory draft document;
error checking updated the draft document and generating an error report of any errors detected either as an in-memory tree-based representation of the errors detected or an xml error report document; and
applying a second style sheet to merge the updated draft document and the error report and generate an interface that juxtaposes the error messages with parts of the draft document containing errors.
13. A method of composing draft xml documents, the method including:
receiving a specification of a document type for an xml document to draft;
building an in-memory tree-based representation of the draft document;
applying a first style sheet to generate an interface that supports editing of the in-memory draft document; and
accepting edits and updating the in-memory draft document;
error checking the updated draft document and generating an error report of any errors detected either as an in-memory tree-based representation of the errors detected or an xml error report document; and
applying a second style sheet to merge the updated draft document and the error report and generate an interface that juxtaposes the error messages with parts of the draft document containing errors.
17. A device for composing and editing generic xml documents, the device including:
a processor:
a schema repository of schemas for xml documents of various document types;
a style sheet repository of style sheets applicable to the document types adapted to generate an interface that supports editing of the in-memory draft document;
a user interaction module that receives a request from a user to compose or edit an xml document of a particular document type;
an document tree module that builds an in-memory tree-based representation of the selected draft document, responsive to the user interaction module and compliant with a schema from the schema repository; and
a transformation module coupled to the user interaction model that selects a style sheet from the style sheet repository, responsive to the request and to the document type requested, and applies the style sheet to the in-memory tree-based representation of the selected draft document, to generate an editing interface that supports editing of the in-memory draft reply document;
wherein the user interaction module is further adapted to publish the editing interface to the user and to accept edits;
wherein the document tree module is further adapted to update the in-memory draft document, marshal it into xml format, and persist it for later use.
2. The method of
3. The method of
4. The method of
5. The method of
error checking the draft reply document and generating an error report of any errors detected either as an in-memory tree-based representation of the errors detected or an xml error report document; and
applying a third style sheet to merge the draft reply document and the error report and generate an interface that juxtaposes the error messages with parts of the draft reply document containing errors.
6. The method of
applying the third style sheet further includes generating an interface that supports editing of the in-memory draft reply document; and
accepting edits, updating the in-memory draft reply document, marshalling it into xml format, and either persisting it for later use or sending it as a reply to the xml document.
8. The method of
9. The method of
10. The method of
11. The method of
12. The method of
applying the second style sheet further includes generating an interface that supports editing of the in-memory draft document; and
accepting edits, updating the in-memory draft document, marshalling it into xml format, and either persisting it for later use or sending it as a reply to the xml document.
14. The method of
15. The method of
16. The method of
|
|||||||||||||||||||||||||||||||
This application is a continuation of U.S. application Ser. No. 11/371,768, filed on Mar. 9, 2006 with projected issuance on Oct. 2, 2007 as U.S. Pat. No. 7,278,096, entitled METHOD AND APPARATUS FOR DECLARATIVE UPDATING OF SELF-DESCRIBING, STRUCTURED DOCUMENTS by inventors Muljadi Sulistio, Yang Wei, Kelly Lane Schwarzhoff and Yuan Ding. U.S. Pat. No. 7,278,096 is a divisional of an application filed on Dec. 18, 2001 that issued as U.S. Pat. No. 7,036,072 on Apr. 25, 2006, also entitled METHOD AND APPARATUS FOR DECLARATIVE UPDATING OF SELF-DESCRIBING, STRUCTURED DOCUMENTS, by the same inventors.
The present application is related to the commonly assigned, co-pending U.S. patent application Ser. No. 09/794,302, filed on Feb. 27, 2001, entitled A METHOD AND APPARATUS FOR VIEWING ELECTRONIC COMMERCE-RELATED DOCUMENTS, by inventors Andrew Everett Davidson, Kelly Lane Schwarzhoff, Gunawan Herri, Changyi Zhu, Ari Krish, Muljadi Sulistio, and Sun Keun Lee, which is hereby incorporated by reference as if fully set forth.
This application is further related to the commonly co-assigned and pending U.S. patent application Ser. No. 10/026,663, xCBL MAILBOX METHODS AND DEVICES filed on Dec. 18, 2001, by inventors Muljadi Sulistio, Yang Wei, Kelly Lane Schwarzhoff, Yuan Ding, Sun Lee and Andy Yang, and the following U.S. patents, also based on applications filed on Dec. 18, 2001: U.S. Pat. No. 7,058,886, METHOD AND APPARATUS FOR DECLARATIVE ERROR HANDLING AND PRESENTATION issued Jun. 6, 2006; and U.S. Pat. No. 7,237,191, METHOD AND APPARATUS FOR GENERIC SEARCH INTERFACE ACROSS DOCUMENT TYPES issued Jun. 6, 2007; by inventors Muljadi Sulistio, Yang Wei, Kelly Lane Schwarzhoff, Yuan Ding, Sun Lee and Andy Yang; which are hereby incorporated by reference as if fully set forth.
A portion of the disclosure of this patent document contains material, which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure is it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever.
Electronic commerce between businesses has gained substantial momentum. Electronic marketplaces and XML or similar documents have begun to replace traditional EDI formats for commerce-related documents. Still, many businesses, particularly small and medium-sized businesses, have not adopted automated EDI or XML document processing. Whatever their size, many businesses face the prospect of an expedited implementation of EDI or XML document processing. It remains easier for large trading partners to generate XML or similar documents than it is for small to medium-sized businesses to adopt the technology needed to process them. In addition, a full scale conversion to EDI or XML transaction processing may involve far more documents than a business can practically convert in a workable time frame or on a reasonable budget.
One problem with the implementation of EDI or XML transaction processing is the complexity and cost of procedural programming to process business documents. Procedural programming, otherwise known as hard coding, requires much effort to describe document transformations and manipulations in procedural terms, using programming languages such as Java and C++. This effort translates into time for implementation and cost of implementation.
In some domains or problem spaces, declarative programming has been introduced. It is generally hoped that so-called declarative programming can make program customization accessible even to non-programmers. At the same time, it has been recognized that declarative programming is best when applied to a limited domain. Accordingly, declarative approaches are narrow and tailored, not generally applied.
Therefore, in the domain of exchanging self-defining, structured documents, it is desirable to develop declarative methods and components for simplifying the handling of documents. Declarative methods and components can improve interactions with users, particularly in the areas of producing documents, presenting error messages and searching for documents.
The present invention includes a method and device for updating a self-describing, structured document. A further aspect of the present invention is enabling client-based modification of the document. Additional aspects of the present invention are described in the claims, specification and drawings.
The following detailed description is made with reference to the figures. Preferred and alternative embodiments are described to illustrate the present invention, not to limit its scope, which is defined by the claims. Those of ordinary skill in the art will recognize a variety of equivalent variations on the description that follows.
From the list of documents in a folder screen, the user can export a document 131, read it 132, or use it as a basis for a new document 133, either by replying to or copying the base document. The document may be exported as an XML, PDF, CSV, HTML or other-formatted document. Standard or user-supplied export filters can be implemented.
The processing of a user request to view a document can be understood by reference to the co-pending application for A Method and Apparatus for Viewing Electronic Commerce-Related Documents at pp. 5-52 and the figures cited therein. In general, a series of style sheets can be constructed for displaying documents. These style sheets may be written in XSLT, or another transformation language applicable to the data type of the documents. A series of style sheets may be written, from generic to highly customized. A rule selector can be used to select among the available style sheets based on criteria such as document type, marketplace identity, sender identity, receiver identity, portal identity or other selected criteria. A directory tree, database or other data structure can be used to access style sheets based upon the criteria used.
A user can select among document types for a resulting reply document 133. The available document types for a resulting reply document depend on the document type of the starting document type, for instance a starting document selected from a list of documents 123.
The document type selection screen of
A document being sent is typically a self-describing, structured document. XML documents are a common type of self-describing, structured documents. Fields within this document are self-describing, as the fields are tagged. A sample document having two different types of tagged fields is illustrated in
Referring to
On server 708, one or more services 711-713 may be available. One service may receive the document 711. The same or another service 712 may persistently store the incoming document, for instance in a database 707. One or more databases may be used to store data useful for electronic commerce or other document exchange. A database may include a repository of schemas 741 for standard and entity-defined business documents, a repository of JavaBeans 742, C++ structures, Pascal records or scripts useful to electronic commerce, a document map repository 743 for translation of documents from one format to another (e.g., the xCBL format to an export format) and for transformation of documents from one type to another (e.g., from a request for quotation to a quotation.) The database may further include a report layout repository 744 and a presentation layout repository 745. The presentation layout repository may include declarative transformations for changing documents from a Sox document format to an HTML format, and back again. The transmission properties data describes the transport information needed to sent a business document to a recipient. For example, SSL security credentials can be stored as transmission properties. A trading partner directory is also useful. The trading partner directory may, as described above, identify URLs to which the sending entity 701 transmits documents. The persistent storage for data 707, 741-47 may be on a single data storage unit or multiple units. Persistent document storage need not be part of a database. An indexed flat file would suffice to store XML-compliant documents. The services host 708 may also host an indexing service to index one or more of the tagged fields. Alternatively, a database system managing the persistent storage or other subsystem may index documents for retrieval. An incoming document may or may not be validated against schema from a schema repository 741, before it is persistently stored. A schema may be used to interpret the document. One or more JavaBeans or Scripps may be used to act on the document before it is stored.
One schema for persistently stored documents is illustrated in
Persistent storage of the incoming document may be accompanied by various processing steps. The original document, prior to normalizing, may be stored in a database. Envelope properties may be extracted from the envelope and normalized in a database or other storage. A predefined list of indexed fields, by document type, may be consulted and those fields indexed. Generic document properties, such as date and status, may be extracted from the envelope. The envelope itself may be separately stored. Attachments may be separately stored. Unneeded white space may be removed and name space abbreviations used to reduce storage requirements.
Returning to
A system 704 may be based upon a web server and a servlet container, for instance, compatible with JRun 3. A user interface application 721 may include a homepage 721, an in box 722, one or more services to read the document and/or its attachments 723, services for folder management 724, customized folders 725, searching for and listing documents. An additional service may provide access for downloading template documents 728. The web server may include Microsoft's WebServer software, a Java interpreter such as JRun 3 and a servlet container. A data storage interface may use the resources of a database. A first collection of services 720 is illustrated as being coupled with a transformation engine 730. The transformation engine may include selection logic 732 to select the style sheet for transformation purposes and transformation logic 731 which applies a style sheet to a document.
Sample excerpts of a document to display transformation 1212 for a main processing routine and display of header information with embedded path specifications follows:
Default.xsl
<?xml version=“1.0” ?>
− <xsl:style sheet version=“1.0”
xmlns:xsl=“http://www.w3.org/1999/XSL/Transform”
xmlns:ext=“http://www.commerceone.com/xmlpres” xmlns:cbl=“urn:x-
commerceone:
document:com:commerceone:XCBL30:XCBL30.sox$1.0”
xmlns:xm=“http://www.commerceone.com/xcblmailbox”>
<xsl:include href=“schematronerror.xsl” />
<xsl:include href=“header_display.xsl” />
<xsl:include href=“detail_display.xsl” />
<xsl:include href=“summary_display.xsl” />
<xsl:include href=“Ir:Quote:Quote_variable.xsl$1.0” />
<xsl:decimal-format name=“DEIT” decimal-separator=“,” grouping-
separator=“.” />
<xsl:decimal-format name=“FR” decimal-separator=“,” grouping-
separator=“” />
− <xsl:template match=“/”>
− <!--
This is for displaying Schematron errors
-->
− <xsl:if test=“string($xm:hasSchematron)=‘true’”>
<xsl:variable name=“results” select=“document(‘error:///
schematronConformance.xml’)” />
− <xsl:call-template name=“ErrorDisplayer”>
<xsl:with-param name=“confdoc” select=“$results” />
<xsl:with-param name=“idmap” select=“$schematronmaps” />
</xsl:call-template>
</xsl:if>
− <!--
If the xml instance has error, display error fields with
field validation error
-->
− <xsl:choose>
− <xsl:when test=“string($xm:hasError)=‘true’”>
<xsl:variable name=“ErrorDocument” select=“document(‘error:/
//inMemoryError’)” />
− <xsl:variable name=“Prefixes”>
<empty />
</xsl:variable>
− <xsl:call-template name=“DisplayHeader_Error”>
<xsl:with-param name=“Prefixes” select=“$Prefixes” />
<xsl:with-param name=“ErrorDocument”
select=“$ErrorDocument” />
<xsl:with-param name=“ErrorCodeMaps” select=“$codemaps”
/>
</xsl:call-template>
− <xsl:call-template name=“DisplayDetail_Error”>
<xsl:with-param name=“Prefixes” select=“$Prefixes” />
<xsl:with-param name=“ErrorDocument”
select=“$ErrorDocument” />
<xsl:with-param name=“ErrorCodeMaps” select=“$codemaps”
/>
</xsl:call-template>
<xsl:call-template name=“DisplaySummary” />
</xsl:when>
− <!--
If the xml instance doesn't contain error, display all
fields without any error
-->
− <xsl:otherwise>
<xsl:call-template name=“DisplayHeader_NoError”/>
<xsl:call-template name=“DisplayDetail_NoError” />
<xsl:call-template name=“DisplaySummary” />
</xsl:otherwise>
</xsl:choose>
</xsl:template>
</xsl:style sheet>
Header display.xsl
<?xml version=“1.0” encoding=“UTF-8” ?>
− <xsl:style sheet version=“1.0”
xmlns:xsl=“http://www.w3.org/1999/XSL/Transform”
xmlns:ext=“http://www.commerceone.com/xmlpres” xmlns:cbl=“urn:x-
commerceone:
document:com:commerceone:XCBL30:XCBL30.sox$1.0”
xmlns:xm=“http://www.commerceone.com/xcblmailbox”>
<xsl:include href=“error.xsl” />
<xsl:include href=“header_party_display.xsl” />
− <xsl:template name=“DisplayHeader_Error”>
− <!--
This is the prefix to namespace bindings used in the
location
-->
<xsl:param name=“Prefixes” />
− <!--
This is the error document to retrieve errors from
-->
<xsl:param name=“ErrorDocument” />
− <!--
This is a result tree fragment that maps error codes
to localized descriptions
-->
<xsl:param name=“ErrorCodeMaps” />
− <TABLE cellpadding=“1” cellspacing=“0” border=“0” width=“100%”>
− <TR class=“ListHeader”>
− <TD align=“left” colspan=“2” class=“ListHeaderText” >
<xsl:value-of select=“$QuoteHeader” />
</TD>
</TR>
− <TR>
− <TD class=“StatusHeaderSmallNew” width=“50%”>
<span class=“RequiredField”>*</span>
<xsl:value-of select=“$QuoteRefNum” />
</TD>
− <TD class=“StatusHeaderSmallNew” width=“50%”>
<span class=“RequiredField”>*</span>
<xsl:value-of select=“$QuoteIssueDate” />
(
<xsl:value-of select=“string($xm:DATETIMEMASK)” />
)
</TD>
</TR>
− <TR>
− <TD class=“ElementStyle” width=“50%”>
<xsl:variable name=“xpath”>/Quote/QuoteHeader/QuoteID/
Reference/RefNum</xsl:variable>
<input type=“hidden” name=“{concat(‘XPostChange:’, $xpath)}”
value=“” />
<input class=“ElementStyle” type=“text”
name=“{concat(‘XPostContent:’, $xpath)}” value=“{cbl:Quote/
cbl:QuoteHeader/cbl:QuoteID/cbl:Reference/cbl:RefNum}”
size=“20”
onChange=“javascript:setModified(‘{concat(‘XPostChange:’,
$xpath)}’);” />
− <xsl:variable name=“RefNumErrors”>
− <xsl:call-template name=“ErrorDetector”>
<xsl:with-param name=“Location”
select=“‘/Quote/QuoteHeader/QuoteID/Reference/RefNum
’” />
<xsl:with-param name=“Prefixes” select=“$Prefixes” />
<xsl:with-param name=“ErrorDocument”
select=“$ErrorDocument” />
<xsl:with-param name=“ErrorCodeMaps”
select=“$ErrorCodeMaps” />
</xsl:call-template>
</xsl:variable>
− <xsl:if
test=“string($RefNumErrors)!=string($NotMappedConstant)”
>
− <span class=“ErrorTextSmall”>
[
<xsl:value-of select=“$Error” />
<xsl:value-of select=“$RefNumErrors” />
]:
</span>
</xsl:if>
</TD>
− <TD class=“ElementStyle” width=“50%”>
<xsl:variable name=“xpath”>/Quote/QuoteHeader/
QuoteIssueDate</xsl:variable>
<input type=“hidden” name=“{concat('XPostChange:', $xpath)}”
value=“” />
− <xsl:variable name=“DateErrors”>
− <xsl:call-template name=“ErrorDetector”>
<xsl:with-param name=“Location” select=“‘/Quote/
QuoteHeader/QuoteIssueDate’” />
<xsl:with-param name= “Prefixes” select=“$Prefixes” />
<xsl:with-param name=“ErrorDocument”
select=“$ErrorDocument” />
<xsl:with-param name=“ErrorCodeMaps”
select=“$ErrorCodeMaps” />
</xsl:call-template>
</xsl:variable>
<xsl:param name=“date” select=“cbl:Quote/
cbl:QuoteHeader/cbl:QuoteIssueDate” />
− <xsl:param name=“QuoteIssuedDate”>
<ce:lookup xmlns:ce=“http://www.commerceone.com/xslt/
extensions“ xmlns:maillookup=“urn:mailbox:lookup”
mapname=“maillookup:DateTimeFormatter” value=“$date”
errorvalue=“‘Can not mapped’” />
</xsl:param>
− <xsl:choose>
− <xsl:when
test=“string($DateErrors)!=string($NotMappedConstant)”>
<input class=“ElementStyle” type=“text”
name=“{concat(‘XPostContent:’, $xpath)}”
value=“{cbl:Quote/
cbl:QuoteHeader/cbl:QuoteIssueDate}” size=“15”
onChange=“javascript:setModified(‘{concat(‘XPostChang
e:’, $xpath)}’);” />
− <span class=“ErrorTextSmall”>
[
<xsl:value-of select=“$Error” />
<xsl:value-of select=“$DateErrors” />
]:
</span>
</xsl:when>
− <xsl:otherwise>
<input class=“ElementStyle” type=“text”
name=“{concat(‘XPostContent:’, $xpath)}”
value=“{$QuoteIssuedDate}” size=“15”
onChange=“javascript:setModified(‘{concat(‘XPostChang
e:’, $xpath)}’);” />
</xsl:otherwise>
</xsl:choose>
</TD>
</TR>
<xsl:call-template name=“DisplayParty” />
</TABLE>
<img src=“../img/spacer.gif” alt=“” height=“5” width=“1” />
<BR />
</xsl:template>
− <xsl template name=“DisplayHeader_NoError”>
− <TABLE cellpadding=“1” cellspacing=“0” border=“0” width=“100%”>
− <TR class=“ListHeader”>
− <TD align=“left” colspan=“2” class=“ListHeaderText”>
<xsl:value-of select=“$QuoteHeader” />
</TD>
</TR>
− <TR>
− <TD class=“StatusHeaderSmallNew” width=“50%”>
<span class=“RequiredField”>*</span>
<xsl:value-of select=“$QuoteRefNum” />
</TD>
− <TD class=“StatusHeaderSmallNew” width=“50%”>
<span class=“RequiredField”>*</span>
<xsl:value-of select=“$QuoteIssueDate” />
(
<xsl:value-of select=“string($xm:DATETIMEMASK)” />
)
</TD>
</TR>
− <TR>
− <TD class=“ElementStyle” width=“50%”>
<xsl:variable name=“xpath”>/Quote/QuoteHeader/QuoteID/
Reference/RefNum</xsl:variable>
<input type=“hidden” name=“{concat(‘XPostChange:’, $xpath)}”
value= “”/>
<input class=“ElementStyle” type=“text”
name=“{concat(‘XPostContent:’, $xpath)}” value=“{cbl:Quote/
cbl:QuoteHeader/cbl:QuoteID/cbl:Reference/cbl:RefNum}”
size=“20”
onChange=“javascript:setModified(‘{concat(‘XPostChange:’,
$xpath)}’);” />
</TD>
− <TD class=“ElementStyle” width=“50%”>
<xsl:param name=“date” select=“cbl:Quote/
cbl:QuoteHeader/cbl:QuoteIssueDate” />
<xsl:variable name=“xpath”>/Quote/QuoteHeader/
QuoteIssueDate</xsl:variable>
<input type=“hidden” name=“{concat(‘XPostChange:’, $xpath)}”
value=“” />
− <xsl:param name=“QuoteIssuedDate”>
<ce:lookup xmlns:ce=“http://www.commerceone.com/xslt/
extensions” xmlns:maillookup=“urn:mailbox:lookup”
mapname=“maillookup:DateTimeFormatter” value=“$date”
errorvalue=“‘Can not mapped’” />
</xsl:param>
<input class=“ElementStyle” type=“text”
name=“{concat(‘XPostContent:’, $xpath)}”
value=“{$QuoteIssuedDate}” size=“15”
onChange=“javascript:setModified(‘{concat(‘XPostChange:’,
$xpath)}’);” />
</TD>
</TR>
<xsl:call-template name=“DisplayParty” />
<img src=“../img/spacer.gif” alt=“” height=“5” width=“1” />
<BR />
</TABLE>
</xsl:template>
</xsl:style sheet>
A draft resulting document also may be generated, in the process of producing the user form. This document may be produced according to a declarative transformation of a starting XML document into a draft resulting XML document. The draft resulting document may include starting values from the starting document. It also may include default values for some fields and directions for completing other fields. The draft resulting document may be stored in memory according to a document-object-model (DOM) or another tree-based representation. Alternatively, the draft resulting document may be stored on disk or in memory in a form compatible with Simple API for XML (SAX or SAX2) or another event-based access model. Or, an event-based API can be used to construct a tree, or traverse an in-memory tree. When a draft resulting document is generated, in addition to a form, the draft resulting document may be maintained in memory while the user works from the form and a document TD can be maintained with other state information for the draft resulting document. Alternatively, a document ID and related information can be transmitted with the user form, even in a stateless fashion, and the draft resulting document constructed after the user's updating of the form. A draft resulting document can be transformed with a display transformation to generate the user form. The display transformation may be generated with an XSLT style sheet or another set of declarative data.
Sample excerpts of a document to document transformation 1211 from a request for quotation to quotation follows, including portions of a main processing routine and a party copy routine:
Default.xsl
- <xsl:style sheet version=“1.0”
xmlns:xsl=“http://www.w3.org/1999/XSL/Transform”
xmlns:ext=“http://www.commerceone.com/xmlpres” xmlns:cbl=“urn:x-
commerceone: document:com:commerceone:XCBL30:XCBL30.sox$1.0”
xmlns:xm=“http://www.commerceone.com/xcblmailbox”>
<xsl:output method=“xml” indent=“yes” omit-xmldeclaration=“yes” />
<xsl:include href=“reference_copy.xsl” />
<xsl:include href=“party_copy.xsl” />
<xsl:include href=“lineitemnum_copy.xsl” />
<xsl:include href=“itemidentifiers_copy.xsl” />
<xsl:include href=“identifier_copy.xsl” />
<xsl:include href=“totalquantity_copy.xsl” />
- <xsl:template match=“/”>
- <xsl:processing-instruction name=“soxtype”>
<xsl:text>urn:xcommerceone:
document:com:commerceone:XCBL30:XCBL30.sox$1.0</xsl:text>
</xsl:processing-instruction>
- <Quote>
<xsl:apply-templates select=“cbl:RequestForQuotation/
cbl:RequestQuoteHeader” />
<xsl:apply-templates select=“cbl:RequestForQuotation/
cbl:ListOfRequestQuoteDetails” />
<xsl:apply-templates select=“cbl:RequestForQuotation/
cbl:RequestQuoteSummary” />
</Quote>
</xsl:template>
- <xsl:template match=“cbl:RequestQuoteHeader”>
<xsl:call-template name=“OutputQuoteHeader” />
</xsl:template>
- <xsl:template match=“cbl:ListOfRequestQuoteDetails”>
<xsl:call-template name=“OutputListOfQuoteDetails” />
</xsl:template>
- <xsl:template match=“cbl:RequestQuoteSummary”>
<xsl:call-template name=“OutputQuoteSummary” />
</xsl:template>
- <xsl:template name=“OutputQuoteHeader”>
- <QuoteHeader>
<QuoteIssueDate />
- <QuoteID>
<xsl:apply-templates select=“cbl:RequestQuoteID” />
</QuoteID>
- <QuoteParty>
<xsl:apply-templates select=“cbl:RequestQuoteParty” />
</QuoteParty>
<xsl:call-template name=“OutputQuoteCurrency” />
<xsl:call-template name=“OutputQuoteTermsOfPayment” />
</QuoteHeader>
</xsl:template>
- <xsl:template name=“OutputListOfQuoteDetails”>
- <ListOfQuoteDetails>
- <xsl:for-each select=“cbl:RequestQuoteDetails”>
- <QuoteDetails>
<xsl:call-template name=“OutputQuoteItemType” />
<xsl:call-template name=“OutputQuoteItemDetail” />
</QuoteDetails>
</xsl:for-each>
</ListOfQuoteDetails>
</xsl:template>
- <xsl:template name=“OutputQuoteSummary”>
- <QuoteSummary>
<xsl:copy-of select=“cbl:TotalNumberOfLineItems” />
</QuoteSummary>
</xsl:template>
- <xsl:template name=“OutputQuoteItemType”>
- <QuoteItemType>
- <QuoteType>
<QuoteTypeCoded />
</QuoteType>
</QuoteItemType>
</xsl:template>
- <xsl:template name=“OutputQuoteItemDetail”>
- <QuoteItemDetail>
<xsl:apply-templates
select=“cbl:RequestQuoteItemDetail/cbl:BaseItemDetail” />
</QuoteItemDetail>
- <QuotePricingDetail>
- <PricingDetail>
- <ListOfPrice>
- <Price>
- <UnitPrice>
<UnitPriceValue />
- <UnitOfMeasurement>
<UOMCoded />
</UnitOfMeasurement>
</UnitPrice>
</Price>
</ListOfPrice>
- <TotalValue>
- <MonetaryValue>
<MonetaryAmount />
</MonetaryValue>
</TotalValue>
</PricingDetail>
</QuotePricingDetail>
</xsl:template>
- <xsl:template match=“cbl:BaseItemDetail”>
<xsl:call-template name=“CopyLineItemNum” />
<xsl:call-template name=“CopyItemIdentifiers” />
<xsl:call-template name=“CopyTotalQuantity” />
</xsl:template>
- <xsl:template name=“OutputQuoteCurrency”>
- <xsl:if test=“cbl:RequestQuoteCurrency/cbl:Currency/
cbl:CurrencyCoded”>
- <QuoteCurrency>
<xsl:copy-of select=“cbl:RequestQuoteCurrency/ cbl:Currency” />
</QuoteCurrency>
</xsl:if>
</xsl:template>
- <xsl:template name=“OutputQuoteTermsOfPayment”>
- <xsl:if test=“cbl:RequestQuoteTermsOfPayment”>
- <QuoteTermsOfPayment>
- <PaymentInstructions>
<xsl:call-template name=“OutputQuotePaymentTerms” />
<xsl:call-template name=“OutputQuotePaymentMethod” />
</PaymentInstructions>
</QuoteTermsOfPayment>
</xsl:if>
</xsl:template>
- <xsl:template name=“OutputQuotePaymentTerms”>
- <xsl:for-each
select=“cbl:RequestQuoteTermsOfPayment/cbl:PaymentInstructions/
cbl:PaymentTerms”>
- <PaymentTerms>
- <xsl:for-each select=“cbl:PaymentTerm”>
- <PaymentTerm>
<xsl:copy-of select=“cbl:PaymentTermCoded” />
<xsl:copy-of select=“cbl:PaymentTermCodedOther” />
<xsl:copy-of select=“cbl:PaymentTermValue” />
<xsl:copy-of select=“cbl:PaymentTermDetails” />
</PaymentTerm>
</xsl:for-each>
</PaymentTerms>
</xsl:for-each>
</xsl:template>
- <xsl:template name=“OutputQuotePaymentMethod”>
- <xsl:for-each select=“cbl:RequestQuoteTermsOfPayment/
cbl:PaymentInstructions/cbl:PaymentMethod”>
- <PaymentMethod>
<xsl:copy-of select=“cbl:PaymentMeanCoded” />
<xsl:copy-of select=“cbl:PaymentMeanCodedOther” />
<xsl:copy-of select=“cbl:PaymentMeanReference” />
<xsl:copy-of select=“cbl:PaymentSystemCoded” />
<xsl:copy-of select=“cbl:PaymentSystemCodedOther” />
<xsl:copy-of select=“cbl:OriginatingFIAccount” />
<xsl:copy-of select=“cbl:ReceivingFIAccount” />
<xsl:copy-of select=“cbl:CardInfo” />
</PaymentMethod>
</xsl:for-each>
</xsl:template>
- <xsl:template match=“cbl:RequestQuoteID”>
<xsl:call-template name=“CopyReference” />
</xsl:template>
- <xsl:template match=“cbl:RequestQuoteParty”>
- <OrderParty>
- <BuyerParty>
<xsl:apply-templates select=“cbl:OrderParty/
cbl:BuyerParty/cbl:Party” />
</BuyerParty>
- <SellerParty>
<xsl:apply-templates select=“cbl:OrderParty/
cbl:SellerParty/cbl:Party” />
</SellerParty>
</OrderParty>
</xsl:template>
- <xsl:template match=“cbl:Party”>
<xsl:call-template name=“CopyParty” />
</xsl:template>
</xsl:style sheet>
Party copy.xsl
- <xsl:style sheet version=“1.0”
xmlns:xsl=“http://www.w3.org/1999/XSL/Transform”
xmlns:ext=“http://www.commerceone.com/xmlpres” xmlns:cbl=“urn:x-
commerceone: document:com:commerceone:XCBL30:XCBL30.sox$1.0”
xmlns:xm=“http://www.commerceone.com/xcblmailbox”>
- <xsl:template name=“CopyParty”>
- <Party>
<xsl:apply-templates select=“cbl:PartyID” />
<xsl:call-template name=“CopyNameAddress” />
</Party>
</xsl:template>
- <xsl:template match=“cbl:PartyID”>
- <PartyID>
<xsl:apply-templates select=“cbl:Identifier” />
</PartyID>
</xsl:template>
- <xsl:template name=“CopyNameAddress”>
<xsl:copy-of select=“cbl:NameAddress” />
</xsl:template>
</xsl:style sheet>
The user acts upon the form 141. Fields are added, completed or changed. More than one iteration may be required, for instance, if a user adds a line item to a quotation. When the user is ready, the form is posted to the server for validation. One or more types of validation can be applied, such as field validation against a schema (e.g., for well-formedness and valid ranges) and business processing validation against a rule base. For instance, a SOX-compliant xCBL schema and a set of Schematron rules can be used for validation. In
Excerpts from a sample of a user form 141 that produced the sample screen in
The sequence in
One or more errors in the primary document are detected 2004. A secondary self-describing, structured document 2012 including the detected errors is generated. For the detected errors, an error identifier and a path specification identifying a node within the primary document corresponding to one or more of the detected errors are generated. The primary 2001 and secondary 2012 documents are merged 2005 for display 2006. In one embodiment, the secondary document is an XML document. An enhanced version of the XSLT document ( ) function is used to allow retrieval of the secondary document containing error text. The XMLPres component, which implements the XSLT functionality, is an enhanced version of Apache Foundation's Xalan. This component takes into account various concepts such as name spaces in Sox documents and polymorphism. Extension of the document ( ) function enables the loading of an external document to be specified by the invoker.
A context-based search facility is user configurable. Database configuration interfaces may be used for specifying those fields to be indexed. The user interface can be configured to provide user-friendly names to be displayed corresponding to XPath or field element name representations. Configuring the user interface permits fields that have different names in different document types to begin a common, user-friendly name at the user interface.
XPath provides a unique way to identify a field inside a XML document, but it may not be meaningful to an end user. As illustrated in
While the preceding examples are cast in primarily in terms of a method, devices and systems employing this method are easily understood. An electronically readable medium, such as a DVD, CD, memory module, magnetic disk or magnetic tape containing a program capable of practicing aspects the claimed method is one such device. A computer system comprising one or more servers and/or workstations having memory loaded with a program practicing the claimed method is another such device.
While the present invention is disclosed by reference to the preferred embodiments and examples detailed above, it is understood that these examples are intended in an illustrative rather than in a limiting sense. It is contemplated that modifications and combinations will readily occur to those skilled in the art, which modifications and combinations will be within the spirit of the invention and the scope of the following claims.
Wei, Yang, Sulistio, Muljadi, Schwarzhoff, Kelly Lane, Ding, Yuan
| Patent | Priority | Assignee | Title |
| 10061754, | Dec 18 2001 | International Business Machines Corporation | Method and apparatus for declarative updating of self-describing, structured documents |
| 8566702, | Sep 20 2010 | Malikie Innovations Limited | Methods and systems of outputting content of interest |
| 9836438, | Sep 20 2010 | Malikie Innovations Limited | Methods and systems of outputting content of interest |
| Patent | Priority | Assignee | Title |
| 6591260, | Jan 28 2000 | Red Hat, Inc | Method of retrieving schemas for interpreting documents in an electronic commerce system |
| 6650433, | Jan 25 2000 | CIMPRESS USA INCORPORATED | Managing print jobs |
| 7010533, | Feb 15 1999 | Panasonic Intellectual Property Corporation of America | E-mail preparation device, terminal device, information forwarding system, and program recording medium |
| 7036072, | Dec 18 2001 | International Business Machines Corporation | Method and apparatus for declarative updating of self-describing, structured documents |
| 7058886, | Dec 18 2001 | International Business Machines Corporation | Method and apparatus for declarative error handling and presentation |
| 7237191, | Dec 18 2001 | PERFECT COMMERCE HOLDINGS, LLC | Method and apparatus for generic search interface across document types |
| 7278096, | Dec 18 2001 | Open Invention Network | Method and apparatus for declarative updating of self-describing, structured documents |
| 7305614, | Jul 17 2001 | International Business Machines Corporation | Interoperable retrieval and deposit using annotated schema to interface between industrial document specification languages |
| 7415669, | Feb 27 2001 | PERFECT COMMERCE HOLDINGS, LLC | Method and apparatus for viewing electronic commerce-related documents |
| 7707492, | Jun 14 1999 | Thomson Reuters Enterprise Centre GmbH | System for converting data to a markup language |
| 20020069083, | |||
| 20020099735, | |||
| 20020116421, | |||
| 20020135621, | |||
| 20020143823, | |||
| 20020147847, | |||
| 20040205615, | |||
| 20040205644, | |||
| 20060156224, |
| Executed on | Assignor | Assignee | Conveyance | Frame | Reel | Doc |
| Oct 01 2007 | Open Invention Network, LLC | (assignment on the face of the patent) | / |
| Date | Maintenance Fee Events |
| Oct 14 2015 | M1551: Payment of Maintenance Fee, 4th Year, Large Entity. |
| Dec 23 2019 | REM: Maintenance Fee Reminder Mailed. |
| Jun 08 2020 | EXP: Patent Expired for Failure to Pay Maintenance Fees. |
| Date | Maintenance Schedule |
| May 01 2015 | 4 years fee payment window open |
| Nov 01 2015 | 6 months grace period start (w surcharge) |
| May 01 2016 | patent expiry (for year 4) |
| May 01 2018 | 2 years to revive unintentionally abandoned end. (for year 4) |
| May 01 2019 | 8 years fee payment window open |
| Nov 01 2019 | 6 months grace period start (w surcharge) |
| May 01 2020 | patent expiry (for year 8) |
| May 01 2022 | 2 years to revive unintentionally abandoned end. (for year 8) |
| May 01 2023 | 12 years fee payment window open |
| Nov 01 2023 | 6 months grace period start (w surcharge) |
| May 01 2024 | patent expiry (for year 12) |
| May 01 2026 | 2 years to revive unintentionally abandoned end. (for year 12) |