new entries

[amilan17]

Hello - We are planning on using LinkPropertyLookupTable terms for our ISO metadata in NOAA and request that you add the following:

HTTPS URL: https://tools.ietf.org/html/rfc2818

FTP URL: https://tools.ietf.org/html/rfc959

OPeNDAP:Hyrax
URL: http://docs.opendap.org/index.php/Hyrax

Thanks, Anna

[tomkralidis]

@amilan17 for HTTPS, we already have a WWW:LINK entry which can cover both HTTP and HTTPS. Does this work for you?

[amilan17]

Hi @tomkralidis - According to the current list, WWW:LINK is defined by the XLink standard (http://www.w3.org/TR/xlink/) and this doesn't match the "secure HTTP connections over the Internet" definition for HTTPS. Furthermore, I think we will have a use case where we need to clarify the type of link...

[rsignell-usgs]

So @amilan17, the idea is that...

OPeNDAP:Hyrax should be used for endpoints like this: https://data.nodc.noaa.gov/opendap/ghrsst/L4/GLOB/DMI/DMI_OI/

while

UNIDATA:THREDDS should be used for endpoints like this: https://data.nodc.noaa.gov/thredds/catalog/ghrsst/L4/GLOB/DMI/DMI_OI/

Is that right?

[amilan17]

I believe so.

Anna ~~Metadata Adds Meaning~~ Anna.Milan@noaa.gov, 303-497-5099 NOAA National Centers for Environmental Information (formerly NOAA’s National Geophysical Data Center) http://www.ngdc.noaa.gov/metadata/emma ~~~~~~~~

On Fri, Sep 23, 2016 at 8:02 AM, Rich Signell notifications@github.com wrote:

So @amilan17 https://github.com/amilan17, the idea is that...

OPeNDAP:Hyrax should be used for endpoints like this: https://data.nodc.noaa.gov/opendap/ghrsst/L4/GLOB/DMI/DMI_OI/

while

UNIDATA:THREDDS should be used for endpoints like this: https://data.nodc.noaa.gov/thredds/catalog/ghrsst/L4/GLOB/DMI/DMI_OI/

Is that right?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/OSGeo/Cat-Interop/issues/28#issuecomment-249201529, or mute the thread https://github.com/notifications/unsubscribe-auth/AE7e4rPZqcjOCLJrG2fhwTXhnhHMq5dPks5qs9wTgaJpZM4KBt6o .

[tomkralidis]

@amilan17 implemented in master. What's the difference between OPeNDAP:OPeNDAP and OPeNDAP:Hyrax, then?

[BobSimons]

I don't know the intent of the people who created those entries, but I would interpret them as: OPeNDAP:OPeNDAP - applicable to any service that follows the DAP specification. OPeNDAP:Hyrax - specifically to identify a Hyrax server (the DAP server made by the OPeNDAP organization) (as opposed to other DAP servers like THREDDS, GRADS, ERDDAP, PyDAP, ...).

On Mon, Sep 26, 2016 at 6:51 PM, Tom Kralidis notifications@github.com wrote:

@amilan17 https://github.com/amilan17 implemented in master. What's the difference between OPeNDAP:OPeNDAP and OPeNDAP:Hyrax, then?

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/OSGeo/Cat-Interop/issues/28#issuecomment-249745851, or mute the thread https://github.com/notifications/unsubscribe-auth/ABarOAQj1tyxVjP3Ev8vBa8pQ43sgR-kks5quHalgaJpZM4KBt6o .

Sincerely,

Bob Simons IT Specialist Environmental Research Division NOAA Southwest Fisheries Science Center 99 Pacific St., Suite 255A (New!) Monterey, CA 93940 (New!) Phone: (831)333-9878 (New!) Fax: (831)648-8440 Email: bob.simons@noaa.gov

The contents of this message are mine personally and do not necessarily reflect any position of the Government or the National Oceanic and Atmospheric Administration. <>< <>< <>< <>< <>< <>< <>< <>< <><

[tomkralidis]

@BobSimons thanks for the clarification. If this means that a Hyrax server is just an OPeNDAP instance then I would propose we remove. Thoughts?

[BobSimons]

No. Please don't remove it.

Lots of servers use the DAP protocol: Hyrax, THREDDS, ERDDAP, PyDAP, GRADS, ... But each one implements a different subset of the DAP specification. And each one adds other features that aren't part of the DAP specification (e.g., THREDDS adds the THREDDS catalog system, ERDDAP adds Make-A-Graph). So each server is has a common core (DAP) and parts that are different.

Names like OPeNDAP:HYRAX are great because they say both:

• This is a DAP server (so if I have a DAP client library, I can get data from this server).
• Specifically, this is a HYRAX server. So if I have a choice, and if I like some specific extra feature offered by HYRAX, I might prefer this server.

"OPeNDAP" alone, or "HYRAX" alone doesn't convey that information.

On Tue, Sep 27, 2016 at 8:27 AM, Tom Kralidis notifications@github.com wrote:

@BobSimons https://github.com/BobSimons thanks for the clarification. If this means that a Hyrax server is just an OPeNDAP instance then I would propose we remove. Thoughts?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/OSGeo/Cat-Interop/issues/28#issuecomment-249900060, or mute the thread https://github.com/notifications/unsubscribe-auth/ABarOFP6aVzHOwc81OgJ4FHrv204F0rcks5quTXtgaJpZM4KBt6o .

Sincerely,

Bob Simons IT Specialist Environmental Research Division NOAA Southwest Fisheries Science Center 99 Pacific St., Suite 255A (New!) Monterey, CA 93940 (New!) Phone: (831)333-9878 (New!) Fax: (831)648-8440 Email: bob.simons@noaa.gov

The contents of this message are mine personally and do not necessarily reflect any position of the Government or the National Oceanic and Atmospheric Administration. <>< <>< <>< <>< <>< <>< <>< <>< <><

[tomkralidis]

@BobSimons thanks for the helpful clarification. OK.