[tdwg-tapir] Is the current schema valid?
Hi All,
I have just noticed that the schema at:
http://rs.tdwg.org/tapir/1.0/schema/tapir.xsd
isn't valid according to Oxygen 8.0.
E cos-all-limited.1.2: An 'all' model group must appear in a particle with '{'min occurs'}' = '{'max occurs'}' = 1, and that particle must be part of a pair which constitutes the '{'content type'}' of a complex type definition.
Am I missing something - I appreciate that there are a stack of emails I need to work back through.
All the best,
Roger
____________________________________________________________
Roger Hyam roger@tdwg.org ____________________________________________________________
Biodiversity Information Standards: http://www.tdwg.org/
"Working To Make Biodiversity Data Global" ____________________________________________________________
TDWG Standards Architecture: http://wiki.tdwg.org/twiki/bin/view/TAG LSID RDF Vocabularies: http://wiki.tdwg.org/twiki/bin/view/TAG/ LsidVocs ____________________________________________________________
Hi Roger,
Before publishing new versions of the TAPIR schema I always use the official w3c validation service:
http://www.w3.org/2001/03/webdata/xsv
Since it's not detecting any problems with the current schema, one of the two validators has a problem.
There's only one xsd:all element that I recently introduced in the schema to allow TAPIR environment variables to be declared in any order in capabilities responses. This xsd:all is part of an xsd:group particle with minOccurs=maxOccurs=1, but this particle is not "part of a pair of a complex type definition".
We could probably replace "all" by a "sequence" to avoid this problem and force a specific order, although this will probably affect one or more data provider implementations. Or maybe just leave things as they are if we can confirm that the Oxygen validator is wrong.
I'll appreciate any thoughts or suggestions...
Best Regards, -- Renato
On 27 Jul 2007 at 11:12, Roger Hyam wrote:
Hi All,
I have just noticed that the schema at:
http://rs.tdwg.org/tapir/1.0/schema/tapir.xsd
isn't valid according to Oxygen 8.0.
E cos-all-limited.1.2: An 'all' model group must appear in a particle with '{'min occurs'}' = '{'max occurs'}' = 1, and that particle must be part of a pair which constitutes the '{'content type'}' of a complex type definition.
Am I missing something - I appreciate that there are a stack of emails I need to work back through.
All the best,
Roger
Renato, Afaik oxygen is using xerces for validation - which is a very good parser/validator. Not sure if the w3c xsv validator is more trustable, but I feel very uncomfortable if xerces doesnt validate the schema.
Markus
Am 27.07.2007 15:07 Uhr schrieb "Renato De Giovanni" unter renato@cria.org.br:
Hi Roger,
Before publishing new versions of the TAPIR schema I always use the official w3c validation service:
http://www.w3.org/2001/03/webdata/xsv
Since it's not detecting any problems with the current schema, one of the two validators has a problem.
There's only one xsd:all element that I recently introduced in the schema to allow TAPIR environment variables to be declared in any order in capabilities responses. This xsd:all is part of an xsd:group particle with minOccurs=maxOccurs=1, but this particle is not "part of a pair of a complex type definition".
We could probably replace "all" by a "sequence" to avoid this problem and force a specific order, although this will probably affect one or more data provider implementations. Or maybe just leave things as they are if we can confirm that the Oxygen validator is wrong.
I'll appreciate any thoughts or suggestions...
Best Regards,
Renato
On 27 Jul 2007 at 11:12, Roger Hyam wrote:
Hi All,
I have just noticed that the schema at:
http://rs.tdwg.org/tapir/1.0/schema/tapir.xsd
isn't valid according to Oxygen 8.0.
E cos-all-limited.1.2: An 'all' model group must appear in a particle with '{'min occurs'}' = '{'max occurs'}' = 1, and that particle must be part of a pair which constitutes the '{'content type'}' of a complex type definition.
Am I missing something - I appreciate that there are a stack of emails I need to work back through.
All the best,
Roger
tdwg-tapir mailing list tdwg-tapir@lists.tdwg.org http://lists.tdwg.org/mailman/listinfo/tdwg-tapir
participants (3)
-
Döring, Markus -
Renato De Giovanni -
Roger Hyam