Comments on: I2: Background http://lackoftalent.org/michael/blog/2009/05/19/i2-background/ The occasional rambling of a digital library artisan Fri, 02 Dec 2011 10:37:42 +0000 hourly 1 http://wordpress.org/?v=3.3.2 By: Michael Giarlo http://lackoftalent.org/michael/blog/2009/05/19/i2-background/comment-page-1/#comment-93168 Michael Giarlo Tue, 19 May 2009 23:41:23 +0000 http://lackoftalent.org/michael/blog/?p=312#comment-93168 @Jonathan Reasonable question. And I too am a fan of simple solutions. I have two answers for you. 1. The group has not yet begun looking at or thinking about the identifier standard itself. Work has been moving slowly, so we're just now getting to community outreach and needs assessment. Once we've got a good sense of needs, we'll start looking at particular solutions, several of which I imagine will be based off of DNS. That's more or less the official answer, to the extent that I may speak officially (which is very little). 2. As far as what -I- have been thinking of, and hoping will match needs, well, yes, that is based off of DNS. The issues you raise w/ DNS are the ones I'd worry about too, especially if there are use cases for, say, identifying departments and units, etc., where DNS does not necessarily model organizational hierarchy very well (though it certainly may). Thanks for the comment, Jonathan. @Jonathan

Reasonable question. And I too am a fan of simple solutions. I have two answers for you.

1. The group has not yet begun looking at or thinking about the identifier standard itself. Work has been moving slowly, so we're just now getting to community outreach and needs assessment. Once we've got a good sense of needs, we'll start looking at particular solutions, several of which I imagine will be based off of DNS. That's more or less the official answer, to the extent that I may speak officially (which is very little).

2. As far as what -I- have been thinking of, and hoping will match needs, well, yes, that is based off of DNS.

The issues you raise w/ DNS are the ones I'd worry about too, especially if there are use cases for, say, identifying departments and units, etc., where DNS does not necessarily model organizational hierarchy very well (though it certainly may).

Thanks for the comment, Jonathan.

]]> By: Jonathan Rochkind http://lackoftalent.org/michael/blog/2009/05/19/i2-background/comment-page-1/#comment-93167 Jonathan Rochkind Tue, 19 May 2009 22:08:29 +0000 http://lackoftalent.org/michael/blog/?p=312#comment-93167 Now, I know that when a simple solution seems to present itself in the identifier world, it usually means the thinker just doesn't know enough about the problem, but... Is there any reason a registered DNS hostname won't do as an institutional identifier? I think jhu.edu serves as a pretty good institutional identifier for my place of work. Well, except right after I write that, I think of all the things that make this more complicated at my own particularly complexly organized institution. (For starters, how do you decide the boundaries of an institution vs. a sub-part or super-part?). But are you thinking of something based off of DNS? Now, I know that when a simple solution seems to present itself in the identifier world, it usually means the thinker just doesn't know enough about the problem, but…

Is there any reason a registered DNS hostname won't do as an institutional identifier? I think jhu.edu serves as a pretty good institutional identifier for my place of work. Well, except right after I write that, I think of all the things that make this more complicated at my own particularly complexly organized institution. (For starters, how do you decide the boundaries of an institution vs. a sub-part or super-part?).

But are you thinking of something based off of DNS?

]]>