Action PID Generator

Assigned

EK: ? ABR: 4 PKO: 3-5

Prev assigned

Tasks adressed

["Tasks/8/2"]

Time estimated

?+7-9md

Time used

Priority

1

Status

Not described

Iteration

24

Notes

Discuss the paper: IT- og Telestyrelsen (2006): Unikke identifikatorer til digitale objekter. Standard. Compiled by a working group and appoved at a meeting in 2006 of Datastandardiseringskomitéen.

The paper recommend to use Uniform Resource Name (URN), but would have recommended eXtensible Resource Identifier (XRI) as a more up-to-date and more elaborated method; but since XRI - contrary to expectation - was not accepted as standard under OASIS the working group could not recommend XRI for the time being

URN consist of 3 parts: 1) "urn" 2) Namespace identifier (NID) 3) Namespace specific String (NSS). NID is assigned by Internet Assigned Numbers Authority (IANA) and NSS is managed by the NID namespace responsible.

As NID you can use ISBN, ISSN, UUID or other number systems. Also there exist a national namespace, NZL (New Zeeland) as a NID. If an organisation wants its own NID, you have to apply for it at the Internet Engineering Task Force. The application shall also describe a possible structure for NSS and it is an obligation that the resources are available via Internet.

An alternative mentioned in the paper is Universal Unique Identifier (UUID). There are more versions of UUID and the standard is described in attachment 2 to the above mentioned paper.

The characteristics of UUID are

• a universal, unique identifier
• do not need central registration
• can be used of everybody
• can be generated without internet connection
• on-demand generating of UUId can be fully automatic
• not performance-demanding to generate
• almost no costs
• can not be resolved alone and therefore need a syntax as URN.

A time based UUID can be generated locally on a computer and will be universally unique because of the combination of

• the hardware address
• the timestamp
• the random principles.

On the internett there are free available UUID generators, e.g. here: www.int/itut/asn1/uuid.html

Checklist For Working On An Action

The Life Cycle of an Action:

• Assign people for action definition: Done at start of iteration status meeting. Fill out Assigned

• Define the action: Describe information about what is to be done and how. Fill out Tasks Addressed and Time Estimated.

• Review the definition: Get another project group member to review the action definition, and update it.

• Assign people for action implementation: Done by project manager, usually the same persons who wrote the definition. Fill out Assigned and Prev assigned if new persons are assigned.

• Implement the action: See details below

• Review the action: Get another project group member to review what is implemented (code and documentation), and update it.

• Finish the action: Change the status to "Finished" and update the "time used" field on the action page.

Please make sure that you address the below issues, when working on an action:

• Update the state of the action to "In Progress" when you start working on it.
• Check if the tasks addressed by this action have their status set to "In Progress". If that is not the case, then change the state of them.

• Keep track of how much time that has been spent working on the action. If it addresses more than one task, then make a note on the action page about how much of the elapsed time that has been spent on the individual tasks. Hint: Continually updating the "Time used" field will make it easier for you.

• Update the "Progress History" and documentation pages of each task addressed by this action when appropriate. This depends on the situation, but in general, the task pages should hold all important related information about the work done, experiences gathered, identified requirements and so on.