PID Information Types WG Final DeliverableDocument the Research Data Alliance Working Group's report on essential information types associated with persistent identifiers, including a conceptual model, API specification, prototype demonstrator, use cases, and example types.Submitter's Note: This StratML rendition has been inferred by ChatGPT from the text of the source, whose authors were Tobias Weigel, Timothy DiLauro & Thomas Zastrow. The group co-chairs were Beth Plale & Tobias Weigel. ^^ It has been minimally edited in the XForm at https://stratml.us/forms2/Part2Form.xmlResearch Data AllianceRDA_b6f1abc4-f0a9-11f0-9f63-425686babdf6Global community organization supporting open sharing and reuse of research data.PID Information Types Working GroupWorking group focused on essential types of information associated with persistent identifiers and their technical and governance enablement.PerformerDevelops the report, conceptual model, API specification, prototype demonstrator, and example types.PerformerRDA Persistent Identifier Interest GroupForum for ongoing PID-related coordination and follow-on evolution after working group termination.BeneficiaryUses and advances WG outputs as part of broader PID architecture discussions.BeneficiaryScience Communities & InstitutionsDiscipline communities and organizations adopting PID information types, contributing community-specific types, and converging on core types through practice.AdoptersImplement, test, and refine types and profiles through operational use cases.PerformerBeneficiariesGain more interoperable discovery, access, verification, provenance, and preservation services via typed PID metadata.BeneficiaryPID Infrastructure ProvidersProviders of PID systems and services (e.g., DOI/Handle-style infrastructures) that can offer PIT API services or enable adapters.Service providersOffer PIT API server-side capabilities or support community-layer implementations.PerformerBeneficiariesReduce integration complexity for clients and increase value of PID services through typed metadata access.BeneficiaryType Registry ServicesRegistry capability used to register properties and their aggregates, enabling governance, interoperability, and discoverability of types.EnablersProvide the registry functions required for property and type definitions and their reuse.PerformerInteroperable PID metadata empowers discovery, access, verification, and stewardship across disciplines.uuid-vision-7c1d3d9aTo enable practical, adoptable typing of PID record information through shared models, registries, and APIs.uuid-mission-8f5c2b11InteroperabilityPromote consistent, cross-system interpretation of PID record information through registered types and conformance checks.PragmatismFavor adoption pathways and lightweight mechanisms that communities can implement incrementally and refine through use.GovernanceSupport bottom-up convergence toward core types via registries, namespaces, and community coordination.ReusabilityEncourage reuse of properties, types, and profiles to reduce duplication and improve service portability.HarmonizationHarmonize essential information types associated with persistent identifiers to reduce integration complexity and enable cross-disciplinary services.uuid-goal-0a6a4f1c1TerminologyClarify core terms and distinctions, including PID record scope, metadata boundary considerations, and the relationship between typing and identifier-provider classifications.uuid-obj-1-1-0e2c1c7b1.1Includes clarifications around PID Information Types as umbrella concepts and distinctions between PID record information and broader domain metadata catalogs.1.1.1Terminology clarityReview ratinguuid-pi-1-1-1-0b9a3a21PLACEHOLDER_1ConsensusDocumented and internally consistentPublish a terminology section describing core entities and relationships with no unresolved internal contradictions.StatusReportedTerminological models and their mapping are described in the report (property-type-profile and type-profile models).Use CasesSpecify cross-disciplinary scenarios motivating typed PID information, including replication, access load leveling, format obsolescence audit, versioning, composite objects, bindings, permissions, write control, custom citation, modification accountability, and provenance tracing.uuid-obj-1-2-7f6a2dd81.2Use cases were captured via formal specification documents (Appendix A) rather than free-text narratives.1.2.1Use case coverageCountuuid-pi-1-2-1-5b2f7b93PLACEHOLDER_210Document at least ten distinct cross-disciplinary use cases in structured form.11Eleven use cases are listed and elaborated in Appendix A.FrameworkEstablish a conceptual and structural framework for defining, registering, and using PID information types, including properties, aggregates, profiles, and namespaces.uuid-goal-2c6c1c552ModelDefine the data model for PID records, registered properties, aggregated types, and optional profiles, including a mapping between alternative models and a recommendation favoring simplicity if adoption is hindered.uuid-obj-2-1-2f0bca3d2.1Models described: property-type-profile model (prototype) and type-profile model (simpler alternative); recommendation: abandon the more complex model if it hampers adoption.2.1.1Model implementabilityImplementation statusuuid-pi-2-1-1-7a7b0c12PLACEHOLDER_3PrototypeImplementedImplement at least one model end-to-end in a prototype service with conformance checking.PrototypeImplementedThe property-type-profile model is implemented in the prototype.RegistryUse a type registry as a governance and interoperability dependency by registering properties and types with identifiers, descriptions, provenance fields, and optional namespace conventions.uuid-obj-2-2-9d2bb7a42.2Registry entries include property name and range (defined in registry), plus descriptive and provenance information such as author, creation date, and contact address.2.2.1Registered examplesCountuuid-pi-2-2-1-3d2a8e9fPLACEHOLDER_44Register multiple example types and their associated properties in the type registry to demonstrate structure and reuse.5Example types include citation, system-level access, aggregation, versioning, and a preliminary EUDAT core information example.InterfaceDefine and demonstrate an API for accessing typed PID record information in a PID-system-agnostic manner, supporting filtering, conformance checking, and type/property lookup.uuid-goal-3b7b6d1e3SpecificationSpecify webservice methods for PID record access and registry lookup using JSON, including PID resolution with filtering and optional property-name injection from the type registry.uuid-obj-3-1-1b0d4c6a3.1Key methods include GET /pid/{identifier} with filters, GET /property/{identifier}, GET /type/{identifier}, GET /peek/{identifier}, and POST /pid for assignment with random UUID PID names in the prototype.3.1.1Core methods documentedCountuuid-pi-3-1-1-0f4a1c88PLACEHOLDER_54Document at least four core API methods supporting PID record retrieval and registry lookups.5At least five major methods are summarized, including read, peek, and create operations.PrototypeImplement a working prototype server and demonstrator client GUI to validate the API and illustrate typed PID record workflows and conformance checks.uuid-obj-3-2-8e1d0d0b3.2Prototype implementation described as a Java servlet using Jersey and ZK, deployable on Apache Tomcat, relying on a type registry prototype and a Handle Server installation; performance bottlenecks noted around frequent registry queries and suggested caching.3.2.1Demonstrator availabilityStatusuuid-pi-3-2-1-61d5b9dePLACEHOLDER_6AvailabilityOperationalProvide an operational demonstrator showing object records, type records, and conformance validation actions.AvailabilityDescribedInterface impressions and operational endpoints are described in the report, including GUI screenshots and base paths.AdoptionEnable sustainable, bottom-up adoption and evolution of PID information types across communities, balancing cross-system coherence with local flexibility.uuid-goal-4c0b7d3a4PathwaysPromote technical and conceptual adoption pathways, including provider-side API offerings, community-layer implementations, and community contribution of types toward eventual convergence on core types.uuid-obj-4-1-4f6a9a0d4.1Adoption considerations include governance for namespaces and elemental range types, attention to performance expectations and possible SLA integration, and coordination with the Type Registry evolution and Persistent Identifier Interest Group.4.1.1Adoption progressMilestone statusuuid-pi-4-1-1-2c1a1d7ePLACEHOLDER_7MilestoneCommunity pilots initiatedInitiate pilots in at least one adopting community to test types, profiles, and workflows and feed results into governance discussions.MilestonePlannedThe report recommends engaging communities for bottom-up adoption and evolution of core types.EnhancementsIdentify and prioritize future refinements, including multi-valued property handling, data model simplification if needed, API evolution while preserving agnosticism, and improved performance via caching strategies.uuid-obj-4-2-3b2c6c2f4.2Future work topics include multi-valued properties (repetition vs list vs subtype patterns), conformance computation vs explicit conformance storage, and clearer boundary criteria between PID records and metadata catalogs.4.2.1Enhancement backlogCountuuid-pi-4-2-1-77b1e5a4PLACEHOLDER_84Maintain a defined set of prioritized enhancement topics for follow-on work.5Refinement topics include data model, API, performance requirements, data fabric integration, and association of profiles with prefixes._b6f1add6-f0a9-11f0-9f63-425686babdf62015-07-102026-01-13https://zenodo.org/records/1405977#.XG5kauhKhaQ_b6f1b0f6-f0a9-11f0-9f63-425686babdf6OwenAmburOwen.Ambur@verizon.net