[Moims-dai] Notes on meeting with Vint Cerf

Tue Apr 26 05:27:38 UTC 2016

Hi,

I’m very much in support of developing standards for interoperable archives.  But as much as I am in support of that, I don’t really know what others mean by that or what they are looking for.  I think I need to see some user requirements/storyboards for what interoperability would look like.   

I think a lot of technical interoperability issues have been solved.  Some others still need to be, but people are working on them.  I think the biggest interoperability issues are the financial and political layers from Vint’s IIPC talk.

There are lots of standards at the lower levels that are available at lower layers and certain profiles of these are used in certain domains for interoperability there.  But I think technical standards are very reliant on markets and marketing of solutions and on technological advancements that allow new technical standards to overtake the old ones.

I think that is why the OAIS and auditing standards are so important.  They help manage those changes.

Wishing you prosperity and peace,

-JOhn

From: moims-dai-bounces at mailman.ccsds.org [mailto:moims-dai-bounces at mailman.ccsds.org] On Behalf Of Mike Kearney
Sent: Friday, April 22, 2016 9:50 AM
To: 'MOIMS-Data Archive Ingestion' <moims-dai at mailman.ccsds.org>
Subject: RE: [Moims-dai] Notes on meeting with Vint Cerf

*  I don’t think that the intention was to say that ALL repositories want to be interoperable.  

Absolutely right.  If a repository is not interoperable, it should be because that repository chooses to be non-interoperable.  Not because there is no choice to be interoperable because of industry divergence and broad incompatibilities.  

In my opinion the business case for interoperability can be entirely made by the cross-discipline research scenario where future researchers need to access multiple discipline databases, multiple mission databases, etc. in order to get synergized results to make new discoveries.  But of course there are also other business cases for the standardization that leads to interoperability, such as commercial products, cost reduction, “many eyes on the problem”, etc.  All of the benefits of standardization, the greatest of which is interoperability.  

Totally understand that there are many diverse and obscure databases and archives that will never be able to line up with an interoperability standard.  But if we fail to produce the standard, then we (the standards community) have produced the problem, not them.  

*  4. We need to assert our original goal of developing a standard and an audit process to evaluate digital repositories against that standard as to their ability to  operate a digital repository that can accept digital data, preserve it, and provide it in a usable form to a user when requested.  If we cannot find or develop that market, we certainly cannot develop Vint Cerf's under developed concepts.  

Absolutely.  That doesn’t contradict the need to set interoperable standards as the next goal, does it?  To better develop those under-developed concepts?  

   -=- Mike

Mike Kearney

Huntsville, Alabama, USA

From: moims-dai-bounces at mailman.ccsds.org <mailto:moims-dai-bounces at mailman.ccsds.org>  [mailto:moims-dai-bounces at mailman.ccsds.org] On Behalf Of David Giaretta
Sent: Friday, April 22, 2016 6:36 AM
To: 'MOIMS-Data Archive Ingestion' <moims-dai at mailman.ccsds.org <mailto:moims-dai at mailman.ccsds.org> >
Subject: RE: [Moims-dai] Notes on meeting with Vint Cerf

Hi Bruce

I don’t think that the intention was to say that ALL repositories want to be interoperable.  

The way I interpreted it was that in order to increase use of the standards and also to add value to what is being preserved by increasing its usefulness – interoperability is one important way of doing that. I think we should take that on board and try to show how DAI/RAC standards can be used both for preservation and also for adding value. 

Regards

..David 

From: moims-dai-bounces at mailman.ccsds.org <mailto:moims-dai-bounces at mailman.ccsds.org>  [mailto:moims-dai-bounces at mailman.ccsds.org] On Behalf Of bambacher at verizon.net <mailto:bambacher at verizon.net> 
Sent: 20 April 2016 20:38
To: moims-dai at mailman.ccsds.org <mailto:moims-dai at mailman.ccsds.org> 
Subject: Re: [Moims-dai] Notes on meeting with Vint Cerf

If I may make an observation:

1. All of this presumes all digital repositories want to be interoperable, which they may not.

2. Vint Cerf appears to seriously minimize the number of spplications and software used to create digital records requiring preservation.  NARA's scope of the problem study found 15,000+ applications and software routines in use in the federal government.  It is hard enough to crosswalk between geospatial applications let alone cross walking between geospatial applications and office applications and CAD-CAM applications.  I could be over reaching his intentions but even if he only called for inter-operability within a specific discipline, designated community, or data type that is a large problem.

3. Recall the approach of a few test audit sites that ingested data only in a single pre-approved SPSS format, essentially frozen in 30+ years old structure.  They dictated to their Designated Community.  They would not fit Mr. Cerf's generic protocol for sharing data.

4. We need to assert our original goal of developing a standard and an audit process to evaluate digital repositories against that standard as to their ability to  operate a digital repository that can accept digital data, preserve it, and provide it in a usable form to a user when requested.  If we cannot find or develop that market, we certainly cannot develop Vint Cerf's under developed concepts.  

5. We should obviously respond, thank him, state our position and how it fits his challenge.  But, unless he can provide funding and/or FTE to pursue the issue, it is beyond our scope of effort.

On 04/20/16, David Giaretta<david at giaretta.org <mailto:david at giaretta.org> > wrote:

Any objections/updates/additions/corrections?

Regards

..David

  _____  

_______________________________________________
Moims-dai mailing list
Moims-dai at mailman.ccsds.org <mailto:Moims-dai at mailman.ccsds.org> 
http://mailman.ccsds.org/mailman/listinfo/moims-dai

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/moims-dai/attachments/20160426/35abfb38/attachment.html>