On Thu, 24 Jun 2004, Kees Cook wrote:
I have actually started this tab already (well, the ideas, anyway). The code is not far along at all, since I didn't have any good text-entry examples. :) But I did commit the changes needed to correctly track the RDF namespace in the XML.
I named the tab "Description". The items I was going to include were:
Title (dc:title) (freeform) Date (dc:date) (date) Author (dc:creator) (freeform)
Btw, I've been shifting SVG::Metadata over to use 'creator' instead of 'author', to be consistent with the RDF. I'll keep author as an alias to creator, though.
Owner (dc:rights) (freeform) Source (dc:source) (url) Keywords (dc:subject) (freeform)
I've been thinking about whether we should use subject for the keywords, or do something different... Ideally I'd rather have each keyword be a separate XML element, instead of a freeform string, so we can maintain some consistency over how it is parsed. What do you think? I haven't checked the schema to see if something like this is provided, but probably should... We could of course add it ourselves via a custom namespace, but I'd kind of like to avoid that if at all possible.
Description (dc:description) (freeform) License (license tag and License section) (pulldown)
(dc:type will be set to always contain rdf:resource="http://purl.org/dc/dcmitype/StillImage")
For the "License" section, I am initially going to just have a pull-down of: Custom Creative Commons Attribution Creative Commons Attribution-ShareAlike Creative Commons Attribution-NoDerivs Creative Commons Attribution-NonCommercial Creative Commons Attribution-NonCommercial-ShareAlike Creative Commons Attribution-NonCommercial-NoDerivs Public Domain
If "Custom" is selected, they can fill in another box that holds a URL.
For brevity, perhaps 'Attribution' can be dropped?
It would probably be wise to load the pull-down contents from the preferences.xml file, so users can override the settings when they need to.
Anyway, looks good so far!
Bryce