Philipp Hochmann

I agree this is necessary, since the functions and especially order of function calls needed is not very intuitive.

See https://github.com/PhilippHochmann/ctable/commit/f215abfda7483aeead693c7048b031d956858006 for function documentation. May be extended by example code snippets and explanations.

Files from examples/, that currently fail SHACL validation: ``` to_test/DAT_PAYLOAD.jsonld failed [Node=_:B7200830382e8ad611377271923b3c26a Path= (DatPayloadShape): Exactly one ids:iss property must point from ids:DatPayload to ids:Connector via an IRI., Node=_:B7200830382e8ad611377271923b3c26a Path= (JwtPayloadShape):...

Update: Currently waiting for GitHub release 4.2.0 to invoke Documentation generator

See https://github.com/International-Data-Spaces-Association/InformationModel/tree/feature/log-entry

Updated requirements (as given by @kragall ): * [x] timestamp: This is the timestamp recording the date when this message was logged by the CH * [x] transaction_id: This is...

See https://docs.github.com/en/pages/getting-started-with-github-pages/about-github-pages#mime-types-on-github-pages: "While you can't specify custom MIME types on a per-file or per-repository basis, you can add or modify MIME types for use on GitHub Pages. For more information,...