I've also been working recently on an RDFS for DSpace that has this
detail defined explicitly for our our application, I would use
something like PREMIS if it fit into the RDF world more cleanly.
Its also my opinion that the while the "DC Library Application
Profile" was a nice start at organizing how Dublin Core might be used
by Library Application, it is very behind the current RDF related
specifications and the consolidation and merging of the dcterms
namespace.
I'm also working with the Bibo community in the hopes that their
project will produce some interesting bibliographic RDF tooling for
applications such as DSpace.
So, an RDFS version of PREMIS or similar
A overly simple File properties schema
http://downlode.org/Code/RDF/File_Properties/
JHove does provide this level of technical metadata, though the data
generated is in the similar domain as soem of the PRemis Object
properties, but not identical.
My concern is that I really don't need all the rights/etc related
PREMIS stuff and I certainly could do without heavily hierarchical/
nested element structures that are only used for grouping.
JHove doesn't not explicitly use "PREMIS". Its metadata is more RDF
like.
http://hul.harvard.edu/jhove/examples.html
Seeing something that explicitly represents the technical attributes
of "file like resources" would be very useful and popular indeed if
it came from an existing well respected standards body.
Sincerely,
Mark Diggory
On Sep 5, 2008, at 6:37 AM, Rebecca S. Guenther wrote:
> I would argue that this sort of information is technical metadata that
> needs to be associated with the objects in a repository. It is used
> for
> managing (including preserving) the objects, not for discovery, so
> doesn't
> belong with descriptive metadata. There is a well developed
> standard for
> this sort of information (PREMIS):
> http://www.loc.gov/standards/premis
>
> Rebecca
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> ^^ Rebecca S. Guenther ^^
> ^^ Senior Networking and Standards Specialist ^^
> ^^ Network Development and MARC Standards Office ^^
> ^^ 1st and Independence Ave. SE ^^
> ^^ Library of Congress ^^
> ^^ Washington, DC 20540-4402 ^^
> ^^ (202) 707-5092 (voice) (202) 707-0115 (FAX) ^^
> ^^ [log in to unmask] ^^
> ^^ ^^
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
>
> On Thu, 4 Sep 2008, Karen Arcamonte wrote:
>
>> Thank you for your reply. It was a relief to hear that things
>> aren't so
>> perfect. As for DC Format, I wish it or the DC schema as a whole
>> could cover
>> more technical information, because it seems very limited if you
>> are a
>> multimedia library of mostly images and some sound and video. I
>> have seen
>> some implementations use the field as almost a catchall, but i'm
>> guessing
>> that is wrong. What we've had to do is to extend our schema with
>> several
>> additional technical fields (called Digitization Methods,
>> Digitization
>> Details and Capture Methods).
>>
~~~~~~~~~~~~~
Mark R. Diggory - DSpace Developer and Systems Manager
MIT Libraries, Systems and Technology Services
Massachusetts Institute of Technology
Home Page: http://purl.org/net/mdiggory/homepage
|