Hi, We're experimenting with adding new metadata schemas on DSpace. I come from a computer science background, so I am thinking hierarchically, like DNS and LDAP, where the hierarchies are essentially name spaces with common at the top, moving to more unique at the bottom:
. org. example. www. OR dc=org dc=example dc=www Naturally, I want to create a schema in DSpace which look like this: org.example.subject org.example2.subject My library guy prefers: org.subject.example org.subject.example2 Are there any technical reasons why we should use one over the other? Cheers, -- Alan Orth alan.o...@gmail.com http://alaninkenya.org http://mjanja.co.ke "I have always wished for my computer to be as easy to use as my telephone; my wish has come true because I can no longer figure out how to use my telephone." -Bjarne Stroustrup, inventor of C++ ------------------------------------------------------------------------------ See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk _______________________________________________ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette