DS - Link back to webpage/more information page

[GoogleCodeExporter]

Thinking about powering clients with the SOS, we should have an optional way to 
reference webpages in a station and/or sensor DescribeSensor response.

ie. a link back to http://www.ndbc.noaa.gov/station_page.php?station=45001

I think a text/html <documentation> tag might suffice with an IOOS defined 
arcrole.

<sml:documentation xlink:arcrole="webpageInformation">
  <sml:Document>
    <gml:description>Webpage for station 45001</gml:description>
    <sml:format>text/html</sml:format>
    <sml:onlineResource xlink:href="http://www.ndbc.noaa.gov/station_page.php?station=45001"/>
  </sml:Document>
</sml:documentation>

Thoughts?  OK to add to templates?

Original issue reported on code.google.com by wilcox.k...@gmail.com on 13 Nov 2012 at 8:22

[GoogleCodeExporter]

This would not be a difficult change to the PHP SOS code.  NDBC already has 
URLs for about 80% of the stations in its database.  Of course, these are all 
www.ndbc.noaa.gov URLs.  The only time consuming task might be verifying the 
URLs we do have.  But that could be done with software.  I like it.

Original comment by mike.gar...@gmail.com on 13 Nov 2012 at 9:48

[GoogleCodeExporter]

Sounds great. +1

Someone was already doing this in an older SOS implementation, but I can't 
remember who. I know b/c I borrowed the idea for the current NANOOS SOS a year 
ago; eg:
http://habu.apl.washington.edu/pyws/sos.py?service=SOS&version=1.0.0&request=Des
cribeSensor&procedure=urn:ioos:station:nanoos:ORCA_Hoodsport&outputFormat=text/x
ml;subtype=%22sensorML/1.0.1%22

Kyle is proposing that this be optional for now (and I agree with that), so 
existing Milestone 1.0 implementations can choose to ignore it till the next 
phase/release.

My comments/questions:
- I still haven't figured out what "xlink:arcrole" is and when it should be 
used instead of "xlink:role"?
- We can easily create a vocabulary entry for "webPage" under 
http://mmisw.org/ont/ioos/definition. Yes, I'm volunteering to add the term. I 
think "urn:ogc:def:role:webPage" exists, b/c I borrowed it from somewhere; 
Google gave me this 2009 email thread:
http://www.pmel.noaa.gov/maillists/tmap/ioos_wsde/msg00596.html 
Or we should we make up something more specific, say, "stationWebPage"?
- There may be more than one candidate URL for a station -- say, from NDBC, an 
RA, and the original provider. Does sml:documentation allow for >1 sml:Document 
children? 
- Ideally, gml:description should include text specifying who is the web page 
host (provider, RA, etc).

Original comment by emilioma...@gmail.com on 13 Nov 2012 at 11:50

[GoogleCodeExporter]

NDBC is already doing this in the DescribeSensor response for DART stations.  
See: 
http://sdf.ndbc.noaa.gov/sos/server.php?request=DescribeSensor&service=SOS&versi
on=1.0.0&outputformat=text/xml;subtype=%22sensorML/1.0.1%22&procedure=urn:ioos:s
tation:wmo:52402

<sml:documentation xlink:arcrole="urn:ogc:def:role:webPage">
  <sml:Document>
    <gml:description>Web page about the system described in this SensorML record</gml:description>
    <sml:format>text/html</sml:format>
    <sml:onlineResource xlink:href="http://www.ndbc.noaa.gov/station_page.php?station=52402"/>
  </sml:Document>
</sml:documentation>

We never added it for other types of stations.

Original comment by mike.gar...@gmail.com on 14 Nov 2012 at 12:30

[GoogleCodeExporter]

I think everyone's in agreement on this as long as it's optional. Can you 
(Kyle) add this to the DS templates and close?

Original comment by sh...@axiomalaska.com on 30 Dec 2012 at 9:25

[GoogleCodeExporter]

Going back to a couple of comments/questions I raised on Comment 2:

- Use of "xlink:arcrole" vs "xlink:role"
Mike Garcia found answers for this. See "role vs arcrole",
https://groups.google.com/d/topic/ioostech_dev/Wrjb8bb5cEY/discussion
xlink:arcrole looks like the appropriate attribute, but Mike also suggested 
that xlink:arcrole should be used in many cases where we're currently using 
xlink:role. This broader change sounds like its own, new issue.

- Use urn:ogc:def:role:webPage, or create a new entry managed by us on 
http://mmisw.org/ont/ioos/definition, as we have done for most, if not all, 
definitions? If we create our own, should it be more specific than "webPage"? 
Say, "stationWebPage" or "assetWebPage"?

- gml:description should include text specifying who is the web page host 
(provider, RA, NDBC, etc).

- There may be more than one candidate URL for a station -- say, from NDBC, an 
RA, and the original provider. Should we try to accommodate that possibility 
now, optionally? I've looked this up, and there's a generic way of handling 
both multiple station URL documents as well as other types of documentation:

<sml:documentation>
  <sml:DocumentList>
    <sml:member name="uff" xlink:arcrole="qualityControlDocument">
      <sml:Document>
        <gml:description>Handbook of Automated Data Quality Control Checks and Procedures, National Data Buoy Center, August 2009</gml:description>
        <sml:format>pdf</sml:format>
        <sml:onlineResource xlink:href="http://www.ndbc.noaa.gov/NDBCHandbookofAutomatedDataQualityControl2009.pdf"/>
      </sml:Document>
    </sml:member>
    <sml:member name="da" xlink:arcrole="urn:ogc:def:role:webPage">
      <sml:Document>
        <gml:description>Station web page from NDBC aggregator</gml:description>
        <sml:format>text/html</sml:format>
        <sml:onlineResource xlink:href="http://www.ndbc.noaa.gov/station_page.php?station=52402"/>
      </sml:Document>
    </sml:member>
    <sml:member name="urgh" xlink:arcrole="urn:ogc:def:role:webPage">
      <sml:Document>
        <gml:description>Station web page from nwmonitoring, the station operator</gml:description>
        <sml:format>text/html</sml:format>
        <sml:onlineResource xlink:href="http://www.nwmonitoring.org/station_page.php?station=52402"/>
      </sml:Document>            
    </sml:member>
  </sml:DocumentList>
</sml:documentation>

Original comment by emilioma...@gmail.com on 31 Dec 2012 at 8:20

[GoogleCodeExporter]

+1 arcrole

+1 Use urn:ogc:def:role:webPage for webpages.  We don't need to create an MMI 
entry for something this.

+1 Create a MMI entry for "qualityControlDocument"

I'll update the templates and create a new issue for creating the MMI entry.

Original comment by wilcox.k...@gmail.com on 3 Jan 2013 at 3:41

• Changed state: Fixed