| 29 | | * a popup window opens after clicking the button "new relation" |
| 30 | | * in this window Paul has to say define a name for the new relation __and__ a name for the inverse relations |
| 31 | | * And Paul has to decide if his new relations are subProperties of either pimo:related, pimo:PartOf or pimo:hasTopic |
| 32 | | * After clicking create Button in this popup the system creates the triples mentioned above |
| | 29 | * Paul sees something like this: http://www.dfki.uni-kl.de/~sauermann/2006/01-pimo-report/img-guithing.png |
| | 30 | * below the relations, is the '''add relation''' field, paul clicks there. |
| | 31 | * the relation can be entered in a text-combo field. |
| | 32 | * after typing the relation name, "attends", no match is found and a "define" button gets visible/enabled. |
| | 33 | * "define" button blinks or does something else to catch attention |
| | 34 | * Paul presses the "define" button |
| | 35 | * he clicks the button "define" |
| | 36 | * a popup window opens |
| | 37 | * in this window Paul has to define a name for the new relation, "attends" is already filled in |
| | 38 | * __and__ a name for the inverse relations |
| | 39 | * Paul has to decide if his new relations are subProperties of either pimo:related, pimo:PartOf or pimo:hasTopic |
| | 40 | * the user interface says "is this a kind of: - related-partOf-hasPart-hasTopic-isTopicOf?" |
| | 41 | * After clicking create Button the property is available in the text field. The define button is still there, but is not catching attention anymore |
| | 42 | * Paul searches for Peter in the field right of "attends", enters "Pete" |
| | 43 | * Alternatives are shown, Paul selects "Peter". |
| | 44 | * Paul presses OK - '''now everything is saved''' |
| | 45 | * the new property is created |
| | 46 | * the relation between the InvestorMeetingRome and Peter is stored in the PIMO-storage |
