[Esip-discovery] ESIP Discovery Cluster Telecon, Tuesday, Aug. 9 @ 4:00 ET / 3:00 CT / 2:00 MT / 1:00 PT

[Hua, Hook (388C)]

Hi James,

For Approach #5, we never really discussed what the exact attribute name would be. We only floated the methodology of using a new namespaced attribute. 

Eric's posting here has a good pros/cons:
http://wiki.esipfed.org/index.php/Talk:Discovery_Change_Proposal-2

The difficulty is in how to achieve compliance with RFC 4287 Atom while supporting both "general" (e.g. data link) and "specific" (e.g. OPeNDAP 3.3) relations types in the links.
http://tools.ietf.org/html/rfc4287#section-4.2.7
Nothing for "specific" fits with in the current RFC spec. Thus the idea for approach #3 using fragments in URIs was also discussed.

Approach #1 would work with on general relation type if we treat it like a taxonomy of more specific subclasses of relations. But then we would have to maintain and reference an external taxonomy or ontology. If we are heading towards semantics anyways, then it may not be such a bad approach...

Also, is anyone familiar enough with OGC OpenSearch on if and how it may be dealing with this type of issue. Perhaps there should be some convergence in the future.

--Hook


________________________________________
From: Eric Rozell [rozele at rpi.edu]
Sent: Tuesday, August 09, 2011 6:47 PM
To: Gallagher James
Cc: Hua, Hook (388C); esip-discovery at lists.esipfed.org
Subject: Re: [Esip-discovery] ESIP Discovery Cluster Telecon, Tuesday, Aug. 9 @ 4:00 ET / 3:00 CT / 2:00 MT / 1:00 PT

James,

We had discussed that adding a new attribute to Atom would cause the W3C feed validator to crash, unless that attribute used a namespace.

I think the proposal is to use the ESIP namespace for new attributes that could be used in the discovery protocol. Particularly, given the "two-level" aspect of the discovery protocol, the rel attribute would be used for "generic" information (e.g., http://esipfed.org/ns/discovery/1.1/data#) and a new attribute would be coined for web service "specific" information (e.g., http://xml.opendap.org/ns/DAP/3.3#).  Both the namespace and the actual name of the attribute are up for debate, but an example might be:

<link rel="http://esipfed.org/ns/discovery/1.1/data#" xmlns:esip="http://esipfed.org/ns/discovery/1.1/" esip:spec="http://xml.opendap.org/ns/DAP/3.3#" href="http://disc2.nascom.nasa.gov/opendap/TRMM_3Hourly_3B42/2011/001/3B42.110101.12.6A.HDF.Z" />

I've added some of this information to the Talk page for DCP-2.

-Eric



On Aug 9, 2011, at 6:15 PM, Gallagher James wrote:

Hook:

Regarding the proposal by Brian (an alternative to DCP-2), do you have any examples of what that third attribute would be?

My two cents (I apologize for missing the meeting) on making the rel attribute a space-separated set of values (I assume that's what is meant by 'Use space-delimitation in "rel" URI') is to not do that. I think it's best to reserve XML attributes for single values.

James

On Aug 9, 2011, at 3:19 PM, Hua, Hook (388C) wrote:

Notes from today's telecon posted:
http://wiki.esipfed.org/index.php/Discovery_Telecon_2011-08-09

We also identified 4 additional approaches to DCP-2. We said that we will continue discussions online. The 5 approaches are posted in the DCP's discussion tab:
http://wiki.esipfed.org/index.php/Talk:Discovery_Change_Proposal-2

--Hook


________________________________________
From: esip-discovery-bounces at lists.esipfed.org<mailto:esip-discovery-bounces at lists.esipfed.org> [esip-discovery-bounces at lists.esipfed.org] On Behalf Of Lynnes, Christopher S. (GSFC-6102) [christopher.s.lynnes at nasa.gov]
Sent: Monday, August 08, 2011 10:38 AM
To: esip-discovery at lists.esipfed.org<mailto:esip-discovery at lists.esipfed.org>
Subject: [Esip-discovery] ESIP Discovery Cluster Telecon, Tuesday, Aug. 9 @ 4:00 ET / 3:00 CT / 2:00 MT / 1:00 PT

The ESIP Discovery Cluster telecon will be held tomorrow, Tuesday, Aug. 9 at 4:00 ET / 3:00 CT / 2:00 MT / 1:00 PT.

The Agenda is:

1)  Ruth Duerr on a proposal for the Discovery Cluster to write a white paper for the NSF EarthCube program ( http://www.nsf.gov/geo/earthcube/index.jsp )
2)  (Tentative) Brian Wilson on how to handle alternate service/data links in granule-level Discovery responses

Telecon instructions:
      • Call-in toll-free number (US/Canada): 1-877-669-3239
      • Attendee access code: 231 407 50
      • To start the online portion of the Personal Conference meeting , go to https://esipfed.webex.com/esipfed/j.php?ED=9910758&UID=485702463&PW=NM2NiZjRlNmNk&RT=MiM3
--
Dr. Christopher Lynnes     NASA/GSFC, Code 610.2    phone: 301-614-5185


_______________________________________________
Esip-discovery mailing list
Esip-discovery at lists.esipfed.org<mailto:Esip-discovery at lists.esipfed.org>
http://www.lists.esipfed.org/mailman/listinfo/esip-discovery
_______________________________________________
Esip-discovery mailing list
Esip-discovery at lists.esipfed.org<mailto:Esip-discovery at lists.esipfed.org>
http://www.lists.esipfed.org/mailman/listinfo/esip-discovery

--
James Gallagher
jgallagher at opendap.org<http://opendap.org>
406.723.8663

_______________________________________________
Esip-discovery mailing list
Esip-discovery at lists.esipfed.org<mailto:Esip-discovery at lists.esipfed.org>
http://www.lists.esipfed.org/mailman/listinfo/esip-discovery