Search Images Maps Play YouTube News Gmail Drive More »
Sign in
Screen reader users: click this link for accessible mode. Accessible mode has the same essential features but works better with your reader.

Patents

  1. Advanced Patent Search
Publication numberUS20060271578 A1
Publication typeApplication
Application numberUS 11/500,683
Publication dateNov 30, 2006
Filing dateAug 8, 2006
Priority dateAug 6, 2003
Also published asUS7313562, US7627607, US20050033750, US20070033207, US20070055682
Publication number11500683, 500683, US 2006/0271578 A1, US 2006/271578 A1, US 20060271578 A1, US 20060271578A1, US 2006271578 A1, US 2006271578A1, US-A1-20060271578, US-A1-2006271578, US2006/0271578A1, US2006/271578A1, US20060271578 A1, US20060271578A1, US2006271578 A1, US2006271578A1
InventorsJohn Cobb, Yeow Lee
Original AssigneeSbc Knowledge Ventures, L.P.
Export CitationBiBTeX, EndNote, RefMan
External Links: USPTO, USPTO Assignment, Espacenet
Rhetorical content management system and methods
US 20060271578 A1
Abstract
A system and method of managing content are disclosed. In one embodiment, the method includes receiving input from an input tool, the input including a plurality of grammatically-structured text elements related to a content subject. The method also includes storing the plurality of grammatically-structured text elements as a plurality of fields of a record associated with the content subject and sending the plurality of fields to a content server in response to a request. The content server converts the grammatically-structured text elements into structured-format rhetorical elements and sends the structured-format rhetorical elements to a first application that integrates the structured-format rhetorical elements into a first electronically distributable document having a first technical level and to a second application that integrates the structured-format rhetorical elements into a second electronically distributable document having a second technical level that is greater in technical specificity than the first technical level.
Images(6)
Previous page
Next page
Claims(19)
1. A method of content management, the method comprising:
receiving input from an input tool, wherein the input includes a plurality of grammatically-structured text elements related to a content subject;
storing the plurality of grammatically-structured text elements as a plurality of fields of a record associated with the content subject; and
sending the plurality of fields to a content server in response to a request, wherein the content server converts the grammatically-structured text elements into structured-format rhetorical elements and sends the structured-format rhetorical elements to a first application that integrates the structured-format rhetorical elements into a first electronically distributable document having a first technical level and sends the structured-format rhetorical elements to a second application that integrates the structured-format rhetorical elements into a second electronically distributable document having a second technical level that is greater in technical specificity than the first technical level.
2. The method of claim 1, further comprising associating a context with at least one of the grammatically-structured text elements, wherein the context indicates a market, geographic region, marketing brand, technical level, or any combination thereof.
3. The method of claim 1, wherein the grammatically-structured text elements include a noun, a verb, a phrase, a sentence, a teaser statement, a point statement, an illustrative description, an analogy statement, a feature statement, a product differentiator, or any combination thereof.
4. The method of claim 1, wherein each of the first and second electronically distributable documents integrates the structured-format rhetorical elements into at least one sentence that includes a comparison statement relating to a product associated with the content subject.
5. A content management system, comprising:
a database configured to communicate with an input tool to receive input, wherein the input includes a plurality of grammatical syntax elements related to a content subject;
wherein the database is configured to store a plurality of records, at least one record of the plurality of records including a plurality of fields storing the plurality of grammatical syntax elements associated with the content subject, each of the plurality of grammatical syntax elements having a rhetorical structure to facilitate selective assembly into at least one sentence; and
wherein the database is configured to send at least one grammatical syntax element of the plurality of grammatical syntax elements to a content server in response to a request, wherein the content server converts the at least one grammatically-structured text element into at least one structured-format rhetorical element and sends the at least one structured-format rhetorical element to a first application that integrates the at least one structured-format rhetorical element into a first electronically distributable document having a first technical level and sends the at least one structured-format rhetorical element to a second application that integrates the at least one structured-format rhetorical element into a second electronically distributable document having a second technical level that is greater in technical specificity than the first technical level.
6. The system of claim 4, wherein each of the first and second electronically distributable includes a plurality of sentences derived from the at least one grammatical syntax element.
7. The system of claim 4, wherein the at least one grammatical syntax element includes a product class.
8. The system of claim 4, wherein the at least one grammatical syntax element includes a product description including a verb having a specified verb tense.
9. The system of claim 4, wherein the at least one grammatical syntax element includes a phrase associated with a specified verb and article.
10. A method of content management, the method comprising:
storing a first computer retrievable grammatical syntax element associated with a rhetorical structure in a first field of a database record, the first retrievable grammatical syntax element received via an input tool;
storing a second computer retrievable grammatical syntax element associated with the rhetorical structure in a second field of the database record, the first retrievable grammatical syntax element received via an input tool; and
wherein the rhetorical structure facilitates selective assembly of the first computer retrievable grammatical syntax element and the second computer retrievable grammatical syntax element into at least one sentence or paragraph of a first electronically distributable document and into at least one sentence or paragraph of a second electronically distributable document, wherein the first electronically distributable document has a technical level greater in technical specificity than a technical level of the second electronically distributable document.
11. The method of claim 10, further comprising storing a third computer retrievable grammatical syntax element in a third field of the database record.
12. The method of claim 11, wherein the first computer retrievable grammatical syntax element is a product name, the second computer retrievable grammatical syntax element is a product class, and the third computer retrievable grammatical syntax element is a product differentiator.
13. The method of claim 11, wherein each of the computer retrievable grammatical syntax elements is stored in a database as a separate database entry.
14. The method of claim 10, wherein:
the input tool includes a user interface having at least one entry page associated with the content subject and wherein each entry page includes at least one text entry form element for receiving input text having a length, the input text constrained in accordance with a grammatical format associated with a rhetorical purpose; and
the input tool includes a selection element configured to initiate manipulation of a data record associated with the content subject at the database upon activation of the selection element.
15. The system of claim 14, wherein the data associated with the content subject is subdivided into a plurality of sections, each section associated with an entry page.
16. The system of claim 15, wherein the sections include a product purpose, a product operation, branding information, frequently asked questions, a teaser, a product feature, a product advantage, a product application, a product implementation, a product testimonial, a product component, a product illustration, a product diagram, a product option, a product availability, a legal notice, a white paper, or any combination thereof.
17. The system of claim 15, wherein each entry page is displayed in connection with a graphical tab and wherein each entry page is displayed as a separate web page.
18. The system of claim 14, further comprising a plurality of test entry form elements.
19. The system of claim 14, wherein the data record includes a plurality of fields associated with a plurality of rhetorical sentence structures.
Description
    REFERENCE TO RELATED APPLICATIONS
  • [0001]
    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.
  • FIELD OF THE DISCLOSURE
  • [0002]
    This disclosure relates, in general, to rhetorical content management systems and methods for their use.
  • BACKGROUND
  • [0003]
    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.
  • [0004]
    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.
  • [0005]
    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.
  • [0006]
    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.
  • [0007]
    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.
  • SUMMARY
  • [0008]
    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.
  • [0009]
    In a particular illustrative embodiment, a method of managing content is disclosed. The method includes receiving input from an input tool, wherein the input includes a plurality of grammatically-structured text elements related to a content subject. The method also includes storing the plurality of grammatically-structured text elements as a plurality of fields of a record associated with the content subject. Further, the method includes sending the plurality of fields to a content server in response to a request, wherein the content server converts the grammatically-structured text elements into structured-format rhetorical elements and sends the structured-format rhetorical elements to a first application that integrates the structured-format rhetorical elements into a first electronically distributable document having a first technical level and sends the structured-format rhetorical elements to a second application that integrates the structured-format rhetorical elements into a second electronically distributable document having a second technical level that is greater in technical specificity than the first technical level.
  • [0010]
    In accordance with another particular embodiment, a content management system is disclosed and includes a database configured to communicate with an input tool to receive input, wherein the input includes a plurality of grammatical syntax elements related to a content subject. The database is configured to store a plurality of records, at least one record of the plurality of records including a plurality of fields storing the plurality of grammatical syntax elements associated with the content subject, each of the plurality of grammatical syntax elements having a rhetorical structure to facilitate selective assembly into at least one sentence. In addition, the database is configured to send at least one grammatical syntax element of the plurality of grammatical syntax elements to a content server in response to a request, wherein the content server converts the at least one grammatically-structured text element into at least one structured-format rhetorical element and sends the at least one structured-format rhetorical element to a first application that integrates the at least one structured-format rhetorical element into a first electronically distributable document having a first technical level and sends the at least one structured-format rhetorical element to a second application that integrates the at least one structured-format rhetorical element into a second electronically distributable document having a second technical level that is greater in technical specificity than the first technical level.
  • [0011]
    In accordance with another particular embodiment, a method of managing content is disclosed and includes storing a first computer retrievable grammatical syntax element associated with a rhetorical structure in a first field of a database record, the first retrievable grammatical syntax element received via an input tool. The method also includes storing a second computer retrievable grammatical syntax element associated with the rhetorical structure in a second field of the database record, the first retrievable grammatical syntax element received via an input tool. The rhetorical structure facilitates selective assembly of the first computer retrievable grammatical syntax element and the second computer retrievable grammatical syntax element into at least one sentence or paragraph of a first electronically distributable document and into at least one sentence or paragraph of a second electronically distributable document, wherein the first electronically distributable document has a technical level greater in technical specificity than a technical level of the second electronically distributable document.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • [0012]
    FIG. 1 depicts an exemplary embodiment of a content management system.
  • [0013]
    FIG. 2 depicts an exemplary embodiment of a rhetorical content delivery system.
  • [0014]
    FIG. 3 illustrates an exemplary embodiment of an input tool.
  • [0015]
    FIG. 4 depicts an exemplary method of content management.
  • [0016]
    FIG. 5 illustrates an exemplary distribution/repurposing of rhetorically structured content.
  • [0017]
    FIG. 6 depicts an exemplary rhetorical data structure.
  • DETAILED DESCRIPTION OF THE DRAWINGS
  • [0018]
    FIG. 1 depicts an exemplary embodiment of a content management system. The content management system includes a content database 104 and a content server 106. In addition, the content management system includes an input tool 102 and various applications 108, 110 and 112.
  • [0019]
    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.
  • [0020]
    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.
  • [0021]
    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.
  • [0022]
    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.
  • [0023]
    <<Product name>> is a <<product class>> that <<product description>>.
  • [0024]
    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>>.
  • [0025]
    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.
  • [0026]
    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.
  • [0027]
    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.
  • [0028]
    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.
  • [0029]
    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.
  • [0030]
    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.
  • [0031]
    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.
  • [0032]
    FIG. 2 depicts an exemplary application for creating content. In this exemplary embodiment, a website may be delivered to users. The pages may include content automatically created using the content elements stored in the database. An application server 200 receives requests associated with a content subject from browsers 208, 210 and 212. The application server may have a gateway program 214 that acts to receive the requests and provide the output. In exemplary embodiment, the gateway program 214 receives HTTP requests and provides each HTML web page content.
  • [0033]
    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.
  • [0034]
    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.
  • [0035]
    FIG. 3 depicts an exemplary user interface or input tool for entering data into a rhetorical content management database. In this exemplary embodiment, the content subject is a product. The user interface takes the form of a page 300 that includes a product name 302. The page may, for example, be a web page.
  • [0036]
    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.
  • [0037]
    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.
  • [0038]
    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.
  • [0039]
    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.
  • [0040]
    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.
  • [0041]
    FIG. 4 depicts an exemplary method of content management. The content management system may receive a user input entered in the grammatically structured text entry elements as shown at step 402. The text entered in its grammatically structured format may be stored in the database records as shown at step 404. Some fields may store nouns. Other fields may store phrases starting with a specific verb having a specific tense and number. These fields may be combined according to their associated rhetorical structure to form sentences. Additional fields may store sentences and paragraphs having an associated purpose. The database stores these elements to fulfill rhetorical/communication purposes.
  • [0042]
    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.
  • [0043]
    FIG. 5 depicts the exemplary use of content data associated with a content subject and its selective use in various applications. The data may be organized into a description 516, features and benefits 518, and other categories. Elements may be stored that can be used in a rhetorical structure to produce content. Each of the elements for use in a rhetorical structure may have a syntax that has the appropriate grammatical format for use in the rhetorical structure. In one exemplary embodiment, a classical rhetorical definition 502 may be used. A sentence structure may be provided such as <<Product name>> is a <<product class>> that has <<a key differentiator>>. A data structure may be provided that stores the product name, the product class, and the key differentiator. The product name, product class and key differentiator may each have a specific grammatical syntax that permits their use in this rhetorical structure, while allowing them to be used together or separately by other grammatical structures that serve similar or even widely different rhetorical/communication purposes in other applications.
  • [0044]
    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.
  • [0045]
    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.
  • [0046]
    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.
  • [0047]
    FIG. 6 depicts an exemplary tag-segmented data file 600. The tag-segmented data file may, for example, be an XML file. The XML file may be produced by the content management system from the content stored in the content database. The tag-segmented data file 600 may be used to store a complete data record or partial data associated with a content subject. In the exemplary embodiment of FIG. 6, a product profile is specified. The product profile may have an associated product ID. The data may be further segmented for use in specific markets or regions as indicated by the <Region> tag. <PAC> indicates a specific region and several specific regions may be specified. A tag and tag end are provided for the product name, expanded product name, update date, and update time. These latter two are content management elements. In addition, tags are provided for subdivisions of content elements. For example, a <Description> tag may identify one or more sets of description elements. A description element may for example follow a classical format as indicated by the <Classical_Def> tag. Elements that follow the grammatical format of the classical definition may then be provided as indicated by separate tags. For example, a class description 602, product description 604, and comparison sentence 606 may be provided. The class description and product description may be combined with the product name to form a classical rhetorical sentence. The comparison sentence 606 may be appended to the classical definition to form a paragraph for use in building content.
  • [0048]
    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.
  • [0049]
    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.
Patent Citations
Cited PatentFiling datePublication dateApplicantTitle
US5369573 *Jul 2, 1992Nov 29, 1994Docustructure CorporationStructured document syntax management
US5459827 *Jul 17, 1992Oct 17, 1995Bull S.A.Layout method for structured documents
US5819260 *Jan 22, 1996Oct 6, 1998Lexis-NexisPhrase recognition method and apparatus
US6026388 *Aug 14, 1996Feb 15, 2000Textwise, LlcUser interface and other enhancements for natural language information retrieval system and method
US6041303 *Jun 6, 1997Mar 21, 2000Mathews; Edward HenryMethod of assisting the conducting of a research project
US6112168 *Oct 20, 1997Aug 29, 2000Microsoft CorporationAutomatically recognizing the discourse structure of a body of text
US6185587 *Jun 19, 1998Feb 6, 2001International Business Machines CorporationSystem and method for building a web site with automated help
US6199034 *Apr 14, 1998Mar 6, 2001Oracle CorporationMethods and apparatus for determining theme for discourse
US6263336 *Jan 30, 1998Jul 17, 2001Seiko Epson CorporationText structure analysis method and text structure analysis device
US6349316 *Apr 8, 1999Feb 19, 2002Microsoft CorporationDocument summarizer for word processors
US6353824 *Nov 18, 1997Mar 5, 2002Apple 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, 1997Apr 16, 2002Fuji Xerox Co., Ltd.Hypermedia document authoring using a goals outline and a presentation outline
US6453302 *Nov 25, 1996Sep 17, 2002Clear With Computers, Inc.Computer generated presentation system
US6513063 *Mar 14, 2000Jan 28, 2003Sri InternationalAccessing network-based electronic information through scripted online interfaces using spoken input
US6523061 *Jun 30, 2000Feb 18, 2003Sri International, Inc.System, method, and article of manufacture for agent-based navigation in a speech-based data navigation system
US6549922 *Oct 1, 1999Apr 15, 2003Alok SrivastavaSystem for collecting, transforming and managing media metadata
US6553373 *Nov 29, 2001Apr 22, 2003Apple 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, 1999Jun 3, 2003Intel CorporationIntelligent content delivery system based on user actions with client application data
US6647396 *Dec 28, 2000Nov 11, 2003Trilogy Development Group, Inc.Classification based content management system
US6675159 *Jul 27, 2000Jan 6, 2004Science Applic Int CorpConcept-based search and retrieval system
US6901402 *Jun 18, 1999May 31, 2005Microsoft CorporationSystem for improving the performance of information retrieval-type tasks by identifying the relations of constituents
US6983288 *Aug 8, 2001Jan 3, 2006Cisco Technology, Inc.Multiple layer information object repository
US7013259 *Jun 30, 2000Mar 14, 2006Fuji Xerox Co., Ltd.System and method for teaching writing using microanalysis of text
US7092974 *Mar 12, 2003Aug 15, 2006Right Hemisphere LimitedDigital asset server and asset management system
US20020102524 *Jan 26, 2001Aug 1, 2002Rizzi Steven D.System and method for developing instructional materials using a content database
US20030065533 *Sep 27, 2002Apr 3, 2003Sap AgPortable business information content and management system
US20030126136 *Jun 24, 2002Jul 3, 2003Nosa OmoiguiSystem and method for knowledge retrieval, management, delivery and presentation
US20040015408 *Oct 11, 2002Jan 22, 2004Rauen Philip JosephCorporate content management and delivery system
US20050033750 *Aug 6, 2003Feb 10, 2005Sbc Knowledge Ventures, L.P.Rhetorical content management system and methods
US20070028166 *Apr 10, 2002Feb 1, 2007Allen HundhausenSystem and processes for dynamic document construction
US20070033207 *Aug 2, 2006Feb 8, 2007Sbc Knowledge Ventures, L.P.Rhetorical content management system and methods
US20070067371 *Sep 19, 2005Mar 22, 2007Sbc Knowledge Ventures, L.P.Database structure and method
Referenced by
Citing PatentFiling datePublication dateApplicantTitle
US7296027 *Mar 22, 2004Nov 13, 2007Sbc Knowledge Ventures, L.P.Rhetorical content management with tone and audience profiles
US7313562 *Nov 9, 2006Dec 25, 2007Sbc Knowledge Ventures, L.P.Rhetorical content management system and methods
US7627607Aug 2, 2006Dec 1, 2009At&T Intellectual Property I, L.P.Rhetorical content management system and methods
US7904451Mar 8, 2011At&T Intellectual Property I, L.P.Rhetorical content management with tone and audience profiles
US20050033754 *Mar 22, 2004Feb 10, 2005Sbc Knowledge Ventures, L.P.Rhetorical content management with tone and audience profiles
US20070033207 *Aug 2, 2006Feb 8, 2007Sbc Knowledge Ventures, L.P.Rhetorical content management system and methods
US20070055682 *Nov 9, 2006Mar 8, 2007Sbc Knowledge Ventures, LpRhetorical content management system and methods
US20070067371 *Sep 19, 2005Mar 22, 2007Sbc Knowledge Ventures, L.P.Database structure and method
Classifications
U.S. Classification1/1, 707/999.1
International ClassificationG06F7/00, G06F17/30, G06F17/00
Cooperative ClassificationY10S707/99933, Y10S707/99931, Y10S707/917, Y10S707/99945, Y10S707/99943, Y10S707/99948, G06F17/30607, G06F17/30654
European ClassificationG06F17/30T2F4, G06F17/30S8T
Legal Events
DateCodeEventDescription
Jul 28, 2009ASAssignment
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