/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/20121128/157e5882/attachment.html
://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20121128/efd29717/attachment.html
thanks, Peter, I will work on it tomorrow.
Bert
Verstuurd vanaf mijn iPad
Op 27 nov. 2012 om 23:06 heeft Peter Gummer peter.gummer at
oceaninformatics.com het volgende geschreven:
Bert Verhees wrote:
I don't have a Jira account at your site, if I have, I post my XSD's as a
proposition.
/openehr-technical_lists.openehr.org/attachments/20121128/dd57de03/attachment.html
:
http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20121128/9e4498ec/attachment.html
-technical_lists.openehr.org
-- next part --
An HTML attachment was scrubbed...
URL:
http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20121128/7892e8c4/attachment-0001.html
openEHR-technical at 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/20121128
On 11/27/2012 10:42 PM, Seref Arikan wrote:
I'll attempt to comment on Bert's problem, hoping I understand it :)
When you do not have a root element definition in an XSD, you can't
create XML documents which will be valid according to that XSD. What
Bert is saying is, if we had a bunch of
On 11/27/2012 10:42 PM, Seref Arikan wrote:
I'll attempt to comment on Bert's problem, hoping I understand it :)
When you do not have a root element definition in an XSD, you can't
create XML documents which will be valid according to that XSD. What
Bert is saying is, if we had a bunch of root
Hi!
I see several use cases for sending and storing XML pieces smaller
than compositions etc as valid XML documents.
What about creating a separate (but official) file with those root
elements in the same namespace as the other schema components? That
way implementers can choose if they want
On 11/28/2012 09:46 AM, Erik Sundvall wrote:
P.s. Bert, I think you may have interpreted the tone of some
comments/replies as more hostile than they were intended by the
senders. It is sometimes hard to understand what you and others asking
for so it takes some rounds of questions to clarify
I didn't realize that the XSD file has no license. Please assume a
CC-BY license, which is the same we use for 13606 schemas.
2012/11/28 Erik Sundvall erik.sundvall at liu.se:
Hi!
I see several use cases for sending and storing XML pieces smaller
than compositions etc as valid XML documents.
was scrubbed...
URL:
http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20121128/bed382fb/attachment-0001.html
/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/20121128/b8c3e8ff/attachment-0001.html
/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/20121128/456ff14d/attachment-0001.html
It seems some of my messages are send twice.
I don't know why.
Sorry, this is unintentionally.
Bert
I'm unclear on the outcome of this confusing discussion. For the lack of
demographic XSD, what should be used is an XSD that is compatible with
the existing ones. For the other questions, they're at a level of detail
I don't know in XSD. But they should be answerable one way or the other.
So
17 matches
Mail list logo