[rant] In general I think that one should not extend the 'dc' namespace which ships with DSpace, but follow a procedure like this:
1) look around for one or more suitable schemas which already define
the attributes you wish to represent. If you find them, use
them. DSpace supports well any reasonable number of schemas (so
long as they can be mapped to a 1- or 2-level hierarchy).
2) create one or more local namespaces to hold any attributes which
are unique to your collection(s). Document these thoroughly, as
if you were a standards body. Consider whether your requirements
are really unique or only generally unmet -- you might wish to
offer your work for others to use and extend.
One should always try to use existing schemas if this is practical,
because their terms have agreed-upon meaning. Consider: if
information on your holdings is harvested by another site, how will
the harvester understand the attributes you have added?
If you must create new namespaces, publish your specifications so that
others will be able to understand and use them.
[end rant]
There has been some discussion of making DSpace's 'dc' schema
immutable for just such reasons, and of shipping additional
widely-used schemas (not yet identified) with the product.
--
Mark H. Wood, Lead System Programmer [email protected]
Asking whether markets are efficient is like asking whether people are smart.
smime.p7s
Description: S/MIME cryptographic signature
------------------------------------------------------------------------------ EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev
_______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
