heckman thesis.pdf
heckman thesis.pdf
heckman thesis.pdf
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
xviii Contents<br />
3.1.4 Deep Map User Modeling System . . . . . . . . . . . . . . . . . . . 35<br />
3.2 Metadata Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37<br />
3.2.1 Dublin Core Metadata . . . . . . . . . . . . . . . . . . . . . . . . . 37<br />
3.2.2 Customer Profile Exchange . . . . . . . . . . . . . . . . . . . . . . . 39<br />
3.2.3 HumanML, the Human Markup Language . . . . . . . . . . . . . . . 40<br />
3.2.4 The CC/PP Framework . . . . . . . . . . . . . . . . . . . . . . . . . 41<br />
3.3 External Ontologies and Knowledge Bases . . . . . . . . . . . . . . . . . . . 41<br />
3.3.1 SUMO/MILO Ontologies . . . . . . . . . . . . . . . . . . . . . . . 42<br />
3.3.2 Cyc Knowledge Base . . . . . . . . . . . . . . . . . . . . . . . . . . 44<br />
3.3.3 WordNet Lexicon . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45<br />
3.3.4 FrameNet Lexical Resource . . . . . . . . . . . . . . . . . . . . . . 46<br />
3.4 Design Decisions and Goals . . . . . . . . . . . . . . . . . . . . . . . . . . 48<br />
3.4.1 Discussion about U2M and Related Systems . . . . . . . . . . . . . 48<br />
3.4.2 Discussion about UbisWorld and Related Ontologies . . . . . . . . . 49<br />
3.4.3 Some Design Decisions and Goals . . . . . . . . . . . . . . . . . . . 49<br />
II Knowledge Representation and Knowledge Management 51<br />
4 Situational Statements & Extended Resource Identifiers 53<br />
4.1 How to Represent Information about Complex Situations? . . . . . . . . . . 53<br />
4.1.1 Situational Descriptions in the Airport Scenario . . . . . . . . . . . . 53<br />
4.1.2 Remarks on Design Decisions for the User Model Language . . . . . 54<br />
4.1.3 From RDF to Extended Triples . . . . . . . . . . . . . . . . . . . . . 57<br />
4.2 The Model of SITUATIONALSTATEMENTS . . . . . . . . . . . . . . . . . . 58<br />
4.2.1 The Mainpart Box . . . . . . . . . . . . . . . . . . . . . . . . . . . 59<br />
4.2.2 The Situation Box . . . . . . . . . . . . . . . . . . . . . . . . . . . 61<br />
4.2.3 The Explanation Box . . . . . . . . . . . . . . . . . . . . . . . . . . 62<br />
4.2.4 The Privacy Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62<br />
4.2.5 The Administration Box . . . . . . . . . . . . . . . . . . . . . . . . 63<br />
4.3 The Model of SITUATIONREPORTS . . . . . . . . . . . . . . . . . . . . . . 64<br />
4.3.1 From Situational Descriptions to SITUATIONREPORTS . . . . . . . . 64<br />
4.3.2 A SITUATIONREPORT in the Airport Scenario . . . . . . . . . . . . 66<br />
4.3.3 Aggregating Statements in SITUATIONALREPOSITORIES . . . . . . 67<br />
4.3.4 Remarks about the Closed World Assumption . . . . . . . . . . . . . 67<br />
4.4 The Syntax of SituationML and UserML . . . . . . . . . . . . . . . . . 67<br />
4.4.1 SITUATIONALSTATEMENTS within SituationML . . . . . . . . . 68<br />
4.4.2 Syntax Variations on SituationML/XML . . . . . . . . . . . . . . 68<br />
4.4.3 SituationML/RDF and SituationML/OWL . . . . . . . . . . . 70<br />
4.4.4 Discussion: Why did we introduce SituationML? . . . . . . . . . . . 72<br />
4.5 Extended Resource Identification . . . . . . . . . . . . . . . . . . . . . . . . 74<br />
4.5.1 Extended URI References with Namespaces . . . . . . . . . . . . . . 75<br />
4.5.2 UbisIdentifier (Ubid) . . . . . . . . . . . . . . . . . . . . . . . . . . 75<br />
4.5.3 UbisExpression (Ubex) . . . . . . . . . . . . . . . . . . . . . . . . . 77<br />
4.5.4 UbisList (Ubli) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79