Bert, You can define elements to be type of an abstract type allowing any concrete subtype in an instance. This is the intent of the items element, to allow any rotatable concrete type to be represented in a document with root element of items. Heath On Nov 27, 2012 6:19 PM, "Bert Verhees" <bert.verhees at rosa.nl> wrote:
> On 11/27/2012 04:26 AM, Thomas Beale wrote: > >> On 26/11/2012 17:02, Bert Verhees wrote: >> >>> Thanks Athanasios and Diego, >>> >>> It is easier to download then to write it myself ;-) >>> >>> But still I wonder why the OpenEHR-community is not offering these. >>> >> >> I think it just did ;-) >> >> Early in 2013, the specifications will be start being revamped. That will >> be an opportunity for people to offer & improve changes and updates to >> existing specifications. >> > > Why didn't the website offer this XSD, for so many years. > It is especially important because Sam and Seref stress the importance of > the XSD and that they are maintained in formal way. > That I never realized. > Under these circumstances it almost begins to look like a statement, but I > couldn't imagine what. > > So it is just a small question, but it seems hard to answer. > > But early 2013 is very near, so I will be patient :) > I can live with the XSD from Diego, which looks very well made. > > Thanks again Diego. > > regards > Bert Verhees > > > > > > ______________________________**_________________ > openEHR-technical mailing list > openEHR-technical at lists.**openehr.org<openEHR-technical at > lists.openehr.org> > http://lists.openehr.org/**mailman/listinfo/openehr-** > technical_lists.openehr.org<http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org> > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20121127/28ef877b/attachment.html>
