Robert Sayre wrote:
Julian Reschke wrote:
Update -06: I'm still confused by the text. For instance:
- is it intentional that 4.1.3.3 says ``If the value of type ends
with +xml or /xml'', while 4.1.3.2 used ``If the value of type
begins with text/ or ends with +xml''?
Yes. In 4.1.3.3, you're
/ Robert Sayre [EMAIL PROTECTED] was heard to say:
| David Powell wrote:
|
|- in 6.4; extension schema allow the use of the atom namespace as child
|elements of the extension. I do not recall this being discussed, but
|personally am +1 to it.
| Yeah, I'm ok with it too. I'm not sure why anyone
Norman Walsh wrote:
The point is that extensions should allow atom:content inside the
extension, is that right?
Yes. Any atom element should be allowed in an extension.
Robert Sayre
On 16 Apr 2005, at 8:33 pm, Robert Sayre wrote:
MAY or MAY NOT. There's no right answer in there right now.
I'm OK with line-breaks being ignored, because it means documents where
the XML has been wrapped to 80 columns aren't messed up.
I'm not OK with publishers not being clear on the
Graham wrote:
On 17 Apr 2005, at 12:02 am, A. Pagaltzis wrote:
* Robert Sayre [EMAIL PROTECTED] [2005-04-16 21:45]:
Atom Processors MAY display it using normal text rendering
techniques such as proportional fonts, white-space collapsing,
and justification.
MAY or MAY NOT. There's no right answer
Graham wrote:
No, since xml:space isn't a built-in part of XML,
Duh! Why then is it described in
http://www.w3.org/TR/2004/REC-xml-20040204/#sec-white-space
and isn't referenced
by the atom spec. It can only be used when spec-makers (us) say it can.
...and I think it should be allowed on text
Thomas Broyer wrote:
(or any element using the CSS white-space property)
That is purely for presentation. You should not use it if you need
whitespace to be preserverd for semantics. (In such cases xml:space
would probably be more appropriate...)
--
Anne van Kesteren
On 18 Apr 2005, at 7:08 pm, Thomas Broyer wrote:
Duh! Why then is it described in
http://www.w3.org/TR/2004/REC-xml-20040204/#sec-white-space
It may be described there, but it doesn't do anything unless the
vocabulary on top of HTML says it does.
How are you supposed to write an HTML PRE (or
/ Robert Sayre [EMAIL PROTECTED] was heard to say:
| Norman Walsh wrote:
|
| The point is that extensions should allow atom:content inside the
| extension, is that right?
|
| Yes. Any atom element should be allowed in an extension.
Fix appended.
And I happened to notice that our example feed in
Norman Walsh wrote:
/ Robert Sayre [EMAIL PROTECTED] was heard to say:
| Norman Walsh wrote:
|
| The point is that extensions should allow atom:content inside the
| extension, is that right?
|
| Yes. Any atom element should be allowed in an extension.
Fix appended.
Thank you.
And I happened to
Anne van Kesteren wrote:
Thomas Broyer wrote:
(or any element using the CSS white-space property)
That is purely for presentation. You should not use it if you need
whitespace to be preserverd for semantics. (In such cases xml:space
would probably be more appropriate...)
Even if you use
Regarding the potential for a DoS attack with stealing somebody else's
GUIDs, no special hacks [1] are needed. Any decent aggregator would
trust IDs with a grain of salt.
* If the IDs of two entries from different feeds are the same **and
the data is the same** show it in only one feed.
* If the
On Apr 18, 2005, at 5:08 PM, fantasai wrote:
xml:space controls whether the parser collapses white space or
not.
False. Parsers are not under any obligation to respect xml:space,
unless they are governed by some other specification that says they
are. -Tim
If the
parser collapses whitespace,
On 19/4/05 12:41 PM, Tim Bray [EMAIL PROTECTED] wrote:
xml:space controls whether the parser collapses white space or
not.
False. Parsers are not under any obligation to respect xml:space,
unless they are governed by some other specification that says they
are. -Tim
some other
14 matches
Mail list logo
