On Tue, Dec 9, 2008 at 3:46 AM, Eric Scheid <[EMAIL PROTECTED]> wrote: > > On 9/12/08 1:53 PM, "Peter Keane" <[EMAIL PROTECTED]> wrote: > >> I am still puzzling over an AtomPub method to add >> categories to a collection > > I've long thought it should* be possible to do this via posting entries to a > designated collection, where each entry is "about" one category. The content > of the entry, ie. the nominated category, would go inside the > <atom:content/> element, with the <atom:summary/> available for any > comments/notes about it's use/provenance etc. The sweet thing about this is > that you can then use <atom:category/> elements (as immediate children of > <atom:entry/>) to designate category collection management meta-data. > > For example: > > <entry> > <title>Siberian Huskies</title> > <author><name>Sally "Woofer" Jones</name></author> > <category > scheme="http://example.com/atompub/atomcat/status"; > term="proposed" /> > <summary type="text">The dog breed</summary> > <content type="application/atomcat+xml"> > <category > scheme='http://www.loc.gov/catdir/cpso/lcco/' > term="SF429.S65" > label="siberian husky" > /> > </content> > </entry> >
This is very nice -- perhaps just what I was after. Up to now I have been (similarly) posting atom entries that represented the attribute but w/o using content atomcat+xml -- which makes good sense to me. I'll play with it a bit... --peter > > > Similarly, the same approach could be used to manage (say) the list of > authors available in the publishing system, the list of collections, a list > of publishing outputs, and so on. > > I don't recall if this would be technically valid though. I do note that the > RNC for atomInlineOtherContent allows anyElement (ie. isn't restricted to > anyForeignElement (which explicitly excludes atom:* elements)) > > e. > >
