tag:blogger.com,1999:blog-7099013253406999323.post6867475122755077501..comments2023-05-09T00:03:39.102-04:00Comments on horothesia: Pleiades and other projects: Atom, GeoRSS and RDFAnonymoushttp://www.blogger.com/profile/10480131160743773420noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-7099013253406999323.post-38587790337719384172007-10-17T12:00:00.000-04:002007-10-17T12:00:00.000-04:00Sean and I chatted about the Atom example briefly...<A HREF="http://zcologia.com/sgillies" REL="nofollow">Sean </A> and I chatted about <A HREF="http://icon.stoa.org/trac/pleiades/wiki/AtomInsAph4-202" REL="nofollow">the Atom example</A> briefly on IRC this morning, and he had a couple of good ideas.<BR/><BR/>Firstly, my example doesn't exploit the full power of the "rel" attribute on the <link> tag in atom. As Sean put it: "atom gives you more power to express link relationships ... <A HREF="http://tools.ietf.org/html/rfc4287#section-4.2.7.2" REL="nofollow">the value of rel can be <B>any</B> url</A>." These URLs could be used to type links according to some mutually-agreed thesaurus.<BR/><BR/>Secondly, there's no good way to type or qualify <georss:where>. This is problematic given that epigraphists (for example) may know about a number of discrete locations associated with a single text (where it originally was placed, where it was first found, where it was subsequently observed). Of most interest to Pleiades are probably the original location and place(s) of finding, but we'd like to be able to tell which is which.<BR/><BR/>Sean suggested we try breaking down the "one text = one <atom:entry>" paradigm implied by my example, and instead provide an <atom:feed> populated by however many typed <atom:entry> elements we need to effect communication.<BR/><BR/>I'll try to have a go at refactoring the example with these suggestions in mind soon. Meantime, I'd be interested in others' reactions.Anonymoushttps://www.blogger.com/profile/10480131160743773420noreply@blogger.com