Second draft: Hard-coded profile card #2
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This merge request adds some further infrastructure and a first set up to show a (currently hard-coded) RDF profile in various formats.
The format serialization is provided by the PDS Interop Flysystem RDF plugin.
When the application is run locally, the profile lives at http://localhost/profile/card`. It does not yet have an HTML representation. The turtle format is shown by default, others can be shown by adding a file extension (for instance http://localhost/profile/card.jsonld will show the JSON-LD format). Content negotiation from the headers still needs to be added.