> -----Original Message-----
> From: Valentina Sagris [mailto:[email protected]]
> Sent: 09 September 2014 19:39
> To: [email protected]
> Subject: [Geoserver-users] App-schema extension: fail to map xlink
> namespace
>
> Hi,
> have defined xlink in mapping file and in the FT schema
> <Namespace>
> <prefix>xlink</prefix>
> <uri>http://www.w3.org/1999/xlink </uri>
> </Namespace>
I wonder if it is the extra space after xlink in your uri element?

This does work fine in our service, you can see many examples of xlink:href in 
a request like: 
http://ogc.bgs.ac.uk/digmap625k_gsml32_gs/wfs?service=WFS&version=2.0.0&request=GetFeature&typenames=gsml:MappedFeature&count=10&;

Our mapping file  for a typical example for us has:
-----
<Namespace><prefix>xlink</prefix><uri>http://www.w3.org/1999/xlink</uri></Namespace>
-----
and
-----
<AttributeMapping>                          
<targetAttribute>gsml:observationMethod/swe:Category/swe:extension/swe:Category/swe:codeSpace</targetAttribute>
<ClientProperty>
<name>xlink:href</name>
<value>'http://resource.geosciml.org/classifierscheme/cgi/201202/valuequalifier'</value>
</ClientProperty>
</AttributeMapping>

-----

Marcus Sen
British Geological Survey
Keyworth
Nottingham
NG12 5GG

Web: http://www.bgs.ac.uk

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.
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Reply via email to