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

[Bruce.Simons at dpi.vic.gov.au]

<specification xlink:href="#xxx"/> counts as "inline" - correct.

Cheers
Bruce 

Ph: +61-3-9658 4502
Fax: +61-3-9658 4555 
Mobile: +61 429 177155



"Boisvert, Eric" <Eric.Boisvert at RNCan-NRCan.gc.ca> 
Sent by: auscope-geosciml-bounces at lists.arcs.org.au
09/09/2010 07:06 PM
Please respond to
auscope-geosciml at lists.arcs.org.au


To
<auscope-geosciml at lists.arcs.org.au>
cc

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






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.
 
Eric

________________________________

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?

Marcus
 


--
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
http://lists.arcs.org.au/cgi-bin/mailman/listinfo/auscope-geosciml


_______________________________________________
auscope-geosciml mailing list
auscope-geosciml at lists.arcs.org.au
http://lists.arcs.org.au/cgi-bin/mailman/listinfo/auscope-geosciml


Notice:
This email and any attachments may contain information that is personal, 
confidential, legally privileged and/or copyright.No part of it should be reproduced, 
adapted or communicated without the prior written consent of the copyright owner. 

It is the responsibility of the recipient to check for and remove viruses.
If you have received this email in error, please notify the sender by return email, delete 
it from your system and destroy any copies. You are not authorised to use, communicate or rely on the information 
contained in this email.

Please consider the environment before printing this email.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opengeospatial.org/pipermail/geosciml/attachments/20100910/6c2b9953/attachment.htm>