Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow markdown formating in "Description" #1125

Open
stranak opened this issue Oct 7, 2024 · 3 comments
Open

Allow markdown formating in "Description" #1125

stranak opened this issue Oct 7, 2024 · 3 comments

Comments

@stranak
Copy link
Member

stranak commented Oct 7, 2024

Allow at least emphasis and code via ** and ``

@stranak
Copy link
Member Author

stranak commented Oct 7, 2024

See for instance this record that tries to use such formating: http://hdl.handle.net/11234/1-5672

@kosarko
Copy link
Member

kosarko commented Oct 21, 2024

What I'm thinking: We should be careful with that, when we officially support this shouldn't we somewhere express the different semantic, eg. by specifying text/markdown (https://www.rfc-editor.org/rfc/rfc7763). Should we drop the formatting in (oai-pmh) exports?

@stranak
Copy link
Member Author

stranak commented Oct 21, 2024

Hmm, those are good points. Especially the exports are something to worry about. If we supported e.g. tables in markdown, it could break into a complete garbage when formating is removed. We certainly do not want that.

Are there some precedents, or is metadata always and everywhere (by definition) plain text?

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

No branches or pull requests

2 participants