1. Draft Data Foundation and Terminology (DFT) Vocabulary Development Process Prepared for WG-Core meeting 24/25.2 Munich/Garching Gary Berg-Cross Co-Chair DFT WG A PID record that points to a metadata record and to instantiations of identical bit- streams that may store additional attributes

2. DFT Goals Describe a basic, abstract (but clear) data organization model that systemizes the already large body of definition work on data management terms, especially as involved in RDA’s efforts. The model and its derived reference data should be sound, practical and agreed to within the community for use: across communities and stakeholders to better synchronize data conceptualization, to enable better understanding within and between communities, and to stimulate adopters & tool building, such as for data services, supportive of the basic model’s use. Need to get the story straight on model to govern the use of related tools. Candidate List Evolves to Refined List Cross WGs DFT WG Discussion & Plenary 3 Future Work 2015?

3. Draft Data Foundation and Terminology (DFT) Vocabulary Development Process by Gary Berg-Cross Five Stage process 1.Start up/Scoping Requirements analysis and development of candidate list 1.Tool prototyping 2.Vocabulary Analysis & Revision Process (3 rd Plenary) 1.Tool demo and final requirements 3.Focused Vocabulary Design Process and Community Agreement (after 3 rd Plenary) 4.Refinement & Maintenance (ongoing) 5.Draft Vocabulary Publication and Review (4 th Plenary)

4. Overview of Term Development Starter areas and items : Persistent Identifiers (PIDs and types) Digital Object - Data Object Collection - Data Set - Aggregation Repository (Registries and related Policies Scope Terms from Model Papers Placed In Tool Digital Information Object A digital item or group of items referred to as a unit, regardless of type or format that a computer can address or manipulate as a single object. Defs & Refinement Analysis and Revision Process Getting Defs organized for review

5. Term Definition Example digital entity: An entity represented as, or converted to, a machine-independent data structure consisting of one or more elements in digital form that can be parsed by different information systems; the structure helps to enable interoperability among diverse information systems in the Internet. From Framework for discovery of identity management information Alternative? This page was last modified on 9 December 2013, at 14:03. Revision Discussion: : This definition does not refer to our practice and is not specific enough. A digital object can cover different types of digital information such as data, software, knowledge etc. So we should separate data and other types of digital information. Also the reference to databases is not useful enough since there are many types of “containers” data is in - the term “database” does not help us since it refers to any type of container. And in DFT we need to stress the fact that a DO is something that has an identity one can refer to, that has a number of properties that can be accessed etc. Peter

6. PID Term and Discussion Discussion on email and Tool (http://smw-rda.esc.rzg.mpg.de/index.php/Talk:Persistent_Identifier_(PID)http://smw-rda.esc.rzg.mpg.de/index.php/Talk:Persistent_Identifier_(PID) We should emphasize that persistence is not purely technical, which is a point I think John Kunze in particular would agree to - there's social contracts associated with the idea of persistence. If you don't put those policies in place, persistence is undefined at best. Which, on 2 nd thought, also means that not just the resolution service is persistent, but also the association between identifier and target object. Which is a contract probably put on the shoulders of the agent requesting the PID in the first place, because the service will be unable to decide/maintain this.-- Tobias Tobias, you have evoked a few things such as PID Service (need to include this as a term). So should we have defs with the idea of a Contract by Agent as part of the metadata for a PID? Assertions: PID Requesting Agent (sub-type of Agent) contracts to maintain connection (definition?) between ID & Target Object. TO has contract. PID service is a service.– Gary The PID Service and the PID System might be the same thing in reality. One diff may be that the PID System is maintaining a Resolution Service, while the PID Service is the entity with which the contract is made. Each PID Service employs a PID System. Each PID System can be employed by several PID Services. Example for a PID Service: DataCite Example for a PID System: The DOI System Example for a Resolution Service: 2a00:1a48:7805:112:2c13:65be:ff08:2e89 - better known as dx.doi.org (In reality, there really is a contract between e.g. DKRZ and DataCite; so this seems adequate) TobiasWeigel (talk) 09:01, 10 December 2013 (UTC) TobiasWeigeltalk

7. Today’s Session- A focus on the following terms / term Data / Realtime Data / Gappy Data / Dynamic Data Digital Object / Registered Digital Object / Information Object Bit Stream / Instances of Bit Stream / Data Stream Identity / Integrity / Authenticity Object Property / Object Attribute / Property Record / Internal Property / External Property Persistent Identifier / PID Record / PID Attribute / PID Resolution / Reference Resolution Data Organization / Data Model Repository / Repository of Origin Aggregation / Collection / Data Set / Corpus / Container Data LifeCycle We can prepare this by looking at the stuff which is in the wiki and comparing etc. we need to make a quantum job in defining a few terms. We need to argue from the different data models/organizations that were presented and of course also look what others have done. clusters:

8. Peter’s Conceptual Space digital object bit stream instance of a bit stream service object informational object aggregation data object is_a is_part_of has_a has_many collection is_a metadata record PID record has_a is_a data stream is_equal data set is_equal corpus is_equal attribute has_a property contains_a

9. Some Notes/Questions on the Conceptual Space for the ­RDA DFT Term Definitions - Some existing stuff digital object bit stream instance of a bit stream service object informational object aggregation data object is_a is_part_of has_a has_many collection is_a metadata record PID record has_a is_a data stream is_equal data set is_equal corpus is_equal attribute has_a property contains_a Perhaps both Data and Service Objects are Informational Objects Better to say that a data set is a type of (Data) Collection. – not every collection is a data set…it could be a Corpus. A data steam is a Data Object, right? An instance of data stream is one Manifestation of the content of the original DO. Shouldn’t we show the relation between the PID and Metadata?

10. Status & Plan Going Forward We now a table of Core Terms with some initial Definitions These are also in the Tool perhaps some still being updated. Our Joint WG-Core meeting represents and opportunity to take stock and do some editing, testing of ideas and refining as well as strategize on next steps. Get some sense of agreement and where issues are for the WG-Core Preparation for 3 rd Plenary Documents Tool and Demo Discussion of working Core

11. Checklist of Issues - What is Needed for DFT Term Progress? Ramp up of effort by DFT WG Community Review of table, categories and definition refinement Confirmation of scope of work How do we handle points of contention? What is the process by which we converge and move to adoption? Training in and exposure of Term Tool Use by other WGs for their needs Is our table example useful as a model for them? Test of Scenarios – are they useful? Examples of term-concepts involved with real data What is a data set, what aggregation examples do we point to etc.?