Thesis full text (PDF) - Politecnico di Milano

More documents

Recommendations

Info

3.1.2 Datatype Component Similarly to the Class Component, the Datatype Component explores the axioms in the knowledge base and deducts UML datatypes either by name, by being disjoint to other datatypes, by their defined properties, or by being instantiated by the condition values. Figure 3.3: Datatype Component A combination of the previous conditions extracts the corresponding data types satisfying all the conditions. The Datatype Component is depicted in figure 3.3 as a UML class diagram. 3.1.3 Property Component The Property Component defines a set of extraction rules for retrieving UML properties (attributes and roles) from the knowledge base. The selection conditions to be applied are: PropertyOfName extracts properties by name, PropertyDisjointOfProperty extracts the properties being disjoint to some values, PropertyInverseOfProperty extracts the properties being inverse to some values, PropertyWithDomain and PropertyWithType extract properties by their defining classes/datatypes, PropertyWithPropertyValue retrieves the properties by their values, PropertyIsTransitive retrieves the properties being transitive, PropertyWithCardinality 30
etrieves the properties by their cardinality values, PropertyIsDatatypeProperty retrieves the properties of data values, and PropertyIsObjectProperty retrieves the properties of objects. Figure 3.4: Property Component 3.1.4 Hierarchy Components The Hierarchy components explore the inclusion axioms in the knowledge base regarding hierarchies of UML classes or properties, and to deduct the taxonomy defined upon them. If no selection condition is specified, they extract the complete taxonomy. Otherwise, they retrieve the elements in the knowledge base (classes or properties) satisfying the corresponding inclusion assertions. The selection conditions for the Classes Hierarchy Component are the following: the DirectSuperClass and SuperClass for extraction of the direct superclass (father) or all the superclasses (ancestors) of the given classes; the DirectSubClass and SubClass for extraction of the direct subclass (child) or all subclasses (descendants) of the given classes; the MostGenericClass and MostSpecificClass for retrieving the most generic or the most specific classes in the hierarchy. A combination of the previous conditions extracts the hierarchy 31
Page 1 and 2: POLITECNICO DI MILANO V Facoltà di
Page 3 and 4: Table of Contents Abstract ........
Page 5 and 6: 1. Introduction At present the Web
Page 7 and 8: • Definition of the formal repres
Page 9 and 10: This approach overcomes the develop
Page 11 and 12: Both the teleological and the ontol
Page 13 and 14: consists of a data schema, describi
Page 15 and 16: high-level business rules, written
Page 17 and 18: Thanks to the automatic generation
Page 19 and 20: 2.4.2 RDF Resource Description Fram
Page 21 and 22: Third, besides the aforementioned r
Page 23 and 24: The XMI serialization of UML [33] e
Page 25 and 26: 2.9.2.1 Pellet Pellet 1 [47] is an
Page 27 and 28: 3. Semantics Web based Recommendati
Page 29: them by invoking respectively the c
Page 33 and 34: Figure 3.6: Instance Component 3.1.
Page 35 and 36: 3.1.8 Add Components The Add compon
Page 37 and 38: Add Class Component ClassDisjointOf
Page 39 and 40: PropertyDisjointOfProperty (for ins
Page 41 and 42: first-class citizens, we have more
Page 43 and 44: Figure 3.17: Remove Datatype Compon
Page 45 and 46: 3.1.19 Remove Instance component Th
Page 47 and 48: 3.2.4 Export-XMI-from-KB component
Page 49 and 50: 3.3.1.2 Properties of a class patte
Page 51 and 52: 3.3.1.5 Instances of a class assumi
Page 53 and 54: 3.3.1.8 Instances of a class assumi
Page 55 and 56: 3.3.2.2 Remove property value for a
Page 57 and 58: 3.4.2 Application Specification In
Page 59 and 60: Action • View Notification: Group
Page 61 and 62: Send Group Invitation Actor: Group
Page 63 and 64: A user can recommend friend as Frie
Page 65 and 66: In the figure 3.37, a User browsing
Page 67 and 68: Through the entry unit in figure 4.
Page 69 and 70: Figure 4.2: Example of WebML hypert
Page 71 and 72: Description Classes Hierarchy Unit
Page 73 and 74: Add PropertyValueAxiom Input: manda
Page 75 and 76: 4.4. The top segment of the page is
Page 77 and 78: page otherwise it will go to the er
Page 79 and 80: We are showing current user’s inf
Page 81 and 82:
current user is sending a friend in
Page 83 and 84:
The information of a particular gro
Page 85 and 86:
Figure 4.20: HTML view to Post New
Page 87 and 88:
the application domain as extended
Page 89 and 90:
Knowledge Instances Yes Yes Yes Yes
Page 91 and 92:
OWL DL KB Framework CLASS HIERARCHI
Page 93 and 94:
of a specific group members of the
Page 95 and 96:
[22] OMG UML (2007), Unified Modeli
Page 97:
[56] BRAMBILLA, M., CERI, S., FRATE
show all

Thesis full text (PDF) - Politecnico di Milano

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?