For each scenario, we find N3 data illustrating the scenario. The decisions and alternatives we have are taken into account.
Claudia and Berit had their wedding in Holland.
Claudia wants to have access to Dirk's rating and other annotations.
The system sends an email including the pictures and their metadata.
One year later the data should still be accessible.
Now Claudia wants to find all pictures that depict herself and Berit.
Claudia has rated and tagged the files. Dirk integrates the files into his own system and changes tags and ratings. Later he needs to determine which music Claudia likes because he will act as the DJ at her wedding.
Current state of data in KDE4:
<urn:A> {
<file:///home/foobar/someimage.jpg>
a nfo:Image ;
nao:desciption "Ugly!" .
}
<urn:B> {
<urn:B> a nrl:GraphMetadata .
<urn:A> a nrl:IntanceBase ;
nao:created "2009-11-05T...."^^xsd:dateTime .
}
<urn:C> {
<file:///home/foobar/someimage.jpg>
nao:rating 5 .
}
<urn:D> {
<urn:D> a nrl:GraphMetadata .
<urn:C> a nrl:IntanceBase ;
nao:created "2009-11-06T...."^^xsd:dateTime .
}
Todo
To exclude one property we would need privacy settings on the property level. This would mean storing each property in its own graph which is not done in KDE at the moment (but would be easy to achieve).
Then we could easily mark the nao:description as non-public.
He needs the music files to be untraceable to him. However he still wants ratings and tags to be preserved.
He wants to share work information using his SAP ID and wedding pictures using his personal ID.
The information about who wrote which comment is preserved.
When he comes home he syncs his phone again and the tags are synced, too.
The phone gives results from his home computer with optional access to download them.