[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Handle-info] Fwd: Handle custom type registration

Hi,

Someone at CNRI will post a more elaborate response to this later, but I think this is fundamentally correct, with a few caveats.

o Assigning handles to types is a good idea.

o The exact syntax of the handle is not so important. If you put 'TYPE' on the left side of the slash, you have to have the ability to create a new prefix or you have to pay for a new prefix. That may not be ideal if you are only creating one or two handles. Putting 'TYPE' on the right side would be fine, or just skip the 'TYPE' string all together.

o More important is the ability to publish a set of types and for others to find them. Wheel re-invention, etc. Our to-do list here includes establishing a searchable type registry, and we will do so unless someone beats us to it.

o While the boundaries are a little fuzzy, the 0.TYPE prefix should be restricted to types that are used at the handle system core, i.e., what the system itself needs to function. We've probably already violated that ourselves (URL) but will try to keep to that principle in the future. What is then open for debate is what constitutes the core. Admin types are clearly in, but what about XML schemas for the values of common handle types?

o Not quite sure what this

The Handle server dedicated to types should be named with the
suffix ".TYPE".

means.

Larry


On Sep 25, 2007, at 8:38 PM, Nick Nicholas wrote:

Hello,

At the PILIN project, we are developing some demonstrator applications
 based on Handles that require new custom Handle types. We would like
to identify and manage the custom types within the Handle System by
giving them their own Handles, which may be managed locally instead or
centrally. Is there any best practice or guidelines for doing this?

Based on CNRI practice for 0.TYPE, and practice implicit in CNRI's
recent use of 100.TYPES, we have been considering the following
convention:

    * A Handle type is labelled through a Handle identifier, encoded
as Naming Authority + "/" + Handle suffix.
    * The Handle identifier for a Handle type is preferably stored on
a Handle server dedicated to types.That server can be any local Handle
server.
    * The Handle server dedicated to types should be named with the
suffix ".TYPE".
    * The Handle record defining the type shall consist of a DESC
field giving a prose description of the type.
    * The Handle server 0.TYPE is implicit. So the type URL is
interpreted as hdl:0.TYPE/URL , whereas the type 102.100.TYPE/URL is
interpreted as hdl:102.100.TYPE/URL.

Any thoughts?


--
===
Nick Nicholas
Business Analyst, PILIN Project, ARROW
Monash University Library
Building 4
Monash University VIC 3800 Australia
Tel: (+61 3) 990 50590
skype: opoudjis
Email: nick.nicholas@lib.monash.edu.au


_______________________________________________
Handle-Info mailing list
Handle-Info@cnri.reston.va.us
http://www.handle.net/mailman/listinfo/handle-info





=========================================
Larry Lannom
Corporation for National Research Initiatives (CNRI)
Suite 100, 1895 Preston White Dr, Reston, VA 20191

email:  llannom@cnri.reston.va.us
tel:  703 620 8990



_______________________________________________
Handle-Info mailing list
Handle-Info@cnri.reston.va.us
http://www.handle.net/mailman/listinfo/handle-info