On Tuesday, February 8, 2005, at 05:47 AM, Bill de h�ra wrote:
Robert Sayre wrote:-1 to using naming it @rel. <feed rel="core"> wouldn't make any sense at all--"The feed's relationship is 'core'." Relationship to what? <feed>...<link rel="core" href="?????" /> likewise makes no sense--what are you going to put in @href?Bill de h�ra wrote:So, is that a +1 or a -1 on the profile concept?
The problem is that switching on the content of an element/attribute is Atom's get out of jail card wrt extensibility. It is the default Atom extensibility model, as it's the only game we have to play that doesn't involve screwing about with the meaning of existing core data items or adding new core items. Allowing people to add elements in other namespaces under atom:feed or atom:entry and calling that extensibility is like saying a new carpet in my living room is an extension to my house - it's a crashingly weak approach.
[You mean we have to decide?!?. Now!?!]
+1 on the concept. I've seen enough cases in the last week to suggest it's useful.
-1 on "@profile" - use an @rel to hold the content instead. I'm not sure whether atom:feed should get an @rel or whether we should use atom:feed/atom:[EMAIL PROTECTED]
