The hypermedia product’s ontology
In the same line of thinking, a final product ontology (or website ontology) always depends on a publication genre and a core ontology that defines the structure of a web page and the graphical components able to be used in creating it. A web page is recursively divided, into several display areas, each of which contains a graphical component. This can be a standard HTML5 component like the video player, a freely accessible online widget like Google Maps, or even a simple textbox. The final product ontology extends the core ontology by defining a structuration of the page particular to the corresponding publication genre.
This structuration can be considered as the web page’s model graph and defined in two different ways:
- - as a partially instanced graph that designates and positions the display areas before composing the web page. For example, the banner area must be located at the top of the page, followed vertically by the main menu area. The area below this menu must be horizontally composed of two areas: to the left, the vertical menu; to the right, the player.
- - with the help of OWL2 expressions, which defines restrictions on the areas constituting a web page.
The transformation engine analyzes the publication graph, applies behaviors to its elements and generates the website’s graph in accordance with the final product ontology. This graph formalizes the structure of each page to be created and the graphic components to be displayed.
The publication’s configuration
In order to personalize the use of rules and give the author a chance to define the website structure that he desires, we have made it possible to configure these rules. The author can thus personalize the different components of the web page by activating and deactivating certain properties. These components may be: the main menu for access functionality, the left menu for contextual access, the links to the named entities, etc. These configuration options are defined as an ontological extension of the publication ontologies that allow certain properties to be annotated. Figure 4.17 shows the detailed architecture of the publication system that we propose.
Figure 4.17. General architecture of the publication system