If it is the case that there is evidence that changing this tag will break
commercial applications, then leaving it alone is probably the best thing to
do.
IF it is true that changing this NOW will only impact a tiny number of
people whose attention is focussed on this discussion, then lets change it
to something more intuitive now , so we don't have to spend the rest of our
lives explaining what an eorschema is????
stu
-----Original Message-----
From: Wagner,Harry [mailto:[log in to unmask]]
Sent: Friday, December 14, 2001 10:32 AM
To: [log in to unmask]
Subject: eor:Schema tag
All,
As you know we currently associate the administrative metadata about each of
the DC schemas to the eor:Schema class. I had proposed we change this to
reflect a convention that was likely to be more widely adopted. This would
allow the registry application to easily identify schemas. Since it seems
unlikely that everyone will ever agree on one class to associate with rdf
schemas I now propose we leave the eor:Schema tag as it is. The registry
import/infuse service will look for this tag and, if found, will use this
information for the schema admin metadata. The import/infuse service will
also provide a form to override (or provide) this information. Either way
the information will be required to import a schema. The form will include
the same information that we currently capture: title, publisher,
description, language, etc. and possibly a few aditional items. There is a
mock-up of this form included in prototype 2 at:
http://wip.dublincore.org:8080/registry/authServlet?req_type=login
As always, this reflects my own person view. Your comments, suggestions,
etc. are always appreciated.
Regards,
Harry Wagner
OCLC / DCMI
Dublin, OH 43017
(614) 761-5178
mailto:[log in to unmask]
|