Skip to content
This repository has been archived by the owner on Nov 13, 2023. It is now read-only.

Specify which fields can contain markdown #33

Open
olinux opened this issue Apr 25, 2022 · 3 comments
Open

Specify which fields can contain markdown #33

olinux opened this issue Apr 25, 2022 · 3 comments

Comments

@olinux
Copy link
Collaborator

olinux commented Apr 25, 2022

We encountered markdown syntax in some of the "controlled terms" - however, the description of those properties (e.g. "description") in the schema doesn't tell anything about it. From a consumer (and validation) perspective, it would be nice to flag those fields which are containing a specific syntax.

@lzehl
Copy link
Collaborator

lzehl commented Apr 25, 2022

@olinux in principle we could assume for all strings markdown syntax, no?

@lzehl
Copy link
Collaborator

lzehl commented Apr 25, 2022

based on our in person discussion we indeed go with the option "_syntax": "markdown" for string values. that way the schema validator will ignore the definition but interpreters such as the KG can use it as a controlled statement for fields that should be interpreted via markdown

@lzehl
Copy link
Collaborator

lzehl commented Apr 25, 2022

I'll prepare the PR for the respective schemas and let you know when to update the pipeline

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants