Hi,
I am trying to parse a Template using Zilics donated code
but for almost all of templates, at least ones which I tried, that exist in OceanInformatics Template folder I receive this parsing error
br.com.zilics.archetypes.models.rm.exception.XmlParserException: Invalid namespaces at …
Does anyone have any idea about it? Is it a problem with templates or should I change something is settings
I’ve tried Parser for Archetypes and it seems there’s no problem there
Regards
Pariya
PhD Student
Interaction Design Division
Department of Computing Science and Engineering
Chalmers University of Technology
Email: hajar.kashfi@chalmers.se
Office:+46 (0)31 7725407
Mobile Phone: +46 (0)707222815
Web: http://www.cs.chalmers.se/~hajar.kashfi/
Visit: Room Simula B, House Svea, Campus Lindholmen
Postal adress:
Email: hajar.kashfi at chalmers.se
Phone: +46 31 772 5407
Office: Room Simula B, House Svea, Campus Lindholmen
Postal Address: Chalmers University of Technology, SE- 412 96 Gothenburg, Sweden
Ocean informatics file radiology_report.oet
Zilics example file Template.oet
It seems like the Zilics file prefixes everything with “TEMPLATE_”
So it would seem that the format (xsd) is not the same?
regards
Olof
20 nov 2008 kl. 12.20 skrev Pariya Kashfi:
I tried one existing Template from Zilic company in
resources–>xml–> template folder and there’s no problem when I run it
I wonder if they are based on the same specification, why this happens?
Hi,
I am trying to parse a Template using Zilics donated code
but for almost all of templates, at least ones which I tried, that exist in OceanInformatics Template folder I receive this parsing error
br.com.zilics.archetypes.models.rm.exception.XmlParserException: Invalid namespaces at …
Does anyone have any idea about it? Is it a problem with templates or should I change something is settings
I’ve tried Parser for Archetypes and it seems there’s no problem there
Regards
Pariya
PhD Student
Interaction Design Division
Department of Computing Science and Engineering
Chalmers University of Technology
Email: hajar.kashfi@chalmers.se
Office:+46 (0)31 7725407
Mobile Phone: +46 (0)707222815
Web: http://www.cs.chalmers.se/~hajar.kashfi/
Visit: Room Simula B, House Svea, Campus Lindholmen
Postal adress:
Email: hajar.kashfi at chalmers.se
Phone: +46 31 772 5407
Office: Room Simula B, House Svea, Campus Lindholmen
Postal Address: Chalmers University of Technology, SE- 412 96 Gothenburg, Sweden
openEHR-technical mailing list
openEHR-technical@openehr.org
http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
Regards
Pariya
PhD Student
Interaction Design Division
Department of Computing Science and Engineering
Chalmers University of Technology
Email: hajar.kashfi@chalmers.se
Office:+46 (0)31 7725407
Mobile Phone: +46 (0)707222815
Web: http://www.cs.chalmers.se/~hajar.kashfi/
Visit: Room Simula B, House Svea, Campus Lindholmen
Postal adress:
Email: hajar.kashfi at chalmers.se
Phone: +46 31 772 5407
Office: Room Simula B, House Svea, Campus Lindholmen
Postal Address: Chalmers University of Technology, SE- 412 96 Gothenburg, Sweden
The current Ocean Template XSD is attached. This is an organically designed (i.e. not designed;-) schema that grew up with the requirements. Ocean has been asked to post this on openEHR.org as a freely available schema for .oet files, until the definitive one becomes available. There is no problem doing this, but I am interested to ascertain what differences there might be with the Zilics or other such schemas, and to ensure there is no confusion about this schema.
- thomas beale
(attachments)
CompositionTemplate.xsd (17 KB)
Hi,
The ZM understands .oet files with a slightly different format, so it is
only possible to use an template created by the Ocean's tools if you
adapt it ... The key differences are:
- ZM templates uses a different namespace:
xmlns="http://schemas.openehr.org/v1"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
This was done to avoid conflicts between the original draft
specification from openEHR an our model;
- All complex types' names are preceeded by "TEMPLATE_", so instead of
using <definition xsi:type="COMPOSITION">, please use <definition
xsi:type="TEMPLATE_COMPOSITION">
This was done because there is another complex type named
"COMPOSITION" in Composition.xsd;
All XSD's are in:
http://www.openehr.org/svn/ref_impl_java/SANDBOX/zilics-models/rm/src/main/resources/xsd/
An example of working template:
http://www.openehr.org/svn/ref_impl_java/SANDBOX/zilics-models/test/src/main/resources/xml/templates/Template1.oet
Cheers,
Humberto Silva Naves
Pariya Kashfi wrote: