Let's see if we can avoid the IETF process for now and encourage Yahoo and Apple to get together with the community to work on some a common approach, get some implementations out there to evolve it a bit, then evaluate later whether or not IETF standardization makes sense. If the community can drive a viable solution without the overhead of a formalized standardization process, it will work out best for everyone and the anti-formal-standards crowd will have far less to complain about or will at least be able to devote more time to bashing atom ;-)
Danny Ayers wrote:
Sam - would I be thinking you've been trying to encourage the Yahoo! Media RSS folks to go IETF? What's the position with that? Background - as I'm sure everyone is aware, both Yahoo! and Apple have come out with extensions of RSS 2.0 for media. Yahoo! did there's in a relatively open list, though not through a standards org (I think ). Apple's was close-door, result: lot of overlap, clunky. But whatever, there's a need for audio/visual media description support in Atom. It would be better if this happened in a more controlled fashion than what's happened with RSS. Personally I'd like to see RDF compatibility from the start too. It's relatively straighforward to cover the Yahoo! & Apple extensions in the RDF model (with owl:equivalentProperty as appropriate) but I'm betting the code to usefully convert from the syntaxes in a useful fashion won't be trivial (how's validation coming along?). There's been a fair amount of related work done around RDF already (though not in the syndication domain), e.g. MPEG-7 is available in OWL. So, any thoughts on what might be a good approach to this? Cheers, Danny.
