PILIN Project Outputs : Community Guidelines & Considerations
Outputs of the PILIN and PILIN ANDS projects, and related material produced by the PILIN team subsequently.
PILIN Stage 1 project outputs are linked to the original project website, but if that output has been superseded, the new output is listed here as well.
Outputs are coded to each of the three stages:
- 1 PILIN 1 = PILIN project proper
- 2 PILIN 2 = PILIN ANDS Transition project
- 3 PILIN 3 = Subsequent Outputs
- *Asterisked content has not yet been finalised or approved
Each output is followed by the Handle for the work (which resolves to the latest published version).
- Community Guidelines & Considerations
-
- Form of Labels 1 hdl:102.100.272/0HJ9X8JQH
- These guidelines present considerations for projects deciding a format for their identifiers.
- Meaningfulness of Labels in Identifiers 1 hdl:102.100.272/D6N8F0DQH
- This describes issues confronting projects in determining a label policy. It addresses in particular the benefits and costs for projects choosing between meaningful, opaque, and arbitrary labels.
- Considerations for Ownership of Identifier Management Systems 1 hdl:102.100.272/461BL3DQH
- What arrangements parties should make for owning and managing identifier management systems: whether they should manage the system themselves or jointly with other parties, and whether they should have exclusive access to the identifiers managed through the systems.
- Namespace Management: One Or Many?: Pros and Cons of Multiple Namespaces 2 hdl:102.100.272/LY1QRDTRH
- Considerations on whether a single namespace should be supported nationally by a national identifier service provider, or whether multiple distinct namespaces should remain decentralised. Summarises Considerations for Ownership of Identifier Management Systems 1.
- Considerations for Managing Contexts 1* hdl:102.100.272/N8R5K6DQH
- This document outlines considerations for parties on how best to manage the contexts for their identifiers. It presents the PILIN model of identifier contexts, and discusses context realisation, context naming, and context scope.
- Identifier Association Guidelines 1 hdl:102.100.272/WBNMH9DQH
- Guidance on what "things" should have persistent identifiers assigned to them by an identifier manager, and at what time.
- Persistence of Identifiers Guidelines 2 (supersedes v 1.0 1) hdl:102.100.272/V89DC0DQH
- Considerations for ensuring that identifiers remain persistent: overall guidance on how to plan for persistent identifiers in the domain. Strategies for maintaining persistence when one or more aspects of the domain change: the identifier name, the identifier context, the identifier authority, the thing identified.
- Identifier Persistence under Changed Management Conditions 2 hdl:102.100.272/B2BJVDTRH
- Guidelines to ensure that identifiers remain persistent under changed management conditions. This includes cases where the thing identified moves to a new trust environment, and where the identifier moves to a new system.
- Using URIs as Persistent Identifiers 2 (supersedes v.1.0 1) hdl:102.100.272/DMGVQKNQH
- Considerations for projects which choose to use URIs, and HTTP URIs in particular, as persistent identifiers.
- Resolution Service Guidelines 2* (supersedes v.1.0 1) hdl:102.100.272/1KKBLPDQH
- Best practice recommendations on distinguishing identifiers from service requests on those identifiers; distinguishing the identifier from the rest of the service request; ensuring that identifiers are seen to be actionable by more than one service.

