|Publication number||US7627607 B2|
|Application number||US 11/498,219|
|Publication date||Dec 1, 2009|
|Filing date||Aug 2, 2006|
|Priority date||Aug 6, 2003|
|Also published as||US7313562, US20050033750, US20060271578, US20070033207, US20070055682|
|Publication number||11498219, 498219, US 7627607 B2, US 7627607B2, US-B2-7627607, US7627607 B2, US7627607B2|
|Inventors||John Neil Cobb, Yeow Loong Lee|
|Original Assignee||At&T Intellectual Property I, L.P.|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (40), Classifications (19), Legal Events (4)|
|External Links: USPTO, USPTO Assignment, Espacenet|
This application is a divisional application of, and claims priority from, U.S. application Ser. No. 10/635,419, filed Aug. 6, 2003, the contents of which are hereby incorporated in their entirety.
This disclosure relates, in general, to rhetorical content management systems and methods for their use.
Content management is useful for providing a consistent image through various content delivery methods. For example, content management may be useful in providing a consistent product description across multiple sales and marketing mediums such as websites, proposals, brochures, and other documents.
However, content management becomes a significant problem for large organizations having multiple products or product lines. A large amount of content is provided to a large number of users. These problems may be further exacerbated by variances in regional availability, market targeting, and the greater demand for content through large sales channels. Delivery of suitable content is often slow.
In addition, content creation is a significantly expensive process. Initial creation is expensive. After initial content creation, the content may not be suitable for various purposes. As such, expenses increase as content is manually adapted for various uses.
Some organizations rely on multiple content management systems. Each system is managed by a different section. As such, content is created more than once and varies between sections. Therefore, it is difficult to create content that is consistent and accurate.
For large entities with extensive product lines, content management becomes a large and expensive process. As such, an improved content management system would be desirable.
The present disclosure is directed generally to a content management system, a method of content management, a rhetorical content model, and automated methods of generating proposals and other documents based thereon.
In a particular illustrative embodiment, a method of managing content is disclosed. The method includes receiving a request from a content application for content associated with a content subject. The method also includes selectively retrieving a plurality of fields of a record stored at a database, wherein the record is associated with the content subject and wherein each of the plurality of fields includes a content segment. Further, the method includes converting each content segment to a first format associated with a first content application, where the first content application includes at least one of the content segments with content having a first technical level. The method also includes converting each content segment to a second format associated with a second content application, where the second content application includes at least one of the content segments with content having a second technical level that is greater in technical specificity than the first technical level.
In accordance with another particular embodiment, a content management system is disclosed and includes a content server configured to selectively retrieve at least one content segment of a plurality of content segments stored at a database communicating with the content server. The content server is configured to convert the at least one content segment to a first format and to provide a first data file that includes the at least one content segment to a first content application, wherein the first content application includes the content segment with content having a first technical level. The content server is configured to convert the at least one content segment to a second format and to provide a second data file that includes the at least one content segment to a second content application, where the second content application includes the content segment with content having a second technical level that is greater in technical specificity than the first technical level.
In accordance with another embodiment, a method of content management is disclosed and includes requesting at least one content segment associated with a content subject from a content server. The method also includes receiving at least one grammatical syntax element from the content server, wherein the content server selectively retrieves the at least one grammatical syntax element from a plurality of grammatical syntax elements stored at a database. Further, the method includes constructing first content related to the content subject, the first content including the at least one grammatical syntax element and a first marketing brand. The method also includes constructing second content related to the content subject, the second content including the at least one grammatical syntax element and a second marketing brand. The method also includes delivering the first content to the first content application and the second content to the second content application over the distributed network via a gateway application.
In accordance with another particular embodiment, a content management system is disclosed and includes an application server configured to communicate with a distributed network to receive requests associated with a content subject from a first content application and a second content application. The application server is configured to send requests to a content server for content segments associated with the content subject. The application server is configured to communicate with the content server to receive a tag-segmented data file, the tag-segmented data file including a plurality of content segments associated with the content subject. The application server is configured to selectively construct first content relating to the content subject, the first content including at least one of the plurality of content segments and a first marketing brand. The application server is configured to selectively construct second content relating to the content subject, the second content including at least one of the plurality of content segments and a second marketing brand. The application server is configured to deliver the first content to the first content application and the second content to the second content application over the distributed network via a gateway application.
The input tool 102 is used to gather content segments and store those segments in a database 104. The content segments may, for example, be sentence fragments, phrases, nouns, sentences, and paragraphs. In one exemplary embodiment, sentence fragments are entered, following a specific grammatical format that fulfills a specified rhetorical purpose. Using the rhetorical format, parts of a sentence may be gathered, stored and associated as fields in the content database 104. Rhetorical principles control the development of the syntax from the grammatical elements and drive the deployment of the content to the application based on the communication function that the write wants to achieve.
The database 104 may be a database such as an OracleŽ or SQL database. The database 104 stores records or file references. Each record is associated with a content subject and may have multiple fields. The fields may contain sentence fragments, phrases, sentences, nouns, and paragraphs. This content data may be selectively used to construct content associated with the content subject.
The content server 106 is coupled to the database 104 and accesses the records associated with the content subjects. Applications such as product profiler 108, proposal builder 110, and e-brochure builder 112 access the content server 106, requesting content associated with a content subject. The content server 106 accesses the database 104 to selectively retrieve requested fields of the record associated with the requested content subject. The content server 106 may provide the content elements in various formats, including a data record set and an XML document.
The applications may construct content using the various formats or models. Some of the fields in the record may, for example, follow a rhetorical model. In this example, the model utilizes sentence elements having a specific grammatical form designed to meet a particular rhetorical or communication function. The sentence elements or grammatical syntax rules may be used to construct a sentence. In one exemplary embodiment, the rhetorical model may be used to form a sentence having three elements, a product name, product class, and product description as shown below. The rhetorical/communication function this grammatical contruct is designed to achieve is DEFINE.
<<Product name>> is a <<product class>> that <<product description>>.
To produce a grammatically correct sentence, the elements follow specific grammatical forms. For example, the product name is a noun, the product class may be a noun that agrees with the singular verb “is” and singular article “a”, and the product description may be a phrase beginning with a third-person singular active verb. An example is <<A chair>> is a <<piece of furniture>> that <<has four legs, a platform for sitting, and a back to lean against>>.
Sentence elements may be stored in the database 104. Fields within records associated with content subjects may store grammatical syntax elements that may be used to create sentences based on one or more rhetorical formats. For example, the product name and product class may be used to make a sentence. In another example, the product name field and product description may be used to build another sentence. Alternately, the product name may be used with another element to build a third sentence.
In addition, fields within the record may be used to store phrases, sentences, or paragraphs that fulfill a specified rhetorical/communication function. For example, fields may store teaser sentences, point statements, illustrative descriptions, analogy statements, and feature statements. For example, sentences or phrases may relate to additional differentiators such as differentiating details such as physical or conceptual differences to other products in a class, comparisons with older technologies, examples, inventories, and analogies. In another example, a point statement may be included that further describes the product such as an advantage or usage from the target audience's point of view.
The database may further store contexts in which a content or content element is applicable. For example, content elements relating to the same content subject may be provided for different markets, regions, and branding efforts. In one exemplary embodiment, different legal statements may be provided for use with content based on the region. In another example, different content elements may be provided for marketing to different target markets. In a further example, different content elements such as product names may be associated with a content subject for different branding efforts. Different content elements may be provided for various technical levels as well.
The fields stored within the records may then be queried to selectively retrieve elements that may be utilized to create content. One exemplary application is the product profiler system 108. The content server 106 provides a tagged-segmented data file, such as an extensible markup language (XML) file, including the requested data elements to the product profiler system 108. The product profiler system 108 interprets the tagged-segmented data file to produce content for delivery through a network such as via a web page.
In other exemplary embodiments such as proposal builder 110 or e-brochure builder 112, the content server 106 may provide the content elements as a data record set. The applications 110 and 112 interpret the data record set, selectively utilizing the content elements to develop context-specific content. The content may then be provided in a document, flash file, PDF, or other electronic format.
In one exemplary embodiment, the content management system may be integrated with enterprise architecture. Applications may reside on a user end of the architecture while the content server and database reside in a business services section. In other embodiments, the system may be implemented on an intranet and use browser technology.
In this manner, content elements associated with a content subject may be reused in various contexts or for various purposes. As such, the content elements may be re-purposed and utilized automatically.
Upon receiving a request from the gateway program 214, the application server 200 may acquire an extensible markup language (XML) file 202 associated with the requested content subject. The XML may have tags that identify the elements. The XML file 202 may be interpreted by an XML parser 216. The XML file 202 may be associated with a document type definition (DTD) file 204 and further interpreted in accordance with the document type definition (DTD) file 204. The application server 200 may also include an XSL file 206 as interpreted by an XSL processor 218. Together, the XML parser 216 and the XSL processor 218 provide content elements to the gateway program 214. The gateway program 214 assembles the content elements into content included in the web pages.
Each web page may utilize different elements derived from the grammatical syntax fields stored in the database and transferred utilizing the XML file 202. In this manner, the content elements may be utilized in accordance with the intended purpose of the content.
Data associated with the product may be subdivided into sections 304, each section having an associated entry page or anchor within the displayed page. The sections may, for example, be subdivisions associated with what a product does, how it works, what it is, general information, branding information, frequently asked questions associated with the product, teasers, product features, advantages, applications, implementation, success stories, components, diagrams, options, availability, legal notices, white papers, and other information.
The interface may be further subdivided into tabbed sections that define certain grammatical structures for a particular content subject, using tabs 306. These tabbed sections may be displayed as individual web pages and each section may have multiple tab pages associated with it. In addition, each page may include an element such as a button. The pages may include buttons such as a view button 308, an add button 310, and an edit button 312. The view button 308 may facilitate a display of content elements associated with the product name 302. The add button 310 may add content entered into the page to the record in the database. The edit button 312 may, for example, unlock text entry fields, permitting editing of text associated with the content elements. Alternately, other buttons may be used to manipulate records within the database.
In this exemplary embodiment, two content elements are shown. Element 314 includes a description of the grammar rules to be applied when entering text. The element 314 may additionally include a text entry form element 316 and a size element 318 that indicates either total size permitted in the text entry element 316, the number of characters remaining for use in the text entry element 316, or the number of characters used in the text entry element 316. For example, element 314 may be a sentence or product tease designed to grab the attention of a potential purchaser. The grammatical and content-guidance rules associated with element 314 may require or suggest that the element be entered as a sentence or a question. The text entry element 316 may, for example, be limited to a size of 250 characters. As the text entry element 316 is used, the number of characters remaining may be displayed in the size element 318.
Element 320 may, for example, be a product classification. The product classification may be used in a rhetorical or classical rhetorical format and require an associated verb, article, and structured phrase or noun. In the exemplary embodiment, a drop-down menu is provided for selecting a verb form that agrees with a controlling grammatical element 322 such as “is” or “are”. Another drop-down menu 324 is provided for selecting an article such as “a” or “an”. A text entry form element 326 is provided for entering the product class syntax. In addition, a size element box 328 may be provided. For example, in a classic rhetorical format, a sentence may be constructed using the product name 302, the verb selected in menu 322, the article selected in menu 324, and the text in the text entry form element 326. The sentence would read: <<Product name>> is/are a/an <text entry>>. The verb selected in menu 322, the article selected in menu 324, and the text of text entry element 326 may be stored in a database and reapplied as needed for specific purposes.
Other elements may be entered such as product descriptions, teasers, descriptions of how a system works, success stories, feature names, and point statement sentences. These elements may also have an associated field in the records of the database.
The content management system may then code the stored text and convert it into structured format-supporting rhetorical elements as shown at step 406. For example, the content management system may query the records and create data record sets. In another embodiment, the content management system may query the stored records and formulate tag-structured data files such as XML files for use by other applications. The content management system may then render an electronically displayable document including at least one of the stored rhetorical elements as shown at step 408. For example, the content management system may display a web page utilizing some of the rhetorical data elements. Alternately, the content may be re-purposed and utilized for brochures, proposals, or other documents needing to fulfill a similar rhetorical/communication purpose. The content used in the brochures or proposals may utilize different rhetorical elements from those utilized in providing content for web pages, or in some cases, use the same elements or subsets, depending on the space available and the degree of content needed.
Another rhetorical structure, such as the comparison between the old and new as shown in block 504, may also use the product name. The rhetorical structure 504 may utilize a key benefit field and comparable product field that have syntax or grammatical structures different than those of the product class or key differentiator. For example, the key differentiator may have a different format than the key benefit. The different syntax for the comparison old/new is based on the rhetorical function of comparison. The payoff statement may be a benefit. The differing syntax would let a re-user emphasize this benefit over others and add flexibility to the application's discussion of the content.
Other rhetorical structures such as rhetorical structure 506 may utilize sentence syntax structures. Each sentence syntax structure may have a specific purpose. Alternately, such as in how does rhetorical structure 508, a rhetorical structure may be formulated using syntax elements that constitute nouns or phrases as well as syntax structures that include sentences and paragraphs. Syntax structure elements such as the product name may be reused in many rhetorical structures. Other elements may be specific to a given rhetorical structure. Further, these rhetorical structures and the syntax elements may be selectively utilized for different purposes.
An e-brochure may be built utilizing the comparison between the old and new 504 as well as a supplemental comparison between the old and new 506. Alternately, a proposal builder 514 may utilize the classical definition structure 502, the product how does rhetorical structure 508, and the features rhetorical structure 510. In this manner, elements and structures associated with a content subject may be selectively utilized to produce content for differing purposes.
Additional files such as XSL files may specify how a sentence or content is to be constructed using the content elements of the XML file. The actual output is shown.
The above disclosed subject matter is to be considered illustrative, and not restrictive, and the appended claims are intended to cover all such modifications, enhancements, and other embodiments which fall within the true spirit and scope of the present invention. Thus, to the maximum extent allowed by law, the scope of the present invention is to be determined by the broadest permissible interpretation of the following claims and their equivalents, and shall not be restricted or limited by the foregoing detailed description.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US5537586 *||May 6, 1994||Jul 16, 1996||Individual, Inc.||Enhanced apparatus and methods for retrieving and selecting profiled textural information records from a database of defined category structures|
|US5819260||Jan 22, 1996||Oct 6, 1998||Lexis-Nexis||Phrase recognition method and apparatus|
|US6026388 *||Aug 14, 1996||Feb 15, 2000||Textwise, Llc||User interface and other enhancements for natural language information retrieval system and method|
|US6038573 *||Apr 4, 1997||Mar 14, 2000||Avid Technology, Inc.||News story markup language and system and process for editing and processing documents|
|US6112168||Oct 20, 1997||Aug 29, 2000||Microsoft Corporation||Automatically recognizing the discourse structure of a body of text|
|US6185587 *||Jun 19, 1998||Feb 6, 2001||International Business Machines Corporation||System and method for building a web site with automated help|
|US6199034||Apr 14, 1998||Mar 6, 2001||Oracle Corporation||Methods and apparatus for determining theme for discourse|
|US6230173 *||Jul 17, 1995||May 8, 2001||Microsoft Corporation||Method for creating structured documents in a publishing system|
|US6263336||Jan 30, 1998||Jul 17, 2001||Seiko Epson Corporation||Text structure analysis method and text structure analysis device|
|US6349316||Apr 8, 1999||Feb 19, 2002||Microsoft Corporation||Document summarizer for word processors|
|US6353824||Nov 18, 1997||Mar 5, 2002||Apple Computer, Inc.||Method for dynamic presentation of the contents topically rich capsule overviews corresponding to the plurality of documents, resolving co-referentiality in document segments|
|US6374271||Sep 26, 1997||Apr 16, 2002||Fuji Xerox Co., Ltd.||Hypermedia document authoring using a goals outline and a presentation outline|
|US6513063||Mar 14, 2000||Jan 28, 2003||Sri International||Accessing network-based electronic information through scripted online interfaces using spoken input|
|US6523061||Jun 30, 2000||Feb 18, 2003||Sri International, Inc.||System, method, and article of manufacture for agent-based navigation in a speech-based data navigation system|
|US6549922||Oct 1, 1999||Apr 15, 2003||Alok Srivastava||System for collecting, transforming and managing media metadata|
|US6553373||Nov 29, 2001||Apr 22, 2003||Apple Computer, Inc.||Method for dynamically delivering contents encapsulated with capsule overviews corresonding to the plurality of documents, resolving co-referentiality related to frequency within document, determining topic stamps for each document segments|
|US6574660||Dec 28, 1999||Jun 3, 2003||Intel Corporation||Intelligent content delivery system based on user actions with client application data|
|US6675159||Jul 27, 2000||Jan 6, 2004||Science Applic Int Corp||Concept-based search and retrieval system|
|US6901402||Jun 18, 1999||May 31, 2005||Microsoft Corporation||System for improving the performance of information retrieval-type tasks by identifying the relations of constituents|
|US7013259||Jun 30, 2000||Mar 14, 2006||Fuji Xerox Co., Ltd.||System and method for teaching writing using microanalysis of text|
|US7092974||Mar 12, 2003||Aug 15, 2006||Right Hemisphere Limited||Digital asset server and asset management system|
|US7133862 *||Dec 5, 2001||Nov 7, 2006||Xerox Corporation||System with user directed enrichment and import/export control|
|US7266553 *||Jul 1, 2002||Sep 4, 2007||Microsoft Corporation||Content data indexing|
|US7284191 *||Dec 5, 2001||Oct 16, 2007||Xerox Corporation||Meta-document management system with document identifiers|
|US7284239 *||Jun 6, 2000||Oct 16, 2007||Adobe Systems Incorporated||Transforming server-side processing grammars|
|US7334216 *||Jan 31, 2003||Feb 19, 2008||Sosy, Inc.||Method and apparatus for automatic generation of information system user interfaces|
|US20020032709 *||Sep 29, 1998||Mar 14, 2002||Rick Gessner||Network client accepts and processes replaceable document type definition components containing corresponding grammars and transforms documents according the same|
|US20020095411 *||Jan 16, 2001||Jul 18, 2002||Caldwell David Edward||Natural language product comparison guide synthesizer|
|US20020102524 *||Jan 26, 2001||Aug 1, 2002||Rizzi Steven D.||System and method for developing instructional materials using a content database|
|US20020107776 *||Feb 5, 2001||Aug 8, 2002||Homestore.Com||System and method for anonymous lead generation and management|
|US20030033288 *||Dec 5, 2001||Feb 13, 2003||Xerox Corporation||Document-centric system with auto-completion and auto-correction|
|US20030065533||Sep 27, 2002||Apr 3, 2003||Sap Ag||Portable business information content and management system|
|US20030126136||Jun 24, 2002||Jul 3, 2003||Nosa Omoigui||System and method for knowledge retrieval, management, delivery and presentation|
|US20040034520 *||Mar 4, 2003||Feb 19, 2004||Irene Langkilde-Geary||Sentence generator|
|US20050033750||Aug 6, 2003||Feb 10, 2005||Sbc Knowledge Ventures, L.P.||Rhetorical content management system and methods|
|US20050193335 *||Apr 29, 2005||Sep 1, 2005||International Business Machines Corporation||Method and system for personalized content conditioning|
|US20060235738 *||Apr 15, 2005||Oct 19, 2006||Judy Doyle||Multi-authoring within benefits content system|
|US20060271578||Aug 8, 2006||Nov 30, 2006||Sbc Knowledge Ventures, L.P.||Rhetorical content management system and methods|
|US20070033207||Aug 2, 2006||Feb 8, 2007||Sbc Knowledge Ventures, L.P.||Rhetorical content management system and methods|
|US20070067371||Sep 19, 2005||Mar 22, 2007||Sbc Knowledge Ventures, L.P.||Database structure and method|
|U.S. Classification||1/1, 707/999.104, 707/999.107, 707/999.003, 707/999.01, 707/999.001, 707/999.1|
|International Classification||G06F17/30, G06F17/00|
|Cooperative Classification||Y10S707/99933, Y10S707/99948, Y10S707/99943, Y10S707/99931, Y10S707/99945, Y10S707/917, G06F17/30607, G06F17/30654|
|European Classification||G06F17/30T2F4, G06F17/30S8T|
|Jul 28, 2009||AS||Assignment|
Owner name: SBC KNOWLEDGE VENTURES, L.P., NEVADA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:COBB, JOHN NEIL;LEE, YEOW LOONG;REEL/FRAME:023013/0311;SIGNING DATES FROM 20031204 TO 20031211
|Mar 18, 2013||FPAY||Fee payment|
Year of fee payment: 4
|Jul 14, 2017||REMI||Maintenance fee reminder mailed|
|Jan 1, 2018||LAPS||Lapse for failure to pay maintenance fees|
Free format text: PATENT EXPIRED FOR FAILURE TO PAY MAINTENANCE FEES (ORIGINAL EVENT CODE: EXP.)