Should Profiles be required to have their own URI identifier, rather than
just a short name?
Eg: http://srw.cheshire3.org/profiles/ccg/1.0/ vs 'ccg'
If they just have a short name, then we have the ever present name
collision issue. If they have just a URI, then there isn't a collision,
but it's harder to read. If they have both, then there's a collision (two
people defining the 'bath' profile for different fields) unless there's a
way to say which bath profile is meant... and we don't have that ability
at the moment.
The way to create that possibility would be to duplicate the schema/set
construction for profiles:
<profile name="bath" identifier="http://..../">
<title>Bath Bibliographic Profile</title>
But this isn't something which is ever sent over the wire in a query, it's
just part of the ZeeRex which is written once and forgotten.
So, after all that, I'm in favor of having just a URI to identify a
profile, rather than a short name or short name + uri.
,'/:. Dr Robert Sanderson ([log in to unmask])
,'--/::(@)::. Special Collections and Archives, extension 3142
,'---/::::::::::. Nebmedes: http://nebmedes.o-r-g.org:8000/
I L L U M I N A T I