Re: On PaceXhtmlNamespaceDiv

On Feb 17, 2005, at 00:18, Robert Sayre wrote: >However, this is not going to reflect what's in MySQL. Does it need to? Could anybody except for you check? Should anybody (including you) care? Is it part of conformance? Yes. No. Yes. Yes. Why does the feed have to reflect what is in MySQL? What if

Re: PaceXhtmlNamespaceDiv

(BAt 01:35 05/02/11, Sam Ruby wrote: (B > (B >Julian Reschke wrote: (B (B >> Nor am I. The question is what's the best way to enhance the spec. One (Balternative suggestion was made by Martin D$B—S(Bst in (B: (B >> "Note: It is

Re: On PaceXhtmlNamespaceDiv

(BAt 19:03 05/02/16, Bill de h$B%b(Bra wrote: (B (B >> As long as it's XML and otherwise conformant, I think it's fine. (B >> >Probably not. Do you and Julian and Anne and Henri approve? (B >> I don't see how I would want to complain about how you generate (B >> your stuff, as long as the

Re: Madonna

On Feb 16, 2005, at 12:09 AM, Henry Story wrote: Now I would like to show how the Madonna example is relevant to Atom. In a mail recently Roy Fielding pointed to the following passage of the the RDF Semantics document: No, you pointed to that passage. I pointed to the RDF semantics intro. Moreove

Re: On PaceXhtmlNamespaceDiv

Henri Sivonen wrote: How's that relevant wrt. type='XHTML'? If you doubt the robustness of concatenation with XHTML, why wouldn't you keep using "entity-encoded HTML"? Anne Van Kesteren wrote: And, now I look at it, Robert is using HTML (the text/html MIME type implies that) so I do not see the

Re: Consensus call on last round of Paces

On Tuesday, February 15, 2005, at 08:11PM, James M Snell <[EMAIL PROTECTED]> wrote: > - If you just think it's not part of the core and can be added later, > fair enough, but that doesn't get around the fact that the current > spec, as written, does not allow extensions to change conta

Re: Posted PaceLangSpecific

On Wednesday, February 16, 2005, at 03:03PM, David Powell <[EMAIL PROTECTED]> wrote: >The purpose of the Pace isn't to ensure that databases don't lose language >tags: >it is to licence databases and other models to not preserve language tags where >they are not meaningful. Then, erm, why do

Re: On PaceXhtmlNamespaceDiv

On Feb 16, 2005, at 10:53, Robert Sayre wrote: This is how I generate my Atom 0.3 feed, using the popular Movable Type program: "> <$MTEntryBody encode_xml="1"$> How's that relevant wrt. type='XHTML'? If you doubt the robustness of concatenation with XHTML, why wouldn't you keep using "entity

Re: Consensus call on last round of Paces

On Tuesday, February 15, 2005, at 07:29PM, Tim Bray <[EMAIL PROTECTED]> wrote: >PaceClarifyDateUpdated >A couple of -1's, one fuzzy +1. >DISPOSITION: Close it. Where'd you get this idea? I see two +1s: http://www.imc.org/atom-syntax/mail-archive/msg13249.html http://www.imc.org/atom-syntax/mail-

Re: Posted PaceLangSpecific

Quoting Karl Dubost <[EMAIL PROTECTED]>: > >>> Implementations MUST preserve the language context of language > >>> sensitive constructs. [...] > If it's about stocking information in a database and that this > information is not lost, I don't see how it's related to Atom. It's a > separate des

Re: Posted PaceLangSpecific

Le 14 févr. 2005, à 23:19, Tim Bray a écrit : On Feb 7, 2005, at 8:36 AM, Graham wrote: On 7 Feb 2005, at 8:29 am, David Powell wrote: Implementations MUST preserve the language context of language sensitive constructs. I have no idea what I'm being asked to do. Equally mystified by that sentence.

Re: On PaceXhtmlNamespaceDiv

Bill de hÃra wrote: As long as it's XML and otherwise conformant, I think it's fine. Do you and Julian and Anne and Henri approve? I don't see how I would want to complain about how you generate your stuff, as long as the result is following the specs. The point I'm seeing here is that creating mar

Re: On PaceXhtmlNamespaceDiv

Martin Duerst wrote: >This is how I generate my Atom 0.3 feed, using the popular Movable Type program: > > > mode="escaped" > xml:lang="en" > xml:base="<$MTBlogURL encode_xml="1"$>"> > <$MTEntryBody encode_xml="1"$> > Not a single namespace declaration here, s

Re: On PaceXhtmlNamespaceDiv

Hello Robert, I'm not sure I understand your point(s) from your mail below. At 17:53 05/02/16, Robert Sayre wrote: >This is how I generate my Atom 0.3 feed, using the popular Movable Type program: > > mode="escaped" > xml:lang="en" > xml:base="<$MTBlogURL encode_xml="1"$

Re: On PaceXhtmlNamespaceDiv

Martin Duerst wrote: [I appologize that this comes late. I was ill last week.] I'm also still not convinced about this one. It was introduced with a very good motivation, namely that it would increase the chance that namespaces would be used correctly. After the changes, what I understand is left i

Re: On PaceXhtmlNamespaceDiv

Martin Duerst wrote: ... For the record: I agree with Martin's analysis. Best regards, Julian

Re: Madonna

Now I would like to show how the Madonna example is relevant to Atom. In a mail recently Roy Fielding pointed to the following passage of the the RDF Semantics document: [[ It assumes, implicitly, that URI references have the same meaning whenever they occur. To provide an adequate semantics whi