On 8/12/08 6:19 PM, "Peter Keane" <[EMAIL PROTECTED]> wrote:
> This would be great in an ideal world, but the key-value pairs are all > arbitrary (created by users, serialized to atom for syndication & atompub > manipulation -- like in a spreadsheet -- column name/cell value). Sounds very much like you are trying to shoe horn non-categorical metadata into the atom:category construct. Please don't do this ;-) > Since I now use a simple extension element for these key-value pairs, I was > thinking about using category instead -- the Balisage paper I cited in my > original message piqued my interest there. (Oh, BTW my example left out the > scheme, which would be something like "http://example.com/metadata";). What would using the <atom:category/> syntax buy you that a <pkeane:key-value/> extension wouldn't? Surely you're not hoping for interoperability of your key-value data with the wider publishing world? >> <category >> scheme='http://www.loc.gov/catdir/cpso/lcco/' >> term="SF429.S65" >> label="siberian husky" /> > >> <!-- note: term may not be entirely accurate, IANAL --> >> <!-- (where L = Librarian, of course ;-) --> >> > This would certainly not work for me since I am, in fact, a librarian ;-)! (just curious btw - was I close with the LOC term for siberian husky, or did I clumsily misappropriate the wrong meta-data value from www.loc.gov?) e.
