On 28/07/2015 18:49, pablo pazos wrote:
If that's the case, we lose the coding system / terminology of the
mime types that are defined.
It would be better to make DV_PARSABLE.formalism of type CODE_PHRASE
instead of String and use "local" for the terminology_id of those
formalisms that doesn't have a mime type.
well actually we could do that and put all those other formalisms into
the openEHR terminology.
The original idea was to allow (encourage) MIME types as strings, and
then outside of MIME, any other formats just as their own short string,
e.g. 'mp5' (imagine it exists), or 'adl'.
There are a lot of formats that are essentially text/plain, but the
format is actually parseable, e.g. glif3, most programming languages and
so on. So 'text/plain' isn't that useful a thing to know.
I wonder if we have to give in and have two fields, one that is a MIME
type field (the current one) and a second field that has a term defining
the semantic format, mostly applicable when the MIME type field is
text/plain, text/xml and other text types.
- thomas
_______________________________________________
openEHR-technical mailing list
[email protected]
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
