Support newlines and formatting in DV_TEXT
Description
CR fixes the problem in
is duplicated by
Activity
Ian McNicoll December 21, 2018 at 4:47 PM
I'm happy with that. Good, strong guidance but short of mandation.
Thomas Beale December 21, 2018 at 12:26 PM
I have replaced the TBD on subset of COmmonMark with some text. See just above this heading: https://specifications.openehr.org/releases/RM/latest/data_types.html#_usage_in_dv_text_instances
Thomas Beale December 21, 2018 at 11:03 AM
- I think you are right - I will change the enumerated value to 'markdown', and just document that CommonMark is the one to use.
Ian McNicoll December 21, 2018 at 9:19 AM
I'm not so bothered about enforcing CommonMark or any other Markdown flavour. AFAICT this is still a pretty unstable space and as long as the text is reasonably human-readable without rendering for safety purposes, I think we may have to leave it to local policy.
We can certainly express a preference but there is a danger that we will back the wrong horse.
Sebastian Garde December 20, 2018 at 5:00 PM
https://specifications.openehr.org/releases/RM/latest/data_types.html#_formatting_and_hyperlinking : ...is no longer use_d_ to represent...
There are still two TBDs re commonmark in there...if we don't make an assumption about minimum version or subset of commonmark now, it will be hard to enforce it later?
Document newlines as being allowed in DV_TEXT; add advice to use this instead of DV_PARAGRAPH by preference; describe how to convert DV_PARAGRAPH instance to a DV_TEXT with newlines.