The following fragment of an instance of hotel ontology (this time represented in
an N3 notation) depicts user (Karol) profile as it is represented in our system:
:KarolOp n ons a sys:Op n onsSet;
sys:conta nsOp n on
[sys:about hotel:Pool;
sys:hasClassification sys:Interesting;
sys:hasNormal zedProbab l ty 0. ].
[sys:about hotel:Exerc seRoom;
sys:hasClassification sys:Interesting;
sys:hasNormal zedProbab l ty 0. ].
[sys:about res:A rCond t on ng;
sys:hasClassification sys:Interesting;
sys:hasNormal zedProbab l ty 0. ].
[sys:about hotel:BathroomAmen t es;
sys:hasClassification sys:Interesting;
sys:hasNormal zedProbab l ty 0. ].
[sys:about hotel:Iron ngBoard;
sys:hasClassification sys:NotInteresting;
sys:hasNormal zedProbab l ty 0. ].
[sys:about hotel:Iron,
sys:hasClassification sys:NotInteresting;
sys:hasNormal zedProbab l ty 0. ].
The previous hotel profile of Karol, tells us that he likes to stay in hotels with swimming
pool and exercise room, while the availability of an iron and ironing board is
inconsequential to him.
Obviously, somewhere in the system we have to store, in some form, information
about the user.
Pages:
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696