itter - @omowizard
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20120116/51865579/attachment.html>
ime.upv.es
Universidad Polit?cnica de Valencia (UPV)
Camino de Vera, s/n, Edificio G-8, Acceso B, 3? planta
Valencia ? 46022 (Espa?a)
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20120116/6e3fb74d/attachment.html>
--
An HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20120116/f2d17f07/attachment.html>
After checking the schema, I have seen some places that the schema
(specifically basetypes.xsd) is missing things that are indeed
supported by ADL (namely assumed_values, lists, etc.)
What is the process to update the schema?
tp://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20120116/b0841549/attachment.html>
On 16/01/2012 06:12, David Moner wrote:
> A possible problem I can envision is that this opens the door to the
> creation of invalid archetypes without the possibility of validating
> them at design time.
>
> A quick and dirty example just to get the idea. In an archetype, the
> HISTORY.origin i
6 matches
Mail list logo