- From: Kathryn Blackmond Laskey <klaskey@gmu.edu>
- Date: Sun, 29 Jul 2007 13:44:13 -0400
- To: Giorgos Stoilos <gstoil@image.ece.ntua.gr>, Peter.Vojtas@mff.cuni.cz, 'Ken Laskey' <klaskey@mitre.org>
- Cc: 'Kathryn Blackmond Laskey' <klaskey@gmu.edu>, public-xg-urw3@w3.org, 'Umberto Straccia' <umberto.straccia@isti.cnr.it>
Folks, > > I think even in use cases we have to be specific, in which form are >> data (annotated, structured, text), from different sources,...how to >> integrate data (not speaking about trust) what about user ... > >As for this point I fully agree that Use Cases must be as specific as >possible. Why don't we focus on the use cases we developed for exactly this purpose? Consider the appointment making use case. Suppose my primary care physician wants me to see a specialist. - I care about cost. If the specialist is in my insurance network, I pay a flat co-payment of $35. If the specialist is out-of-network, I pay the co-pay, plus 20% of what the specialist charges in excess of my co-pay. - I want the specialist to be near my home, or if not, then near my workplace. I would prefer no more than 15 minutes driving time. I would prefer a location that doesn't get too congested at rush hour, because otherwise a 15 minute driving time could easily stretch to 30 or 45 minutes. - I need to see this person as soon as possible. I have checked my calendar. Monday or Wednesday morning would be most convenient, but Thursday afternoon would be acceptable, and Friday might be OK, depending on whether the meeting that was tentatively scheduled that day will actually occur. What do we need to be able to represent to solve this problem? K
Received on Sunday, 29 July 2007 17:44:49 UTC