Use Cases and Functional Requirements Goal Agree on

Use Cases and Functional Requirements Goal: Agree on prioritization and scope of requirements Sources – UDFR Technical Working Group: • The Functional Requirements for Phase 1 Technical Development of the Unified Digital Format Registry (UDFR) • Complete list of UDFR use cases on UDFR wiki

Use Cases - Documented Edit: • Add & Update Record • Amend Audit Trail Discover: • Search and Browse Records • Browse Audit Trail Delivery: • Retrieve record via web interface or web service • Retrieve format identification information • Retrieve audit records

Use Cases – Undocumented (1) Edit Provide Editorial Oversight Security Authenticate Registry User Manage Support editorial Review Metadata and Process Storage Be capable of expressing level of editorial review

Use Cases – Undocumented (1) Edit Provide Editorial Oversight Security Authenticate Registry User Pending Decision on who can edit records Manage Support editorial Review Metadata and Process Storage Be capable of expressing level of editorial review

Use Cases – Undocumented (2) Delivery Export records to repository software Discovery Support preservation service software Storage Support local copies of the registry

Use Cases – Undocumented (2) To the extent that Delivery Export records to repository software records can be exported Discovery Support preservation service software Storage Support local copies of the registry

Use Cases – Undocumented (3) Delivery Export format information for a format identification tool Storage Manage audit trail Storage Be capable of associating an arbitrary number of notes with records Storage Be capable of associating an arbitrary number of docs with records

Use Cases – Undocumented (3) Delivery Export format information for a format identification tool DROID signature file Storage Manage audit trail Versioning Data Model Storage Be capable of associating an arbitrary number of notes with records Storage Be capable of associating an arbitrary number of docs with records Architecture

Use Cases – Undocumented (3) Delivery Export format information for a format identification tool DROID signature file Storage Manage audit trail Versioning Data Model Storage Be capable of associating an arbitrary number of notes with records Storage Be capable of associating an arbitrary number of docs with records Architecture

Appendix - Requirements

Functional Requirements. Administrative Req Number Requirement UDFR-SYS 28 There would also be a mechanism to add new related data records to the registry H UDFR-SYS 29 The editor is authenticated and is allowed to execute this feature (add new record) H UDFR-SYS 30 The system adds administrative information to the registry used in the record's audit trail H UDFR-SYS 39 If a system error has occurred, the web interface should roll back all data insertion to the registry M Priority Clarification UDFR registry will be capturing provenance information.

Functional Requirements. Governance (1) Req Number Requirement Guaranteed public access to the UDFR-SYS-31 representation information Priority Clarification To be discussed at H Stakeholder meeting. Suppress from public view for a limited embargo period some representation information in order to protect proprietary, trade secret, or other legally-encumbered information. / Ability to manage in the local copy of the registry local information that is not supposed to be shared with other registry instances. There are two goals for this requirement: manage in the local instance information that the institution has no right to share (information on software for example), manage information on local preferences (format preferences, local UDFR-SYS-32 policies…). M Scenarios: (1) Private area, not replicable (2) Private area, replicable (3) No Private area

Functional Requirements. Governance (2) Req Number Requirement UDFR-SYS 33 Support editorial oversight or some form of quality vetting of contributed registry information UDFR-SYS 34 Be maintained and sustained by a permanent governance body Priority Clarification M What is the minimum governance model that the registry should support? Is it a matter of setting status or does some sort of workflow model need to be considered? L To be discussed at Stakeholder meeting.

Functional Requirements. Storage Req Number Requirement UDFR-SYS 40 Store sample files for each format created by different applications (e. g. a PDF produced by Adobe PDF Library 4. 8). M UDFR-SYS 41 Store format specifications Priority H Clarification

Functional Requirements. Validation Req Number UDFR-SYS 38 UDFR-SYS 42 Requirement If the record is associated with other data records, for example a format record may be associated with certain software, the system adds the associations into the registry Priority Clarification H Constraints will be those defined within GDFR and PRONOM specifications The system validates all data attributes, H UDFR-SYS 43 The system provides verification of successful record insertion to the registry along with the identifier associated with the record UDFR-SYS 44 If an error occurs during attribute validation, the web interface should provide explicit hints for the editor to fix the data entry H M This will be most likely be handled by constraints.

Interface Requirements (1) Req Number UDFR-SYS 45 Requirement Support distributed input of registry information UDFR-SYS 46 The web interface should populate related data from existing records in the registry. For example, when the editor associates software, say Acrobat Reader, to a format record (ex. PDF 1. 6) , the web interface should display existing software for users to choose from H UDFR-SYS 47 Provide end-user interfaces for discovery and delivery of managed representation information for human and automated agents H Priority Clarification H This will be handled by Controlled Vocabulary

Interface Requirements (2) Req Number Requirement UDFR-SYS 48 The input process should be easy to use but result in machine actionable output H UDFR-SYS 49 UDFR-SYS 50 Provide a mechanism for the distribution of the registry data to the local instances Interface should present all required and optional fields in their proper format The interface should be self-explanatory and intuitive with hints/helps provided for some fields for additional assistance in data entry All controlled vocabularies should be presented directly on the web interface UDFR-SYS 51 UDFR-SYS 52 Priority M H H H Clarification All format data is represented in RDF which can be serialized as RDF/XML for actionable output A distribution mechanism will be recommended.

Data Structures Requirements (1) Req Number Requirement Priority Storage of format representation UDFR-SYS information of as many different formats as -1 possible H The UDFR will follow evolving best practices UDFR-SYS for the secure, sustainable management of -2 format representation information H For local registry instances: ability to express value assessment and priorities for using UDFR-SYS formats. For example: prefer. rtf than. doc, -3 prefer TIFF than JPEG. M Clarification

Data Structures Requirements (2) Req Number Requirement Priority Descriptive representation information should include a format classification providing a means to indicate a format's (using terminology drawn from the GDFR Format Classification) genre, role, composition, UDFR-SYS encoding form, constraint, basis, domain, -4 transformative nature H UDFR-SYS -5 Agents can be either corporate or individual H Semantic representation information should include an arbitrary number of specification documents; an arbitrary number of format assessments expressed in some formal notation, such as Library of Congress FDD, etc. ; UDFR-SYS an arbitrary number of informative notes -6 documenting format semantic properties. H Support the binding of various typed UDFR-SYS representation information [ISO 14721] to -7 format identifiers L Clarification Mapping to UDFR schema and data within model

Data Structures Requirements (3) Req Number Requirement Priority Descriptive representation information should include an arbitrary number of namespaced identifiers publicly associated with the format, such as MIME type, PUID, GDFR identifier, Apple UTI, Library of Congress FDD identifier, standard identifier (ANSI, ECMA, FNOR, ISO, ITU, NISO, etc. ), UDFR-SYS IETF RFC identifier, IANA identifier, W 3 C -8 recommendation identifier, etc. H Syntactic representation information should include arbitrary number of typed external signatures; arbitrary number of internal signatures; an indication of byte ordering: bigendian, little-endian, either, both, or unknown; an arbitrary number of format grammars expressed in some formal notation, such as ABNF, BSDL, DFDL, EAST, XCEL, etc. ; an arbitrary number of example UDFR-SYS files. ; an arbitrary number of informative notes -9 documenting format syntactic properties. H Clarification To be discussed at Stakeholder meeting. We may need some input as to which controlled values to use if not explicit in existing GDFR/PRONOM data specifications

Data Structures Requirements (4) Req Number Requirement Priority Behavioral information should also include arbitrary number of software processes that are not necessarily dependencies (that is, they are not necessarily required in order to use the format) that accept a given format as an input or output. These processes should be typed with regard to their UDFR-SYS supported operation, e. g. validator, transformer, -10 renderer, etc. --Abrams 21: 26, 19 May 2010 (UTC) H Documents can be described in terms of Title; Edition; Authoring agent(s); Publishing agent(s); Date of publication; an arbitrary number of formal identifiers, such as DDC, ICC, IETF BCP, IETF RFC, IETF STD, ISBN, ISO, ITU, LCCN, OCLC number, SICI, etc. ; Document language; Document type; an indication of the IPR status of the document; an arbitrary number of informative notes documenting UDFR-SYS document properties; an arbitrary number of files -11 that contain manifestations of the document content. H Clarification We need the controlled vocabularies used to express the Type. We need the controlled vocabularies used to express the types. We need a list of identifiers to support.

Data Structures Requirements (5) Req Number Requirement Priority Files can be described in terms of Name; File type, such as data, executable, object code, source code, etc. ; an arbitrary number of typed message digest values, such as CRC-32, MD 5, SHA-1, SHA-256, etc. ; an indication of the IPR status of the file; Agent(s) UDFR-SYS who hold a copy of the file; an arbitrary number of -12 informative notes documenting file properties. H The UDFR representation information should be capable of expressing the descriptive, administrative, syntactic, semantic, and behavioral UDFR-SYS properties of formats pertinent to curation and -13 preservation analysis, decision making, and activities H All representation information will be tagged to UDFR-SYS indicate the level of centrally-coordinated review by -14 the UDFR governing authority or its designees. M Support embargo metadata for representation UDFR-SYS information to protect proprietary, trade secret, or -15 other legally-encumbered information M Clarification Controlled vocabularies taken from existing GDFR and PRONOM data specifications. Assumption is that these properties are fully expressed in GDFR and PRONOM 6. 2 Data Models To be discussed at Stakeholder meeting.

Data Structures Requirements (6) Req Number Requirement UDFR-SYS Descriptive representation information will -16 include: a canonical UDFR identifier UDFR-SYS -17 UDFR-SYS -18 UDFR-SYS -19 UDFR-SYS -20 Descriptive representation information should include a format version identifier, as issued by the legitimate maintenance agency Local holdings are described in terms of a locallymeaningful identifier, an indication of public accessibility to the file. Descriptive representation information should include an arbitrary number of common names publicly associated with the format Descriptive representation information should include a short discursive description of the salient properties of the format Priority H Clarification An initial grammer for the identifier has been specified The model schema will support version identifiers. The population of the data is the responsibility of the institution that populated it. M To be discussed at Stakeholder meeting. H Satisfied through skos: alt. Label H H

Data Structures Requirements (7) Req Number Requirement Priority Descriptive representation information should include (using terminology drawn from the GDFR Format Model and Relationships) affinity, containment, definition, extension, modification, UDFR-SYS requisition, restriction, semantic equivalence, -21 syntactic equivalence, version H UDFR-SYS Descriptive representation information should -22 include an arbitrary number of informative notes H Administrative representation information should include the corporate or individual agent(s) that created the format, the corporate or individual agent(s) that hold the intellectual property rights to the format, the corporate or individual agent(s) responsible format maintenance, the format creation or release date, the format withdrawal date, an indication of the IPR status of the format, UDFR-SYS an arbitrary number of informative notes -23 documenting format administrative properties. H Clarification

Data Structures Requirements (8) Req Number Requirement Priority Behavioral representation information should include an arbitrary number of format software dependencies, an arbitrary number of format hardware dependencies, an arbitrary number of format media dependencies, an arbitrary number UDFR-SYS of informative notes documenting format -24 behavioral properties H IPR status can be described in terms of the agent holding the rights; the effective date of the rights claim; the expiry date of the rights claim; the legal jurisdiction in which the rights claim is made; the type of rights claim, such as copyright, patent, trade secret, etc. ; license terms of use for the items covered under the rights claim; an arbitrary UDFR-SYS number of informative notes documenting the -25 rights claim. H Clarification

Data Structures Requirements (9) Req Number Requirement Priority All representation information will be tagged with UDFR-SYS provenance information sufficient to provide a -26 complete audit trail of changes over time. H UDFR-SYS -27 Mapping to DROID L UDFR-SYS Use a controlled namespace for the unambiguous -35 persistent public identification of digital formats H UDFR-SYS UDFR identifiers should be amenable for human -36 purposes and resilient against transcription error H The system assigns a unique and presistent UDFR-SYS identifier for the new record and adds record to -37 the registry H Clarification Assumption is that all provenance properties are fully expressed in GDFR and PRONOM 6. 2 Data Models URIs are not necessarily machine actionable. UDFR identifiers should prefer names over codes and be as short as possible. We will have a grammar to define the UDFR identifiers. Every resource in the model has a URI.

Use Cases and Functional Requirements Anything else?