On Thu, Jun 24, 2004 at 04:11:02PM -0700, Bryce Harrington wrote:
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.
Do you mean the tag or name on the dialog? I was using the "dc:creator" tag in the XML, but the name "Author" in the dialog, since I thought it was more sensible.
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.
Well, it seems like the only place it could go without creating a new namespace. According to the spec, they suggest using a limited vocabulary.
Creative Commons Attribution-NonCommercial-NoDerivs
For brevity, perhaps 'Attribution' can be dropped?
Well, that's an _element_ of the license, so I'd rather not. Maybe "CC", but if someone isn't familiar with it. I think the "best" route would be just a simple "Creative Commons" license, and then when that's selected a radio-button section becomes selectable, and that has the various combinations there.
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.
Well, I'm not sure about this since the the selected license impacts the <License> tag, and that needs to be programmatic or do some kind of XML merge if people are adding their own stuff. I was just going to blow away the entire License tree and put in our own if someone changed the setting away from "Custom".