Adding metadata to a notification through RDF injection

[Dexagod]

Adding metadata to a notification through RDF injection

It may be useful to add metadata to an already created notification, independently of the RDF format used to create the notification. This can be done by

• parsing the notification into Quads (using rdf-parse)
• adding the desired metadata quads
• re-serializing the notification to a desired format (using rdf-serialize).

However, in order add metadata to the root of the notification, we need a reference to this root id. As notifications do not really have an id on creation (they have not yet been posted), we maybe should enforce that notifications cannot have a root id. Additionally, I ran into the problem that the rdf-parse](https://www.npmjs.com/package/rdf-parse)) library allocates a random blank node id to the root of the notification if no valid baseIRI is provided, making it difficult to allocate the metadata to the root. (I currently solved this issue by using a temporary urn:Notification id as baseIRI, but this is not a real solution)

Concrete question:

• Can we expect notifications to not have an identifier for the notification root.
• How can the issue be solved with rdf-parse allocating a random blank node identifier to the root node.