Add LogEntry + Shape

[PHochmann]

No description provided.

[kragall]

Hi, so I checked with the current version of the Clearing House and saw that the originally requested structure doesn't fit anymore. So I wondered if it's possible to adjust the changes to fit this structure:

• timestamp: This is the timestamp recording the date when this message was logged by the CH
• transaction_id: This is basically a counter with a unique (unique in the database) number for each stored message.
• process_id: This is a string that describes the process under which the message is logged. Think of it as the label of the folder under which the message has been filed together with other messages.
• document_id: This is a unique (unique in the process) id in the form of a uuid for the stored message
• client_id: This is the unique id of the client that sent the stored message taken from the DAT the client sent with the original LogMessage
• server_id: This is the unique id of the server that stored message in form of the id of private key
• hash: This information is used for integrity protection in the CH
• signature: This contains a cryptographic signature of the data
• payload: This optional field contains the payload of the original LogMessage

Please note that in the original request LogEntry contained a LogMessage. This is not the case anymore.

[PHochmann]

Hi, so I checked with the current version of the Clearing House and saw that the originally requested structure doesn't fit anymore. So I wondered if it's possible to adjust the changes to fit this structure:
* payload: This optional field contains the payload of the original LogMessage

Is this payload a string or another Data Type property, or does it point to another object? I can't find any information about what a LogMessage's payload looks like.

[kragall]

The payload does not reference another entity, so it's probably best to use a string

[JohannesLipp]

The payload does not reference another entity, so it's probably best to use a string

Thanks for the info! @PHochmann please implement it as DatatypeProp with xsd:string then. Thank you in advance!

[PHochmann]

Edits are under taxonomies/Message.ttl @kragall Please have a look

[PHochmann]

All requested changes are now resolved, feel free to review and merge. Thanks!