[auscope-geosciml] RE : MappedFeature specification has inline elementcontent

Boisvert, Eric Eric.Boisvert at RNCan-NRCan.gc.ca
Thu Sep 9 05:06:51 EDT 2010

I think that <specification xlink:href="#xxx"/> counts as "inline" in this case.
having the same gml:id more than once in a document is not schema valid anyway.


De: auscope-geosciml-bounces at lists.arcs.org.au de la part de Sen, Marcus A
Date: jeu. 2010-09-09 03:38
À: auscope-geosciml at lists.arcs.org.au
Objet : [auscope-geosciml] MappedFeature specification has inline elementcontent

I've just noticed the following rule at https://www.seegrid.csiro.au/twiki/bin/view/CGIModel/GeoSciML3SchematronRules:

RULE: MappedFeature.specification is has inline element content.

In Testbed 3 one of the bits of functionality that Eric's GIN mediator system did and that we got Snowflake software to implement was to be able to return MappedFeatures where the first occurrence of a MappedFeature with a specification of a particular GeologicUnit was inline but subsequent occurrences of MappedFeatures with a specification of the same GeologicUnit had this by internal reference to the first inline reference. We've been looking at using the WFS2 additionalObjects container to hold things like GeologicUnits which might be pointed to by multiple MappedFeatures.

Was it decided to do things differently in Rome?


This message (and any attachments) is for the recipient only. NERC
is subject to the Freedom of Information Act 2000 and the contents
of this email and any reply you make may be disclosed by NERC unless
it is exempt from release under the Act. Any material supplied to
NERC may be stored in an electronic records management system.
auscope-geosciml mailing list
auscope-geosciml at lists.arcs.org.au

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/ms-tnef
Size: 4814 bytes
Desc: not available
URL: <http://lists.opengeospatial.org/pipermail/geosciml/attachments/20100909/9711a1d2/attachment.bin>

More information about the GeoSciML mailing list