Taxonomy Driven Multi-System Networking and Content Delivery

FIELD OF THE INVENTION

The present technology relates generally to web content management, and more specifically, but not by way of limitation, to systems and methods that provide for networking between a plurality of systems using a taxonomy scheme in order to provide a dynamic user experience. In some embodiments these systems and methods leverage artificial intelligence or machine learning to deliver content from the plurality of systems using a taxonomy scheme.

BACKGROUND OF THE INVENTION

Generally speaking, the content of a website may be composed by gathering a mix of content such as textual, image, video, hyperlinks, and applications—just to name a few. These various types of content may be gathered from a variety of sources and from many different third party software tools, such as web design programs. Web content that is created specifically for distribution through web sources, such as a website, may be created in utilizing, for example, a content manager explorer (CME).

Content authors may desire access to information related to the design of web content stored in other systems (e.g., the third party software) that they desire to make use of in the CME. Such an integration of third party software would require specific integrations of the third party software into the main CME and in some cases the core software used by end users to create, manage and publish web content to websites, also known as “CM.” Unfortunately, these types of integrations may restrict the number and level of integrations possible.

Moreover, most websites are comprised of a patchwork of functionalities created directly for the website. These functionalities may be included in a web application that is utilized to operate the website. Additionally, the functionalities may be derived from third party sources (internal and external). These third party sources may provide their own code (e.g., tag libraries or application programming interfaces) that must be run in the same environment in which they were created in order for the functionality to be completely rendered by the web application. If the third party sources are not run in the same environment in which they were created, the functionalities may not operate correctly within the web page. One alternative to this requirement is for the CME to allow the use of client side rendering through at least one of hypertext markup language HTML iframe elements and web services through AJAX or JavaScript integrations that may render portions of the web page once the web service data is returned by the web application. Unfortunately, these integration methods may make it difficult to clearly separate web services code from the actual web content. Moreover, web services that utilize, for example, .NET functionalities, may not be able to effectively render third party functionalities from other sources.

SUMMARY

According to some embodiments, the present invention is directed to a system comprising: a website authoring platform generating a taxonomy structure for a webpage, the taxonomy structure indicating assets to be included in the webpage a layout for the assets; a technical documentation authoring system for creating technical documents related to the assets; and a metadata binder providing the technical documentation authoring system with access to the taxonomy structure of the website authoring platform so that technical document authors are provided with the taxonomy structure to guide creation and structuring of the technical documents so that the technical documents comprise data that corresponds to the assets.

According to some embodiments, the present invention is directed to a system comprising: a website authoring platform generating a taxonomy structure for a webpage, the taxonomy structure indicating assets to be included in the webpage a layout for the assets; a technical documentation authoring system for creating technical documents related to the assets, wherein a technical document includes data that is structured and labeled according to the taxonomy structure, the taxonomy structure being received through a metadata binder; and a unified delivery platform system that creates a webpage comprising a content mashup having both the assets and the data from the technical document relating to the asset, the content mashup being created according to the taxonomy structure.

According to some embodiments, the present invention is directed to a method comprising: receiving a taxonomy structure for a webpage, the taxonomy structure defining a layout of content for the webpage, receiving one or more technical documents generated by a technical documentation authoring system related to assets of the webpage, combining, into the webpage, the assets selected by a website authoring platform and data of the one or more technical documents generated by the technical documentation authoring system, according to the layout of the taxonomy structure; and publishing the webpage.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A is a schematic diagram of an exemplary architecture of a system for managing web content that may be utilized to practice aspects of the present technology.

FIG. 1B is a partial schematic diagram of the exemplary architecture of FIG. 1A.

FIG. 2 is a flow diagram of an exemplary method for managing web content.

FIG. 3 is an exemplary user interface in the form of a web page for interacting with a web content management application.

FIG. 4 is a block diagram of an exemplary computing system that may be utilized to practice aspects of the present disclosure.

FIG. 5 is a diagrammatic view of an example system for managing and delivering web content that may be utilized to practice aspects of the present technology.

FIG. 6 is a schematic diagram of an example system of the present disclosure as well as an example taxonomic integration between a web experience management system and a structure content management system through use of a metadata binder.

FIG. 7 is a flowchart of an example method of the present disclosure.

FIGS. 8A-8C collectively illustrate an example embodiment of a system that is configured to provide content mashups of the present disclosure in response to real-time navigation data.

DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS

While this invention is susceptible of embodiment in many different forms, there is shown in the drawings and will herein be described in detail several specific embodiments with the understanding that the present disclosure is to be considered as an exemplification of the principles of the invention and is not intended to limit the invention to the embodiments illustrated.

Generally speaking, the systems and methods provided herein may be utilized to generate, manage, and selectively modify web content for global marketing campaigns. The systems and method maintain a global marketing framework that may be utilized to create individual web marketing campaigns across a wide variety of communications mediums. Content authors may utilize the global marketing framework in a collaborative manner and seamlessly incorporate content data created thorough third party applications.

The systems and methods provided herein utilize application data created in a web content management application that provides extra data storage on an item level allowing a content author to store additional web content and external other data (e.g., third party application data) directly into the web content management application. The systems and methods provide mapping between web content associated with a marketing campaign and corresponding data in third party systems, such as product information management systems.

The systems and methods may utilize simple object access protocol web services that are adapted to expose web application data and in some embodiments, affect application data associated with web content as an item transaction. The CME also includes an extensible framework that allows implementers to add extra data obtained through third parties sources/software, as well as associated third party workflow into the web content management application. It will be understood that the term “implementer” may include individuals producing computer readable instructions that may be utilized to modify the appearance or functionalities of the web content management application. These functionalities provide the content authors with one location (the web content management application) at which are able to perform actions with scope over many systems. The combination of these functionalities provides third parties, such as partners, the ability to create portable solutions to integrate third party data from third party data sources. These portable solutions may allow for customization of the web content management application across many installations of the web content management application.

The systems and methods may include a dynamic rendering engine and dynamic rendering engine data format that allows implementers to abstract dynamic functionalities to a predetermined format that is intercepted and rendered by the dynamic rendering engine. Data abstracted to the predetermined format may be utilized as a portion of a core development implementation before being passed back to the requester. According to some embodiments, the core development may include functionalities adapted to render dynamic links that ensure that a website never has broken links to internal pages associated therewith.

It will be understood that the data included in the web content generated by the web content management application is provided according to the predetermined format of the rendering engine, rather than from data format utilized by standard web applications such as JavaScripts or .NET. In some embodiments, tag libraries available to the rendering engine data format may be added in Java making it possible to render the functionalities of the web application without actually requiring the deployment of the web application.

Referring now to FIG. 1A, illustrating an exemplary system 100 for managing web content. The system 100 may include a web content management application, hereinafter referred to as the “application 105,” adapted to communicate with a plurality of client devices 110. Each of the client devices 110 may be associated with a user (e.g., a content author) who provides content data that may be utilized by the application 105 to generate a global marketing framework. It will be understood that a global marketing framework may include detailed information indicative of a marketing campaign. Portions of the global marketing framework may be utilized to generate customized marketing campaigns that may be deployed across a wide range of communication channels (e.g., web, radio, television, print, and so forth). In some instances, the marketing campaign may include information, such as text, audio, video, forms, templates, user interfaces, and any additional information that may be utilized in the creation of marketing campaigns. Non-limiting examples of marketing campaigns include, banners, links, web pages, and so forth, both interactive and non-interactive.

It is noteworthy that the application 105 may be adapted to generate web marketing campaigns utilizing these customizable and multi-channel functionalities. This may be accomplished, for example, by converting data received by the content authors into widely implemented content structural formats. Such formats may include, for example, an extensible markup language format (XML) that is utilized by the application 105.

The application 105 may be implemented in the context of a web site 300 (FIG. 3) that is hosted on a web server 115. It will be understood that the web server 115 may include a single web server or a plurality of web servers networked or associated together in a cloud configuration (not shown). As will be discussed in greater detail below, the system 100 may include a presentation server 155 adapted to display the web marketing campaign generated by the application 105. A more detailed description of the basic functionalities of client devices 110, web server 115, and presentation server 155 are provided with reference to computing system 400 illustrated in FIG. 4.

In some embodiments, the web server 115 may be operatively associated with one or more databases 120. The one or more databases 120 may be configured as Object Linking and Embedding, Database (OLEDB) or Open Database Connectivity (ODBC) databases. In some embodiments, the content (e.g., global marketing framework, web marketing campaign, etc.) generated by the application 105 may be stored in the one or more databases 120. It will be understood that the client devices 110 may be operatively coupled to the application 105 via a network 125, which in some embodiments includes the Internet.

The content authors may interact with the application 105 via graphical user interfaces (GUIs) 130 generated by the application 105. According to some embodiments, the content authors may interact with the GUIs 130 via a web browser resident on the client device 110. The graphical user interfaces 130 may provide visual representations of the web marketing campaigns generated from the global marketing framework. An exemplary graphical user interface 300 is shown with reference to FIG. 3.

In additional embodiments, content authors may interact with the application 105 via a word processor connector 135 that provides a simplified mechanism for content authors to upload textual information that may be included in the global marketing framework or a web marketing campaign. For example, the word connector 135 may be utilized by content authors who need to create simple text for use in a web marketing campaign via any commonly utilized word processing tool. Content authors may open, edit, and create structured (XML) content by uploading a word processing document that is converted by the word processor connector 135 to structured XML content that may be utilized by the application 105. The XML content may then be saved directly to the content manager module 150, which is described in greater detail below.

Content authors may generate web marketing campaigns from the global marketing framework by inheriting portions (or potentially all) of the data of the global marketing framework. The content authors may customize the data for a web marketing campaign based upon a targeted channel of communication. For example, a content author may modify a web marketing campaign targeted to a social networking web site differently from the way the content author modifies the web marketing campaign for use with an e-commerce web site. It will be understood that inheriting may include selecting, extracting, gathering, referencing, and the like.

According to other embodiments, rather than requiring the content authors to create a plurality of individual web marketing campaigns from the global marketing framework, the application 105 may be adapted to automatically and intelligently generate individual marketing campaigns from the global marketing framework. For example, once the global marketing framework has been established, the application 105 may automatically generate web marketing campaigns in a plurality of different languages. Because the plurality of web marketing campaigns inherit their data from the global marketing framework, consistency may be maintained with regard to branding and message content.

Additionally, the application 105 may tailor the content of individual marketing campaigns based upon the desired audience. For example, the application 105 may not only generate an individual marketing campaign for a particular country based upon language utilized in the country, but may also selectively modify the appearance of the individual marketing campaign based upon marketing data gathered for the particular country. For example, if marketing data suggests that different color schemes produce more efficient results for different countries, the various web marketing campaigns may be created with varying color schemes to maximize the efficiency of a web marketing campaign.

While it has been contemplated that the application 105 may tailor individual marketing campaigns for countries, one of ordinary skill in the art will appreciate that individual marketing campaigns may likewise tailored to other targets such as specific consumers, business entities, and states—just to name a few.

In some embodiments, content authors may create folder structures for storing marketing campaign data that may be utilized by the application 105 via a webDAV connector 140. Content authors may add, edit, delete, and use content that is utilized in the generation of web marketing campaigns in the same way that they would use the Windows file system. For example, content authors may access folder structures using a web browser application or any other suitable desktop application resident on the client device 110.

According to some embodiments, the application 105 may include a content porter module 145 adapted to facilitate the exchange of data between the database 120 associated with the web server 115 and at least one of the application 105 and the client devices 110. In other embodiments, the content porter module 145 provides content authors the ability to develop marketing content and/or web site functionalities apart from the live version (e.g., the version currently published on the presentation server 155) of the web site 300. As stated above, an exemplary visual representation of web site 300 is provided in FIG. 3, and will be described in greater detail below. The application 105 may then transfer the developed marketing content to the application 105, which facilitates the inclusion of the developed content to the live version of the web site 300.

The content porter module 145 may be adapted to transfer data between different versions or instances of the application 105 running on multiple client devices 110 (e.g., collaborative web marketing campaign creation). The application 105 may be adapted to assemble the portions of the web marketing campaign created by the various content authors into one or more cohesive web marketing campaigns.

Regardless of how the application 105 generates the web marketing campaign(s) (e.g., automatically, via collaborative effort, etc.), the web marketing campaigns may be published to a web site associated with the presentation server 155 via the content distributor module 160. As the web marketing campaigns are published on a presentation server 155, the web marketing campaigns may be accessed via consumer devices 165A or customer portals 165B via a consumer device 165A. It will be understood that the consumer portal 165B may include a web site operated by a marketer or utilized by a marketer to deliver web marketing campaign (e.g., banner advertisement).

It will be understood that consumer devices 165A may include computing systems of any kind, and may generally be described with reference to computing system 400 (FIG. 4). It is noteworthy that the presentation server 155 and the web server 115 hosting the application 105 may be combined together.

The system 100 may include a visitor intelligence module 170 adapted to gather, via the presentation server 155, marketing data from the plurality of consumer devices 165A accessing the web marketing campaign. It will be understood that each of the consumer devices 165A may be associated with an individual consumer (i.e., end user) such that an analysis data provided by the consumer devices 165A may yield information indicative of the end user (i.e., consumer) associated therewith. According to some embodiments, the marketing data may include information indicative of the interests of the consumer.

Additionally, the visitor intelligence module 170 may be adapted to analyze information received from the consumers accessing a web marketing campaign via consumer portal 165B.

Generally speaking, the marketing data may include any of a consumer name, a consumer identification, an address, a postal code, a telephone number, a credit card number, a social networking profile, a Internet protocol address, a media access control (MAC) address, visitation duration, visitation frequency, and combinations thereof. One of ordinary skill in the art will appreciate that many other types of information indicative of a consumer may likewise be utilized in accordance with the present invention.

To be sure, any aspects of the present disclosure related to the use of customer or consumer information will be conducted in accordance with relevant and specific data privacy rules and regulations such as GDPR (General Data Protection Regulation) or other similar data privacy regulations that would be known to one of ordinary skill in the art.

In some embodiments, the visitor intelligence module 170 may be adapted to gather marketing data by examining at least one of a cookie, a web form associated with the presentation server hosting the web marketing campaign, a query string embedded in a uniform resource locator (URL) associated with the presentation server hosting the web marketing campaign, window.name information associated with a web browser session, hyper text transfer protocol authentication information, and combinations thereof.

The marketing data gathered by the visitor intelligence module 170 may be stored in a raw format on the database 120 via the content porter module 145. In addition to creating lists of consumers to which marketing campaigns may be directed by utilizing basic raw data such as names, or addresses, the visitor intelligence module 170 may be adapted to create lists based up the one or more consumer groups. For example, a marketing content author, such as an individual creating electronic mail marketing campaigns, may author content that is directed to all consumers that belong to the consumer group of “baseball.” Therefore, rather than sending electronic mail marketing campaigns to all consumers indentified by the visitor intelligence module 170, directed electronic mail marketing campaigns may be directed to consumers that are known to have an interest in the content of the electronic mail marketing campaign, which in this instance may include a sale on baseball related sports memorabilia.

The content author creates the electronic mail marketing campaign via the application 105 and retrieves the particular consumer groups to which the electronic mail marketing campaign should be directed from the application 105. The application 105 then provides the selected consumer groups to the content author via a business connector module 175.

Referring now to FIGS. 1A and 1B collectively, the application 105 may include the business connector module 175 adapted to interface the application 105 with one or more third party application(s) 180A by way of one or more data exchange adapters 185. In addition to data exchange adapters 185, the business connector module 175 may be adapted to communicate directly with third party applications 180A such as Java-based applications.

As stated above, the application 105 may be adapted to utilize a dynamic rendering engine (not shown) and dynamic rendering engine data format that allows implementers to abstract dynamic functionalities (from a third party application 180A) to a predetermined format (that is intercepted and rendered by the dynamic rendering engine). Data abstracted to the predetermined format may be utilized as a portion of a core development implementation before being passed back to the requester.

In some embodiments, the data exchange adapter 185 may be adapted to convert at least one of the marketing data gathered by the visitor intelligence module 170 and the one or more consumer groups created by the visitor intelligence module 170, to the data format utilized by the third party application 180A. For example, the third party application 180A may include applications such as a web page design application, a graphics editing program, and the like that may be utilized to create marketing content that may be incorporated into the web marketing campaign.

The data exchange adapter 185 may interface with web-service enabled third party applications 180A utilizing a simple object access protocol (SOAP) interface 190A, an extensible stylesheet language transformations (XSLT) transformer 190B, and mapping logic module 190C.

In other embodiments, the business connector module 175 may utilize an enterprise application integration broker 195 to exchange data with one or more enterprise third party programs 180B. For example, the broker 195 may be adapted to facilitate the exchange of data between an enterprise third party application 180B such as an email server application, and the business connector module 175 by determining a data format utilized by the enterprise third party application 180B, which in this case includes simple mail transfer protocol (SMTP) format. In practice, a content author may provide content via an electronic mail message. The data exchange adapter 185 receives the message that is converted by the XSLT transformer 190B to a data format utilized by the application 105, i.e., XML format. The mapping logic module 190C may be adapted to index the data format exchange information established between the SOAP interface 190A and the enterprise third party application 180B. Again, other document formats and service protocols can be used other than XML/SOAP as would be appreciated by one of ordinary skill in the art.

It will be understood that the business connector module 175 may be adapted to provide at least one of the raw marketing data and the one or more consumer groups gathered by the visitor intelligence module 170 to one or more of the third party applications 180A or enterprise third party applications 180B. For example, the data exchange adapter 185 may convert the marketing data gathered by the visitor intelligence module 170 in XML format to a data format that is utilized by a web page design application.

With regard to modifying the content of a web marketing campaign based upon marketing data, the system 100 may include a dynamic broker module 155A associated with the presentation server 155. The dynamic broker module 155A may be adapted to selectively modify a web marketing campaign based upon the marketing data received by the visitor intelligence module 170. For example, the dynamic broker module 155A may modify the web marketing campaign to include different advertisements directed to products from a product catalogue of a marketer based upon the interests of the consumers viewing the web marketing campaign, as determined by the visitor intelligence module 170.

In other embodiments directed to consumers who utilize mobile devices, the dynamic broker module 155A may be adapted to determine a configuration of each mobile consumer device requesting the web marketing campaign. The dynamic broker module 155A may determine the configuration of a mobile consumer device by evaluating the international mobile equipment identifier (IMEI) of the mobile consumer device. By analyzing the IMEI, a mobile device operating system version may be determined, along with other pertinent information. Utilizing the gathered information, the dynamic broker module 155A may cause the provision of a version of the web marking campaign (via the presentation server 155) to the mobile consumer device that may be substantially compatible with the mobile device operating system version of the device.

In other embodiments, the dynamic broker module 155A may be utilized to periodically or continually modify the content of a web marketing campaign based upon an analysis of marketing data. For example, marketing data received from the consumer devices 165A may indicate that a particular web marketing campaign is underperforming (i.e., not generating the proper number of click through instances or generating enough sales). As such, the interests of the consumers accessing the web marketing content may indicate that a change in the products included in the web marketing campaign may more closely coincide with the interests of the consumer groups. Therefore, the application 105 may modify the content of the web marketing campaign to substantially correspond to the interests of the consumers. Moreover, this type of dynamic modification may take place on a granular level (i.e., at the individual consumer level).

FIG. 2 illustrates an exemplary flow chart of a method 200 for managing web content. The method 200 may include the step 205 of providing a web content management application via a web site. The web content management application may be coupled to a web server associated with the web site. Moreover, the web content management application may be adapted to maintain a global marketing framework indicative of a marketing campaign.

Next, the method 200 may include the step 210 of generating a web marketing campaign from at least a portion of the global marketing framework, via the web server, which in some embodiments includes a presentation server. In an additional embodiment, the method 200 may include the step 215 of gathering, via the web server (or the presentation server), marketing data from a plurality of consumer devices accessing the web marketing campaign. It will be understood that each of the consumer devices may be associated with a consumer and that the marketing data may include information indicative of interests of the consumer associated with the consumer device.

Additionally, the method 200 includes the step 220 of storing the marketing data in a database and a step 225 of associating consumers together according to at least one common interest to create one or more consumer groups. The method 200 may also include the step 230 of providing the one or more consumer groups to at least one marketing content author such that the web marketing campaign delivered to the consumer groups may be tailored to the interests of the consumer.

The method 200 may include an additional step 235 of interfacing the application with one or more third party applications via the use of a data exchange adapter or an EAI broker. The method 200 may also include a step 240 of selecting an appropriate version of the web marketing campaign to deliver to a mobile consumer device by evaluating the mobile device information indicative of the mobile consumer device and selecting a version of the web marketing campaign that corresponds to the mobile consumer device. Additionally, the method 200 may include the step 245 of selectively modifying the web marketing campaign based upon the marketing data to increase the efficiency of the marketing campaign.

FIG. 3 illustrates an exemplary user interface 300 that allows content authors to interact with the application 105. Generally speaking, the user interface 300 generated by the application 105 may provide content authors with a What You See Is What You Get (WYSIWYG) representation of the web marketing campaign. That is, the user interface 300 generated by the application 105 may include a representation of the web marketing campaign that is identical, nearly identical, or to the actual visual appearance of the web marketing campaign that is published by on the presentation server 155. As additional content is added to the web marketing campaign, the user interface is updated to include the new content.

The user interface 300 may include a plurality of block icons 305A-D indicative of individual web marketing campaigns. More particularly, each of the block icons 305A-D may be indicative of a web marketing campaign for a particular communication channel. Block icon 305A includes a web marketing campaign that may be directed to a search engine. Block icon 305B includes a web marketing campaign that may be directed to a first social networking application and block icon 305C to a second social networking application. Additionally, block icon 305D may be directed to a banner advertisement that may be directed to any suitable web site.

The user interface 300 includes visual representations of the relationships of the individual web marketing campaigns relative to one another via directional arrows 310. For example, the directional arrows 310 linking each of the block icons 305A-D may indicate that each of the web marketing campaigns associated with the block icons 305A-D direct consumers to the landing page (represented visually by block icon 305E) of a marketer's website.

As stated previously, the web content management system described above also includes an extensible framework that allows implementers to add extra data obtained through third parties sources/software, as well as associated third party workflow into the web content management application. It will be understood that the term “implementer” may include individuals producing computer readable instructions that may be utilized to modify the appearance or functionalities of the web content management application.

It is noteworthy that some embodiments according to the present technology support a variety of web browsers. Examples include but are not limited to Internet Explorer, Firefox, Chrome, Safari, Opera, various mobile browsers, and so forth. It may be desirable, in certain instances, for a user to be able to extend the graphical user interface (GUI). Advantageously, the system is adapted to allow users (or content authors) to customize the GUI to include features that they commonly use, rather than loading a plurality of features that the user may not need.

It various embodiments, the user possesses the ability specify how the desired add-in features are included in the GUI. For example, a feature such as “rename” may be included in a right-click mouse menu (for example), in an icon included in a toolbar, and so forth. The system may also allow users to change the visual appearance of their GUI, for example, by adding or subtracting columns that provide various types of information. The flexible architecture used for the GUI allows for enhanced extensibility so that users may extend functionality and customizations.

In some embodiments, a centralized model repository is implemented. The inclusion of this centralized model repository may allow for the editors, and the different screens of the editors, to communicate with main model items hosted in a single place. In other words, it is envisioned that when there is a change in a single location in the model repository, the various editors and views may be notified about the change. In exemplary embodiments, when an editor makes a change, the editor makes the change in the centralized model repository. Further, the system may support object models with inheritance of the extended Java script language, thus allowing for the building of object models with inheritance. The inclusion of a configuration framework allows the plug in of new models, editors, and so forth.

FIG. 4 illustrates an exemplary computing system 400 that may be used to implement an embodiment of the present invention. The computing system 400 of FIG. 4 includes one or more processors 410 and main memory 420. Main memory 420 stores, in part, instructions and data for execution by processor 410. Main memory 420 can store the executable code when the system 400 is in operation. The system 400 of FIG. 4 may further include a mass storage device 430, portable storage medium drive(s) 440, output devices 450, user input devices 460, a graphics display 440, and other peripheral devices 480.

The components shown in FIG. 4 are depicted as being connected via a single bus 490. The components may be connected through one or more data transport means. Processor unit 410 and main memory 420 may be connected via a local microprocessor bus, and the mass storage device 430, peripheral device(s) 480, portable storage device 440, and display system 470 may be connected via one or more input/output (I/O) buses.

Mass storage device 430, which may be implemented with a magnetic disk drive or an optical disk drive, is a non-volatile storage device for storing data and instructions for use by processor unit 410. Mass storage device 430 can store the system software for implementing embodiments of the present invention for purposes of loading that software into main memory 410.

Portable storage device 440 operates in conjunction with a portable non-volatile storage medium, such as a floppy disk, compact disk or digital video disc, to input and output data and code to and from the computer system 400 of FIG. 4. The system software for implementing embodiments of the present invention may be stored on such a portable medium and input to the computer system 400 via the portable storage device 440.

Input devices 460 provide a portion of a user interface. Input devices 460 may include an alphanumeric keypad, such as a keyboard, for inputting alphanumeric and other information, or a pointing device, such as a mouse, a trackball, stylus, or cursor direction keys. Additionally, the system 400 as shown in FIG. 4 includes output devices 450. Suitable output devices include speakers, printers, network interfaces, and monitors.

Display system 470 may include a liquid crystal display (LCD) or other suitable display device. Display system 470 receives textual and graphical information, and processes the information for output to the display device.

Peripherals 480 may include any type of computer support device to add additional functionality to the computer system. Peripheral device(s) 480 may include a modem or a router.

The components contained in the computer system 400 of FIG. 4 are those typically found in computer systems that may be suitable for use with embodiments of the present invention and are intended to represent a broad category of such computer components that are well known in the art. Thus, the computer system 400 of FIG. 4 can be a personal computer, hand held computing system, telephone, mobile computing system, workstation, server, minicomputer, mainframe computer, or any other computing system. The computer can also include different bus configurations, networked platforms, multi-processor platforms, etc. Various operating systems can be used including UNIX, Linux, Windows, Mac OS, Palm OS, and other suitable operating systems.

The computer system 400 may also include a mobile computing device that may have a configuration that includes at least one of a mobile operating system having an operating system version number. Additionally, mobile device may be identified by way of an international mobile equipment identifier (IMEI).

According to some embodiments, the systems and methods of the present disclosure can provide functional access to content through querying and/or access of a plurality of systems. For example, an object such as a product for sale is described by more than one digital document such as a marketing brochure and a technical whitepaper. These documents can often be stored in different repositories or data stores. For example, a network can include a data repository that stores only marketing materials. The network can also include a data repository that stores only technical documents. More often than not, these systems are independent and the authors of these different document types do not communicate or work with one another to generate content. Thus, when the products are advertised, for example, on a webpage, the advertising content may be linked to the webpage or replicated as content on the webpage, but the technical document(s) relating to the products may not be linked to the webpage or readily accessible. To be sure, many customers, and as many as 70% or more, will consider the technical document(s) of a product before consummating a purchase of the product. Thus, webpages that lack multiple content types for a product for sale may lack all the necessary information needed to convert a sale.

A significant technical problem that causes these issues is a lack of cross-referencing between these different document types. For example, authors who create marketing material may be unaware that technical documents for a product exist. Moreover, these individuals lack the means to integrate the technical materials even if they are known. Again, this is often due to the fact that different document types are created and stored in systems that exist and operate orthogonally and/or in a mutually exclusive manner.

The present disclosure provides a technical solution to this type of system and content incompatibility through the creation of a taxonomic-based network structure that allows for combined use of two or more data repositories. This allows content authors to create digital assets such as webpages that are automatically populated with content from many sources by specifying content they desire to incorporate into a webpage. For example, the content authors create a webpage to advertise a service or good. The systems and methods can evaluate the content (attributes of the service or good) included in the webpage and automatically gather links to digital documents that relate to the service or good from many repositories. This automatic content identification and linkage is made possible through the creation and use of a taxonomy structure for each of the data repositories.

In one general example, two systems can be functionally integrated. These example systems include a web content management (WCM) and structured content management (CCMS) with translation technology. The systems of the present disclosure uniquely integrate a webpage authoring system and a product technical document repository. This integration enables the defining of digital experiences on a global scale.

Moreover, these systems and methods enable content publishing for all audiences no matter what location, language or touchpoint, supported by artificial intelligence and machine learning. Both marketing and in-depth product content (e.g., technical content) can be created, managed and delivered cohesively to eliminate the disconnects that characterize digital experiences today and to build brand equity across an entire customer journey.

In some embodiments, the systems and methods herein leverage machine assisted authoring to improve the quality of content by providing guidance, suggesting improvements on style, tone of voice, clarity, grammar, spelling and preferred terminology, while dashboards enable monitoring of overall content quality. This helps keep large, globally dispersed teams of authors, on brand when writing and translating content.

Thus, the systems and methods herein have been developed with both marketing and product development teams in mind. Product developers can benefit from superb content reuse as the CCMS implements a Darwin information typing architecture (DITA) standard and its dynamic publishing features to deliver tailored documentation. This means faster time to ship with better build-integrated documentation, easier content review processes, lower development costs (through automated publishing across multiple platforms and channels), and integrated documentation translation.

In an example use case, if a product and its descriptive content exists the systems and methods herein can dynamically find associated support documents and marketing document, whether co-located or not, using the taxonomy structures disclosed herein. These taxonomy structures are created for each repository and use a standardized format for labeling and categorizing digital document content so that matching content can be linked between repositories. In a basic example, a product name can be standardized and that name can be identified as belonging to documents in multiple data repositories. In some embodiments, this can be accomplished through a taxonomic widget that can be activated during webpage authoring.

Correspondingly, marketers, facing tight deadlines and shorter product release cycles can consistently manage multiple online brands, digital assets and marketing messages with using the WCM system. It gives teams the ability to quickly build and evolve multi-lingual, multi-cultural and multi-brand websites to deliver locally relevant, personal experiences on a global scale to customers' preferred channel and device—all while dramatically shrinking time to market.

Constantly reconfirmed by analysts' market assessments is the ability to handle extreme content volumes and complexity associated with multi-brand, multi-product, multi-site, multi-publication, multilingual environments. The approaches disclosed herein not only create an experience that blends pre-sale, sale and post-sale content into a single customer journey, but also maintains the critical feature richness needed at the authoring level for the various types of content and makes the required sophistication easy to work with.

To keep up with customer demand, companies need to rethink the way they approach the customer journey. Only by unifying experience delivery mechanisms for both marketing content, commerce elements and in-depth product content, can companies truly ensure a joined up digital experience during the entire online customer journey.

Also, in some embodiments, the systems and methods can control webpage or other content authoring using constraining templates or trees. These constraining trees define the types and structure of content that can be placed into a webpage. This guides web content authors by providing them the ability to visualize rules when creating web content. These and other objects of the present disclosure are provided herein with reference to the collective drawings.

FIG. 5 illustrates an example conceptual diagram of a system of the present disclosure. The system 500 comprises a web content management or web experience management system 502, a structure content management system 504, a contextual relevance process 506, a dynamic experience delivery service 508, and a global distribution management system 110. In general, the web experience management system 502 can correspond to the system 100 for managing web content disclosed and illustrated above.

Web content generated using the web experience management system 502 and digital documentation (e.g., technical documents) are assembled in the structure content management system 504 before transmission to the contextual relevance process 506. As noted above, the web experience management system 502 is utilized to create multi-site (e.g., end point), multi-brand, and/or multilingual online experiences. The structure content management system 504 is used to generate product and technical documentation various file formats and versions for delivery to different end points.

In the contextual relevance process 506, the content created in both the web experience management system 502 and the structure content management system 504 are tailored using personal, cultural, and/or geographical information. Examples of content tailoring for these parameters are described in greater detail supra, but generally, the authored content from the web experience management system 502 and the structure content management system 504 can be translated from a source language to a target language in the contextual relevance process 506, as well as tailoring for cultural and/or geographic relevance. This tailoring is performed when it is known where the web content and related documentation will be published. For example, web content and/or documentation can be tailored to general or specific preferences of individuals in a country. In some embodiments, the content can be further or additionally tailored for specific individual preferences. In general, tailoring can include any combination of translation, localization, and transcreation of content for the purpose of making web and technical content relevant from a cross-cultural perspective.

In various embodiments, the dynamic experience delivery service 508 creates and leverages the taxonomies of the present disclosure for improving web and technical content. For example, the dynamic experience delivery service 508 can create a taxonomy for content generated by the web experience management system 502 and the structure content management system 504. In one example embodiment, the taxonomy is created using a textual analysis of the web content and the technical documentation. The dynamic experience delivery service 508 can compare the taxonomies created for the respective content of the web experience management system 502 and the structure content management system 504 and link the documents in each of these systems together such that when the web content is delivered the technical documentation is delivered necessarily due to the linking therebetween.

The global distribution management system 510 is used to publish the web content and linked technical documentation to a plurality of end points 512 that can include social networks, computing systems, email mobile devices, and so forth. It will be understood that the global distribution management system 510 can be used to manage and publish content to hundreds, and sometimes thousands of end points.

As noted above, the web experience management system 502 is a distinct system that allows web content creators to author webpages and other similar content. The structure content management system 504 is a system that allows technical document creators to author technical materials such as technical specifications, user manuals, whitepapers, and so forth.

In sum, the system 500 provides a single online dynamic content delivery environment for both web experiences and product led structured content. The system 500 scales to optimize and streamline an entire global content creation and delivery process. The system 500 enables users to create a continuous, consistent brand and content experience across every digital touchpoint in any language. The system 500 is enhanced with artificial intelligence and machine learning to assist authors as they create quality, consistent content more efficiently. The system 500, and specifically the dynamic experience delivery service 508 implements an API-first approach, enabling users to expose content to any site, application or touchpoint, while also providing content authors the benefits of integrated in-context content creation. The system 500 allows authors to extend content delivery options using a RESTful API, providing the option of using dynamic API-based delivery to an ecosystem of mobile applications and websites for full cross-platform publishing and custom user experiences.

Referring briefly to FIGS. 1A-1B and 5 collectively, the business connector module 175 in some embodiments comprises a SOAP based web-service(s). In other embodiments the business connector module 175 comprises an HTTP REST based web-service deployed with respect to the content manager side of the system 100. This service is used for integration during content creation, management, translation, and so forth. Once complete, the content is published the distributor module 160 (corresponding to the dynamic experience delivery service 508). Embodiments utilizing the dynamic experience delivery service 508 expose the published content using a separate service running in the dynamic experience delivery service 508 (see the unified delivery platform 612 of FIG. 6 as an example).

As alluded to above, the features and functions of the content distributor module 160 can be considered in view of the descriptions of the dynamic experience delivery service 508 disclosed herein. That is, in some embodiments, the content distributor module 160 is replaced with the dynamic experience delivery service 508. In some embodiments, such as in the embodiment of FIGS. 8A-8C, content distribution and presentation service are implemented as a web application.FIG. 6 illustrates an example taxonomic integration between a web experience management system 602 and a structure content management system 604 through use of a metadata binder 606. As with the examples disclosed above, the web experience management system comprises a core service 608 that allows for creation of webpages and a taxonomy generator 610 that creates or allows for creation of a taxonomy structure for webpages generated in the web experience management system 602. The taxonomy that is generated is exposed to the structure content management system 604 by the metadata binder 606. That is, the taxonomy created for a webpage by a webpage author is exposed to authors of technical documentation.

In some embodiments, a unified delivery platform (UDP) 612 is utilized to receive independent content published by both the web experience management system 602 and structure content management system 604 and integrate the independently published content using the taxonomy structure generated by the taxonomy generator 610 of the web experience management system 602. In some embodiments, the unified delivery platform 612 can align content from both systems 602 and 604 and using the taxonomy structure. This ensures that content included on a webpage and technical content are properly aligned and integrated into a webpage. In an example webpage 614 being created, content such as an image 616 of a car for sale is placed into a webpage by a webpage author. When the image 616 is placed, the author is provided with an interface that allows the author to fill out taxonomic data about the object in the image. In some instances, the interface is referred to as a taxonomic widget that is activate during webpage authoring.

In some embodiments, the unified delivery platform 612 receives an extensible markup language (XML) document from the web experience management system 602. This can occur during webpage authoring or at runtime when access to a webpage is requested by an end user. The technical documentation is received by the unified delivery platform 612 in a document format that has been structured (or can be read and evaluated) based on the taxonomy structure. The unified delivery platform 612 can create the content mashup between the webpage and the technical documentation using the taxonomy structure.

In some instances, some of the taxonomic data is discovered as metadata that is found in the image 616. If not found, the taxonomic data is provided by the author. The taxonomic data is based on a taxonomy structure. Thus, a taxonomy structure in this example could include category descriptions such as “transportation” and “cars”. The taxonomy structure includes keywords such as a model number, maker, and so forth. In sum, the taxonomy structure and its corresponding taxonomic data include both categories and keywords that descriptively define the object, which in this case is a vehicle.

Correspondingly, technical document creators can utilize the taxonomy structure generated by the web experience management system 602 to create and structure technical content so that it corresponds to the taxonomy structure as exposed by the metadata binder 606.

In general, the metadata binder 606 provides the technical documentation authoring system with access to the taxonomy structure of the website authoring platform so that technical document authors are provided with the taxonomy structure to guide creation and structuring of the assets so that the technical documents comprise data that corresponds to the assets. Thus, these authors and systems are now no longer disconnected and creating content that is independent and/or potentially mutually exclusive.

In more detail regarding the creation and use of taxonomies, metadata is stored as part of the content XML of a webpage and can be used to enhance published sites, and drive automation, scheduled publishing and management to the data store. Metadata can be assigned to any object (content, pages, folders, templates, publications etc.) and can be configured directly in a webpage creation interface 622. Using categories and keywords, authors of the webpage can create taxonomies that can be used to by non-technical users to populate metadata fields by selecting pre-configured keywords. Thus, these categories and keywords for classification or metadata become a taxonomy.

Due to the connection between the system 602 and 604 through the metadata binder 606, connections and mashups created between webpages and technical documents produce these taxonomies based on keyword and category. These taxonomies connect the two systems and the metadata binder 606 ensures that when or if taxonomy changes occur in one system they are automatically replicated in the connected system.

On the content delivery or unified delivery platform 612 side, taxonomies can also be used as templates to render content for drill-down, intelligent navigation and more. Authors can nest keywords to define deeper levels of classification and you can add metadata to categories and keywords themselves. In some embodiments, unified delivery platform 612 can also include an indexing service 613 that is used to generate and allow for root queries based on taxonomies and corresponding content.

In some embodiments, a taxonomy tree can be exposed to webpage and/or technical document creators as an aid to build intelligent and dynamic navigation and display content based on user context.

Turning back to the example, the webpage author can utilize a widget 618 of the webpage 614 that provides an interface used to specify asset information according to a taxonomy structure (e.g., defining of categories and keywords). The widget 618 can appear when an asset such as the image 616 is dropped into the webpage 614 during webpage authoring. The webpage author can insert asset information such as a make and model of a car. Using this taxonomy structure to gather data, the unified delivery platform 612 can obtain data from technical documents in the system 604 in order to obtain technical information such as horsepower and fuel consumption. This information is reflected in window 620. Thus, webpage authors can cause the insertion of technical information into the webpage by specifying a minimal amount of data about a given asset. The unified delivery platform 612 completes the webpage by combining or mashing together the asset data and the technical document data regarding the assets. The taxonomy structure defines not only how the assets are described through use of the widget 618, but also a format and content of the window 620 that appears on the webpage 614. Also, in some instances, the taxonomy structure can be used to define a layout of the webpage 614 as well, which will indicate to an author where assets and technical document data should appear. In some embodiments, the layout of the webpage 614 can be determined by use of frameworks or customization features described in the embodiments of FIGS. 1A-3.

Using the taxonomy structure generated for the image 616 from the widget 618, the unified delivery platform 612 can automatically insert technical documents or data from the technical documents into the webpage using the taxonomy structure. This ensures that the webpage creators do not need to understand or have access to the technical documents, but these technical documents nevertheless are inserted into the webpage at runtime. In some embodiments, data is extracted from the technical document using the taxonomy structure and inserted into a window 620 that is a popup relative to the webpage 614. In another embodiment a link or URL 621 to the technical document is provided in lieu of or in addition to the data provided in the window 620.

In one or more embodiments, assets such as images and video can be inserted into the webpage at runtime as well. For example, assets can be stored and delivered from a content delivery network (referred to as CDN 640). Thus, webpage authors can insert assets from the CDN 640 or merely links to the assets that reside on the CDN 640. In some instances the asset is populated into the webpage at runtime by the unified delivery platform 612.

In general taxonomies can be used to classify content of a webpage and technical documents in multiple ways and to define a knowledge map of the content domain. The unified delivery platform 612 environment taxonomies can be used for website navigation and dynamic content assembly. For example, the unified delivery platform 612 stores the taxonomy structures created by the structure content management system 604. When a webpage is requested, the unified delivery platform 612 populates the webpage with the assets required such as images and video or other content as defined in the XML of the webpage, as well as the technical documentation related to the assets. In sum, these content types are populated based on the taxonomy structure for the webpage.

In general, authoring of both webpage and/or technical documents is made available through a client interface 624. A resulting webpage 614 (roughly corresponding to what is shown in the webpage creation interface 622) is created using the integration of FIG. 6 and includes modular components. For example, the webpage 614 includes a content link (sites link 628) and sites component 630 that bring in data from the web experience management system 602, while a docs link 632 and topic 634 include content obtained from the structure content management system 604. The respective content from each system 602 and 604 is arranged using a taxonomy.

As alluded to earlier, the taxonomy can be structured visually as a tree. Each leaf of the tree represents a data type and indicates content that can be pulled from either of the systems 602 and 604. In some embodiments, the taxonomy can be structure can be represented in a webpage layout as well. Thus, taxonomy and its tree structure can be converted into a template that can aid a webpage creator in placing content into the webpage.

Using the example webpage 614 illustrated, the taxonomy tree was used to create the basic layout of the webpage 614 and where content is inserted into the webpage 614. The content areas can be color coded and/or labeled to ensure that web content such as assets like images are placed in their correct location, while linked technical documentation appears in its desired location.

In sum, a taxonomy of the present disclosure allows for component-based webpage creation and management, as well as technical document authoring. These taxonomies act as a model for instructing authors (both webpage and technical) in deciding what content goes on what page. This structured model provides template webpages that have sections arranged according to a structure of a taxonomy. Thus, the taxonomy provides a predefined region schema which reflects a structure (predefined tree) of a webpage. The structure assists a user in putting the proper content in the proper place. The visual depiction guides the user on what types of content are allowed or not based on regional constraints.

FIG. 7 is a flowchart of an example method of the present disclosure that can be executed using, for example, the system 600 of FIG. 6. The method includes a step 702 of receiving a taxonomy structure for a webpage. As noted above, the taxonomy structure defines in general a layout of content for the webpage. The taxonomy also includes categories and keywords that are defined by assets selected for the webpage.

In some embodiments, the method includes a step 704 of receiving one or more technical documents generated by a technical documentation authoring system related to assets of the webpage. Additionally, the method includes a step 706 of combining, into the webpage, the assets selected by a website authoring platform and data of the one or more technical documents generated by the technical documentation authoring system, according to the taxonomy structure. In sum, this process creates a mashup of assets and their corresponding technical document content using the taxonomy structure. In some embodiments, the taxonomy structure is generated by the webpage authors and then subsequently shared with the technical document authors who use this shared taxonomy structure to create technical documents that can be easily searched and used within the webpage.

Once the webpage has been assembled with both assets and data from technical document(s) using the shared taxonomy structure, the method includes a step 708 of publishing the webpage.

In some embodiments, the method includes a step of generating the taxonomy structure for the webpage by a taxonomy generator of the website authoring platform. This step would occur prior to step 702 in some instances.

According to some embodiments, the process of sharing the taxonomy structure involves both pulling of the taxonomy structure from the website authoring platform and providing the taxonomy structure to technical document authors.

In other embodiments, taxonomy generator can create the taxonomy structure and produce a content mashup in a real-time manner. For example, the content pulled from each of the website authoring platform and the structure content system can be in response to real-time user navigation on a website. In an example use case, an end user is navigating on a website published in accordance with the present disclosure. In this example the user is browsing for new vehicles. When the user selects a vehicle to view and subsequently selects to view details regarding the interior features of the vehicle, the publishing server providing the webpage receives the user selections and the dynamic experience delivery service can create a content mashup between images of the vehicle obtained from the website authoring platform and specific technical details from technical documents related to the vehicle, and specifically technical documents related to the interior features of the vehicle. Thus, rather than providing the user with less specific technical documents related to the vehicle, the technical documents provided to the user are provided in accordance with the actual navigation behaviors of the user. In this way, the content mashup provided by the publishing server is based on the taxonomy structure and navigating behaviors of the end user.

Thus, in some embodiments, the method includes a step 710 of tracking user navigation and behaviors. This tracking of user navigation and behaviors can result in republishing the webpage to the user which will include a unique content mashup based on the available website components and technical documents that are germane to the user navigation and/or behaviors.

As noted above, the taxonomy structure comprises at least one category and at least one keyword for each of the assets. In certain embodiments, the assets are defined at least partially by metadata tags that are used by a metadata binder to represent the taxonomy structure to technical documentation authoring system.

FIGS. 8A-8C collectively illustrate an example diagram that illustrates a real-time capable system of the present disclosure. In general, the system comprises a core service 802, which corresponds to the web experience management system 502 (see FIG. 5) that provides component presentations such as a component presentation 804. The component presentations are indicative of content modules for a webpage. The content of the components is/are represented by metadata 806. The core service 802 can provide the metadata to a metadata binder (e.g., metadata binding provider) 808. The metadata 806 is illustrated as being integrated into a technical publication 810 of a structure content management system 812. Both the core service 802 and the structure content management system 812 comprise a publisher that allows each system/service to publish its content (e.g., publication) to a deployer 814. In some embodiments, the webpage content provided by the core service 802 is represented as a transport package 816. In some embodiments, component presentations are classified with keywords.

Also, the structure content management system 812 produces a DITA (Darwin Information Typing Architecture) package 818. In some embodiments, the DITA package 816 includes keywords that is/are indicative of the technical publication created by the structure content management system 812. A content API 820 couples with the deployer 814 to receive the packages from the core service 802 and the structure content management system 812.

These two content types are combined at a web application 822 and served as a page 824. In one example, the component presentation 804 and the technical publication 810 are combined at the web application 822. The ability to integrate the component presentation 804 and the technical publication 810 is enabled by a taxonomic structure.

Thus, the web application 822 mashes up content for delivery on a page 824 so that the page 824 comprises the component presentation created by the core service 802 and the technical documents of the structure content management system 812. The content obtained from the technical documents in view of the website components is based on a taxonomy structure created from the packages provided to the web application 822.

In this example, the content mashup is created at the web application 822 level. This enables real-time content mashup based on user behaviors. Thus, as a user is interacting with the page 824, the web application 822 provides user behavior data back through the content API 818 to the deployer 814 in order to fine-tune subsequent mashups as noted above.

Some of the above-described functions may be composed of instructions that are stored on storage media (e.g., computer-readable medium). The instructions may be retrieved and executed by the processor. Some examples of storage media are memory devices, tapes, disks, and the like. The instructions are operational when executed by the processor to direct the processor to operate in accord with the invention. Those skilled in the art are familiar with instructions, processor(s), and storage media.

It is noteworthy that any hardware platform suitable for performing the processing described herein is suitable for use with the invention. The terms “computer-readable storage medium” and “computer-readable storage media” as used herein refer to any medium or media that participate in providing instructions to a central processing unit (CPU) for execution. Such media can take many forms, including, but not limited to, non-volatile media, volatile media and transmission media. Non-volatile media include, for example, optical or magnetic disks, such as a fixed disk. Volatile media include dynamic memory, such as system RAM. Transmission media include coaxial cables, copper wire and fiber optics, among others, including the wires that comprise one embodiment of a bus. Transmission media can also take the form of acoustic or light waves, such as those generated during radio frequency (RF) and infrared (IR) data communications. Common forms of computer-readable media include, for example, a floppy disk, a flexible disk, a hard disk, magnetic tape, any other magnetic medium, a CD-ROM disk, digital video disk (DVD), any other optical medium, any other physical medium with patterns of marks or holes, a RAM, a PROM, an EPROM, an EEPROM, a FLASHEPROM, any other memory chip or data exchange adapter, a carrier wave, or any other medium from which a computer can read. The memory can also include solid state drives or equivalents thereof.

Various forms of computer-readable media may be involved in carrying one or more sequences of one or more instructions to a CPU for execution. A bus carries the data to system RAM, from which a CPU retrieves and executes the instructions. The instructions received by system RAM can optionally be stored on a fixed disk either before or after execution by a CPU.

The above description is illustrative and not restrictive. Many variations of the invention will become apparent to those of skill in the art upon review of this disclosure. The scope of the invention should, therefore, be determined not with reference to the above description, but instead should be determined with reference to the appended claims along with their full scope of equivalents.

	Number	Date	Country
Parent	13016989	Jan 2011	US
Child	16169901		US

Taxonomy Driven Multi-System Networking and Content Delivery

Information

Publication Number

Date Filed

Date Published

Inventors

Original Assignees

CPC

International Classifications

Abstract

Description

Claims

CROSS-REFERENCE TO RELATED APPLICATIONS

Continuation in Parts (1)