[Moims-dai] RE: Possible scope reduction

Fri Sep 18 11:19:34 UTC 2015

I cannot do Thursday 24th - will be at RDA.

..David 

-----Original Message-----
From: Boucon Daniele [mailto:Daniele.Boucon at cnes.fr] 
Sent: 18 September 2015 11:25
To: Mike Martin <tahoe_mike at sbcglobal.net>
Cc: John Garrett <garrett at his.com>; Giaretta, David (STFC,RAL,RALSP) <david.giaretta at stfc.ac.uk>; Sawyer at acm.org; rdowns at ciesin.columbia.edu; Conway, Esther (STFC,RAL,RALSP) <esther.conway at stfc.ac.uk>; moims-dai at mailman.ccsds.org; stephane.reecht at bnf.fr
Subject: RE: Possible scope reduction

Hi Mike and all,

As only John and myself responded to move the today ILF telecon, I suggest that we keep a short slot, and we can plan another one in a short delay.

Here are my comments on Mike's proposal: 

1. I find that the mapping you propose between the life cycle activity and the topics interesting.

2. I find your point of view in the Info life cycles stage interesting. If we adopt this, then we'll have to explain the "handover" part (when the project does not exist any more).

3. concerning the content of the table itself:

Gathering the lines are ok, considering the fact that they will be expanded in sub bullets.
I'm not convinced that we have to cut the exploitation part.
I'm in favour of keeping the "adding value" and "discoverability", as this is what is a great interest for the users.

The lines from David's table-topicsand subtopicsDB- that I have not found in Mike's table are the following:

Line 5: Data	Semantics of the data elements	repInfo?	Needed to support interpretation and interoperability
Line 6: Data	Context documentation 	Context	Ex: description of mission, instrument, .
Line 7: Data	Quality specifications	?? DI ??	Future confidence in data. Definition of quality parameters. Ex: QA4EO .  => related to quality parameters, could ne enlarged in Mike's proposal
Line 9: Data	Inventory of data produced/expected		What level of granularity is needed? List of info + relationships among all the info (network)
Line 11: Representation Information	Applicable standards	RepInfo	Complex topic, maybe too big for general document
Line 12: Representation Information	Software dependencies	RepInfo	Minimize as archives don't have resources to maintain software
Line 13: Representation Information	Data dictionaries and other semantics	RepInfo	Need clean mechanism to transfer to archive, support interoperability
Line 14: Representation Information	Format definitions and formal descriptions	RepInfo	Needed to provide access to data.
Line 15: Representation Information	Information Model 	RepInfo	Information Model includes relationships between classes - important for automated production, validation, sw development
Line 17: Descriptive Information	Outline of background concepts needed to understand the project	Descriptive Info	Needed for future use of the data.
Line 23: (Adding) value	Related data which may in the future be combined with this data		This may be too broad.  
Line 24; (Adding) value	Other software which may be used on the data		Tutorials are very valuable for future access to the data.
Line 25: (Adding) value	Interfaces that are applicable to the data e.g.  images, tables.		I don't understand this issue.
Line 26: (Adding) value	Potential value of the data and likely business case for sustainability		Archive Support Plan 
Line 27: Proposal	Record of origins of the project e.g. in a CRIS system	Context	Descriptive information, record of commitments, evaluation of project success
Line 29: Provenance	Documentation about the hardware and software used to create the data, including a history of the changes in these over time 	Provenance	How do we capture this?
Line 34: Provenance	Record of any special hardware needed	Provenance	Submission Agreement?
Line 37: Authenticity	Who was responsible for each stage of processing		To allow archive to contact preparer?  Not generally collected.
Line 41: Handover	Pointers to the components to be transferred to the archive		How does this differ from inventory in Data Topic
Line 43: Handover	Potential preservation aims of the archive		Part of Archive Support Plan
Line 49: Handover	Resident Archives		Intermediary between provider and archive in some cases for maintaining specialized h/w or s/w.

Mike, could you please tell me if this analysis is correct or not? Are some of them included in other lines of your table?

As an aim for our telecon, I suggest that we all give opinion on this list (grouping, what more to include or expand).

Regards,

Daniele

-----Message d'origine-----
De : Mike Martin [mailto:tahoe_mike at sbcglobal.net] Envoyé : mercredi 16 septembre 2015 15:32 À : Boucon Daniele Cc : John Garrett; david.giaretta at stfc.ac.uk; Sawyer at acm.org; rdowns at ciesin.columbia.edu; esther.conway at stfc.ac.uk; moims-dai at mailman.ccsds.org Objet : Possible scope reduction

Hi everyone

If you haven't started looking at the attachments here are two slightly edited versions.

Thanks, Mike