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. thoughtS?
-- Kind regards, Eng. Pablo Pazos Gutiérrez http://cabolabs.com Date: Mon, 27 Jul 2015 08:23:49 +0200 Subject: Re: Term set for DV_PARSABLE.formalism From: yamp...@gmail.com To: openehr-techni...@lists.openehr.org CC: openehr-implementers@lists.openehr.org Probably was left this way to deal with the ones that don't have an official mime, like adl El 27/7/2015 7:11, "pablo pazos" <pazospa...@hotmail.com> escribió: Reading the specs I realize that there isn't a term set for DV_PARSABLE.formalism and it is a free text attribute. Since stuff like XML, JSON, CSV, etc. are in fact modeled by DV_PARSABLE, and those have a MIME type associated (text/xml, application/json, text/csv, ...), shouldn't we define a term set for that attribute like we have for DV_MULTIMEDIA.media_type? (of course this attribute is CODE_PHRASE and not String like "formalism"). -- Kind regards, Eng. Pablo Pazos Gutiérrez http://cabolabs.com _______________________________________________ openEHR-technical mailing list openehr-techni...@lists.openehr.org http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org _______________________________________________ openEHR-technical mailing list openehr-techni...@lists.openehr.org http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
_______________________________________________ openEHR-implementers mailing list openEHR-implementers@lists.openehr.org http://lists.openehr.org/mailman/listinfo/openehr-implementers_lists.openehr.org
