add contact information

[tbonfort]

Reporter: tomkralidis Date: 2004/10/10 - 23:34

In WCS Capabilities, between service level <keywords> and <fees>.  Here is the
structure:

<responsibleParty>
 <individualName>[ows_contactinfo_name]</individualName>
 <organisationName>[ows_contactinfo_org]</organisationName>
 <positionName>[ows_contactinfo_pos]</positionName>
 <contactInfo>
  <phone>
   <voice>[ows_contactinfo_tel]</voice>
   <facsimile>[ows_contactinfo_fax]</facsimile>
  </phone>
  <address>
   <deliveryPoint>[ows_contactinfo_address]</deliveryPoint>
   <city>[ows_contactinfo_city]</city>
   <administrativeArea>[ows_contactinfo_stateprov]</administrativeArea>
   <postalCode>[ows_contactinfo_postcode]</postalCode>
   <country>[ows_contactinfo_country]</country>
   <electronicMailAddress>[ows_contactinfo_email]</electronicMailAddress>
  </address>
  <onlineResource xlink:type="simple" xlink:href="[ows_contactinfo_url]"/>
 </contactInfo>
</responsibleParty>

[tbonfort]

Author: tomkralidis Date: 2004/10/10 - 23:42

The above [ows_*] directives are just suggestions, as there are a few ways to
tackle this:

- leverage the existing wms_contactinfo_* config values, as "ows_contactinfo_*"
- make new wcs_responsibleparty_* config values

The bottom line is that, while this is a relatively easy fix in the near term,
WCS' output content model is different that WMS'.  Same type of info, just
structured (and named) differently.

Keep in mind that this'll change again as OGC specs move towards the "OGC Common
Implementation" Specification, where again, same type of info, just structured
(and named) differently.

Hence another vote from myself for an abstract model at the MapServer level of
how these things are named and defined.

[tbonfort]

Author: tomkralidis Date: 2004/10/28 - 00:00

Guys,

Any way we can slip this one into 4.4.0?  Seeing that this will be the first
official release with OGC:WCS.

[tbonfort]

Author: sdlime Date: 2004/10/28 - 00:46

Yes, there were a couple of outstanding WCS ones that will make it. Ain't hard 
just takes time...

Steve

[tbonfort]

Author: tomkralidis Date: 2004/11/17 - 19:40

Setting to 4.4 release after Steve's confirmation in comment #3

[tbonfort]

Author: sdlime Date: 2004/11/28 - 23:55

Fixing now. I'm trying to support both a WCS specific method (i.e.
wcs_responsibleparty_name) and the WMS method (i.e. wms_contactperson). Note
that I don't see support for *_contactinfo_* metadata anyplace.

Steve

[tbonfort]

Author: sdlime Date: 2004/11/29 - 05:20

Fixed although only lightly tested. Both the wcs_responsibleparty_* metadata and
the WMS contact metadata are supported (although you can't mix and match). If
both are present the WCS specific encoding takes precedence. Note that WMS did
not have the equivalent of onlineResource so wcs_responsibleparty_onlineresource
is supported regardless. Also note that WCS getCapabilities.xsd schema spells
"organization" as "organisation". MapServer expects
wcs_responsibleparty_organizationname as metadata but produces XML that
validates against that schema.

J.F. if you have time and could verify...

Steve

[tbonfort]

Author: tomkralidis Date: 2004/11/29 - 06:10

comments:

1./

typo in:

<organisationName>Environment Canada</oranisationName>

Closing element should be "organisationName" to match opening element (line 374).

2./

typo when mapows.c looks up facsimile in both WCS and WMS metadata (lines 394
and 422) (should be facsimile, not facimile)

3./

for onlineResource, use the new "ows_service_onlineresource" (line 451) when a
WCS equivalent is not found.

This should do it -- let me know when I can retest.

[tbonfort]

Author: sdlime Date: 2004/11/29 - 15:42

Why can't they just use 'fax'... Fixed 'em.

Steve

[tbonfort]

Author: tomkralidis Date: 2004/12/01 - 05:56

Fixed.