Category URI's
I'm in the process of going through a number of application scenarios with Atom and I'm coming up with a problem because I cannot associate a URI with a category element. This is mainly coming up in the context of tagging. I want to be able to specify a tag and a URI that can be used to request a list of other items associated with that tag. What I want is: category scheme=... term=... href=... / What I end up having to do is: category scheme=http://.../tag; term=foo / link rel=http://.../tag; title='foo href=.../?tag=foo / Having an href attribute on the Category element strikes me as an obviously useful thing that we need to make sure gets into a future update of the specification. - James
Re: Category URI's
Hi James, * James M Snell [EMAIL PROTECTED] [2006-01-09 22:25]: What I end up having to do is: category scheme=http://.../tag; term=foo / link rel=http://.../tag; title='foo href=.../?tag=foo / you don’t spell your examples out sufficiently to decode them, but what you want sounds to me like you should be doing this or a variation thereof: category scheme=http://.../tag; term=?tag=foo label=foo / Regards, -- Aristotle Pagaltzis // http://plasmasturm.org/
Re: Category URI's
This makes sense but seems to assume using a scheme+term construction for building a URI, which makes sense in practical impl terms but is not codified in the standard. The scheme attribute is just an identifier. There is currently no normative means of associating or constructing a URI from a category element. Doing so should not be a requirement but it should be an option. A. Pagaltzis wrote: Hi James, * James M Snell [EMAIL PROTECTED] [2006-01-09 22:25]: What I end up having to do is: category scheme=http://.../tag; term=foo / link rel=http://.../tag; title='foo href=.../?tag=foo / you don’t spell your examples out sufficiently to decode them, but what you want sounds to me like you should be doing this or a variation thereof: category scheme=http://.../tag; term=?tag=foo label=foo / Regards,
Re: Category URI's
On 9 Jan 2006, at 9:33 pm, A. Pagaltzis wrote: category scheme=http://.../tag; term=?tag=foo label=foo / Blurgh. Graham
Re: Category URI's
Graham Parks wrote: On 9 Jan 2006, at 9:33 pm, A. Pagaltzis wrote: category scheme=http://.../tag; term=?tag=foo label=foo / category term=http://example.org/cat/foo; label=foo / cheers Bill
Re: Category URI's
* Bill de hÓra [EMAIL PROTECTED] [2006-01-10 00:50]: category term=http://example.org/cat/foo; label=foo / Good point. category scheme=http://example.org/tag; term=http://example.org/?tag=foo; label=foo / Regards, -- Aristotle Pagaltzis // http://plasmasturm.org/
Re: Category URI's
Sorry, I wasn't clear, what I need is to associate a dereferenceable URI with a category without requiring the client to construct one (e.g. by combining the scheme+term. The approach Bill suggested should work for what I need. I still think an href attribute may be useful in the future but, we'll see. Tim Bray wrote: On Jan 9, 2006, at 1:12 PM, James M Snell wrote: I'm in the process of going through a number of application scenarios with Atom and I'm coming up with a problem because I cannot associate a URI with a category element. From my Atom feed: category scheme='http://www.tbray.org/ongoing/What/' term='Technology/XML' / The scheme is identified by a URI. -Tim
Re: Category URI's
Yeah, that would work. However, whether or not to interpret the term as a dereferenceable url still comes down to an implementation detail. e.g. Terms associated with xyz scheme should always be interpreted as dereferenceable URI's. So i could say... category scheme=http://ibm.com/tag; term=http://example.org/mylist?tag=foo; label=foo / This should work for what I need. Thanks for the responses. - James Bill de hÓra wrote: Graham Parks wrote: On 9 Jan 2006, at 9:33 pm, A. Pagaltzis wrote: category scheme=http://.../tag; term=?tag=foo label=foo / category term=http://example.org/cat/foo; label=foo / cheers Bill
Reader 'updated' semantics
I'm looking for info about what the expected 'updated' datetime element semantics look like, andhaven't found anything in old email and the wiki on this topic. Is there a description somewhere? RSSBandit and FeedDemon don't pick up entry changes based on my changing the feed and entry 'updated' element to a later datetime. Instead I change the id element and get a 'new' entry, which is not desirable, since id for an entry should be a permanent uuid. I don't know how updates are supposed to occur. Thanks for any help,James
Re: Category URI's
James M Snell wrote: This is mainly coming up in the context of tagging. I want to be able to specify a tag and a URI that can be used to request a list of other items associated with that tag. Having an href attribute on the Category element strikes me as an obviously useful thing that we need to make sure gets into a future update of the specification. You've got to be kidding. Worst case you stick a couple of related link elements at the top of your feed for category specific feeds. Better would be to toss them on your webpage somewhere where a user might actually see them. An extra attribute in every category of every element which nobody is ever going to see strikes me as insane. The category element has some major problems, but this isn't one of them. Regards James
Re: Reader 'updated' semantics
On Jan 9, 2006, at 5:08 PM, James M Snell wrote: The updated element is used to indicate when a significant update has occurred to the entry. If you are updating the updated element when you update your entry, you are doing the right thing. If RSSBandit and FeedDemon are not picking up the fact that the entry has been modified based on a changed updated value (even if the updated element is the only thing that is different), then I would say those readers have a bug. You should never be changing your id element value. James is exactly right. The whole reason 'updated' exists is *exactly* so you can tell the downstream software unambiguously when some entry has changed and this ought to be brought to the consumers' attention. -Tim
