Maindata
This is how the 'Maindata' resources work in our proposed structure: Each Citizen has a Maindata container in their own Pod As of now these contain one resource: maindata.ttl
<https://id.inrupt.com/guddii> <http://xmlns.com/foaf/0.1/name> "Florian Gudat".
<https://id.inrupt.com/guddii> <http://xmlns.com/foaf/0.1/firstName> "Florian".
<https://id.inrupt.com/guddii> <http://xmlns.com/foaf/0.1/lastName> "Gudat".
<https://id.inrupt.com/guddii> <http://xmlns.com/foaf/0.1/title> "Sir".
<https://id.inrupt.com/guddii> <http://xmlns.com/foaf/0.1/homepage> "flo.de".The purpose of this resource is to be used with other service providers such as the Tax Office App. It is not the same as the profile resource of the WebID
Tax Data
Tax form data is saved in separate Pods for each citizen and can be accessed by that person, but not changed.
Messages
To enable information flow between Government Apps, such as the Tax Office app and Citizens, each citizen Pod has an inbox Container. If there are new documents a message will be sent to the public inbox.
A message contains metadata using the Schema.org/message type. This contains information about sender, recipient and timestamp.
Additional information is given in rdf syntax
<https://storage.inrupt.com/bc19cca5-1d8c-4b61-bd9f-287b04878050/inbox/message>
a <http://schema.org/Message> ;
<http://schema.org/dateSent> "2023-07-13T12:00:00.000Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
<http://schema.org/recipient> <https://id.inrupt.com/maja> ;
<http://schema.org/sender> <https://id.inrupt.com/taxofficeapp> ;
<http://schema.org/text> "Your Tax Data has been uploaded to your Pod at the Tax Office" .
<https://id.inrupt.com/maja>
<http://schema.org/subjectOf> <https://storage.inrupt.com/965f1474-6227-4601-a92a-9f1d09980adb/taxData-1688512759625.ttl> ;
<http://www.w3.org/ns/pim/space#storage> <https://storage.inrupt.com/965f1474-6227-4601-a92a-9f1d09980adb/> .