1 / 8

Summary of Working Session for Federated Technologies: OpenSearch , Data Casting, Service Casting

Summary of Working Session for Federated Technologies: OpenSearch , Data Casting, Service Casting. 9 th ESDSWG Technology Infusion Working Group Thursday, October 21, 2010 New Orleans, Louisiana. Objectives. Refresh on Casting/Feed/Discovery Casting is about metadata micro-formats.

munin
Download Presentation

Summary of Working Session for Federated Technologies: OpenSearch , Data Casting, Service Casting

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Summary of Working Session forFederated Technologies:OpenSearch, Data Casting, Service Casting 9th ESDSWG Technology Infusion Working Group Thursday, October 21, 2010 New Orleans, Louisiana

  2. Objectives • Refresh on Casting/Feed/Discovery • Casting is about metadata micro-formats. • Show what the technologies are and go into the specifications with examples. • Federated technologies "under the hood”. • Assess the various casting “standards”. • E.g. can we make a recommendation for casting response format across OpenSearch, Data Casting, and Service Casting. • Resolve interoperable issues across the different casting “standards” • Solicit more involvement ESDSWG Meeting 2010

  3. Session Summary • Gave short introduction/refreshers on technologies • OpenSearch, Chris Lynnes (GSFC) • Data Casting collection, Ruth Duer (NSIDC) • Data Casting granule, Sean McClees (JPL) • Service Casting, Brian Wilson (JPL) • Defined Use Cases for mashup of federatedness of opensearch, data casting, & service casting. • E.g. Provide collection-level Data Casting contains links to granule-level OpenSearch • Also determine issues to be resolved for use cases • As a group, resolved some standardization issues, technical issues, overlaps in specs, standards, work out interoperability. • E.g. we agreed on a common casting response format “standard” with a set of defined tags and link relationship types. ESDSWG Meeting 2010

  4. Detailed Results

  5. Working Session: Defined Use Cases for Mashup • Federation of Casting? Top-level aggregators • Federated search fed by federated data casting aggregation • Need rel links for casting type • Collection-level Data Casting contains links to Granule-level OpenSearch • OpenSearch and Service Cast mashup. • Referencing service casting feeds in search of data • How would link up OpenSearch with Data Casting? • Ruth: need general “Open Science” services and Aggregator ESDSWG Meeting 2010

  6. Working Session: Issues Resolved • Handling domain-specific tags • Put at top-level <entry> with namespace • Put into container like <content> or <channel> • Atom spec allows for clients to ignore custom tags • Example flags • dayNightFlag • projection • Settled on GeoRSS and ISO 8601 at <entry> level • E.g. <geo:box>-180.0, -90.0, 180.0, 90.0</geo:box> • <time:start>2005-01-01T00:00:00Z</time:start> • <time:end>2005-01-01T03:00:00Z</time:end> • OpenSearch request custom parameters • Can define domain-specific Schema XSD to reference. XML instance in <entry>. • But may want to have custom allowed value restrictions. Could subclass xsd and define additional restrictions. • Can put hierarchy in atom’s <category> using string “domain/subdomain/subsubdomain/”. ESDSWG Meeting 2010

  7. Working Session: Issues Resolved • Consolidated common casting response format “standard” • Put custom tags (with namespace) at top-level of <entry> • Want to keep namespaces generic for all artifacts with space-time. Let’s look for other nampespaces other than ESIP nampespace. For now, decided to maintain esipfed.org • http://infodiscovery.orgis available • Decided to settle on (for now) on rellinks based on http://esipfed.org/ns/cast/1.1/<cast_type># where cast_type is of value: • data: Data Casting Granules. OpenSearch Granules response • collection: Data Casting Collection. Not for OpenSearch Collection response which uses OSDD instead. • service: Service Casting • event: natural phenomenon • feed: feed of various feeds • browse: browse image • documentation: arbitrary documentation • metadata: data and collection metadata • rellinks shall have types. Decided to keep type values open. • Implication: OpenSearch response and DataCasting converging ESDSWG Meeting 2010

  8. Next Steps… • Need to continue discussion on a common standard for OpenSearch Response, Data Casting, and Service Casting • Create general “discovery” or “esipdiscovery” mailing list on ESIP • Should we form a new “discovery” ESIP cluster? • Ruth prefers to relabel the “fedsearch” cluster and mailing list to “discovery”. ESDSWG Meeting 2010

More Related