as a Live Bookmark in Firefox.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
as
it should be. They don’t even throw crappy aggregators a bone
by duplicated the bookmark as a link in the content, which is
just as well.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
of the item?
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
of the same resource that this Atom Document
represents.”
Which option is correct should be pretty clear from that.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
?
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
you can dispatch on because the
vocabulary in question is not in a namespace.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
in the document order.
That will lead to silent data loss if the content is malformed
such that it contains an extraneous `/div`.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
, so
putting such elements in the content will usually fail to achieve
what you wanted – hence the SHOULD.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
is intended for limited
amounts of inline content that can be rendered in menus, lists
and the like, not for substantive amounts of content.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
will have to keep doing what you’re already doing with
`type=html` containing `pre` tags.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
. The track name, album and artist are data;
they should be part of the payload of an entry, not part of its
envelope. In practice, that means you use either microformats or
a more structured format than HTML. Extending the Atom envelope
is a strategy of last resort.
Regards,
--
Aristotle Pagaltzis
be used.
(Note: Just because ;type=entry is used DOES NOT imply that
;type=feed must also be used)
+1
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
rel=stylesheet href=/style.css /
And what with this?
link rel=stylesheet type=text/plain href=/style.css /
Is their behaviour right? Wrong? Why?
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
* Franklin Tse [EMAIL PROTECTED] [2006-12-07 10:00]:
If browsers do not support text/plain as a stylesheet, they
should just simply ignore link rel=stylesheet
type=text/plain href=/style.css /.
Exactly.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
Feed Document to a Collection
using the application/atom+xml media type is undefined.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
,
--
Aristotle Pagaltzis // http://plasmasturm.org/
in the future,
eg. to track changes to a document. However, that’s still an
entirely different use case from subscribing to feed.]
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
,
--
Aristotle Pagaltzis // http://plasmasturm.org/
in the hopes of derailing
a discussion?
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
element there. And praise to mnot, who
suggested we do this in RFC4287 but was overruled by the WG
(including myself).
+1
(Wow, I +1ed both James and Robert in the same mail. :-) )
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
about what error status codes to
use in which circumstances could also help unify expectations.
But the scope of any such endeavour will be huge…
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
that.
Don’t you have any identifying information about who is POSTing
the entry? That’s where I’d look to.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
could discuss whether these ideas would have been worthwhile.
However, this is moot, as the spec is done and cannot be changed.
Since these suggestions are incompatible with RFC 4287, they
cannot be recommended as best practices either. Sorry. :-(
Regards,
--
Aristotle Pagaltzis // http
Does xml:base and xml:lang apply to html encoded content?
Yes, definitely.
--
GMX DSL-Flatrate 0,- Euro* - Überall, wo DSL verfügbar ist!
NEU: Jetzt bis zu 16.000 kBit/s! http://www.gmx.net/de/go/dsl
, that’s fine, and more power to you.
But nothing like that is mandated, much less is any approach for
deriving a dereferencable URI for a single term.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
think) this spec aims for.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
the atom:content as instances
of an independent XML vocabulary. The latter seems favourable,
but again I don’t know whether any of this is really a good idea.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
Pagaltzis // http://plasmasturm.org/
* Bill de hOra [EMAIL PROTECTED] [2006-10-04 03:55]:
A. Pagaltzis wrote:
I think given the above background you'll agree that the
intent of the document is pretty coherent.
I couldn't tell whether new Atom extensions are foreign markup,
or something else to be dealt with under wrt being
* Elliotte Harold [EMAIL PROTECTED] [2006-10-02 16:40]:
It would essentially rule out using DOM to process this stuff,
for example.
OK, sold. I hadn’t thought of that.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
undoubtedly be helpful, though.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
to relicense it.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
* James Holderness [EMAIL PROTECTED] [2006-09-01 01:30]:
Encouraging people to use xhtml when they don't know enough to
have made that decision themselves is just asking for trouble.
+1
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
feeds for all the comments
on each separate post. We’ve also added support for the RSS
2.0 and Atom 1.0 standards.
That makes what, another few dozen million Atom 1.0 feeds?
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
* Antone Roundy [EMAIL PROTECTED] [2006-07-26 16:45]:
Or you put the whole thing in a CDATA block.
Which is the easiest option, so long as you remember the edge
case of having to turn any `]]` sequences in the input into
`gt;![CDATA[`.
Regards,
--
Aristotle Pagaltzis // http
nbsp must be escaped.
But he did say “escaping and ”, so it would be. I’m not sure
what Bill’s question even is.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
`relation` elements have and what do they mean?
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
extensions. Doesn’t that cover your use case? Do you
actually need to extend the functionality of the syndication
format?
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
to
child elements of the div.
How is that any different from having to find ways to pass any
in-scope xml:lang/xml:base down to API clients when the content
is type=html or type=text? I hope you didn’t punt on those?
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
* James M Snell [EMAIL PROTECTED] [2006-06-28 20:00]:
A. Pagaltzis wrote:
* James M Snell [EMAIL PROTECTED] [2006-06-28 14:35]:
Hiding the div completely from users of Abdera would mean
potentially losing important data (e.g. the div may contain
an xml:lang or xml:base) or forcing me
and base
URL context. You need to communicate those anyway in the case
they are inherited from higher up in the document tree.
Exactly.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
to avoid such a mistake should be reasonably
easy by naming the methods appropriately, ie something like
`get_container_content` and `get_container_base` vs `get_content`
and `get_base`. (That the first pair of names is so long is fully
intentional… :-) )
Regards,
--
Aristotle Pagaltzis // http
='http://www.example.org/cat/Technology/Coding/Java/'
label='Java'
/
category
scheme='http://www.exmple.org/'
term='http://www.example.org/cat/Technology/Sun/Java/'
label='Java'
/
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
are intent on violating them.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
* Sylvain Hellegouarch [EMAIL PROTECTED] [2006-06-07 20:20]:
/me wonders how long before a wiki engine based on Atom :)
You mean http://www.xml.com/pub/a/2004/04/14/atomwiki.html? :)
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
relevant functionality.
I have no further commentary to offer.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
preferences are equally wise.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
then need to “solve” in the first place.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
Hi Robert,
* Robert Sayre [EMAIL PROTECTED] [2006-05-31 19:35]:
On 5/31/06, A. Pagaltzis [EMAIL PROTECTED] wrote:
My interpretation of these facts is that string comparison is
explicitly expected.
Incorrect.
I don’t see how, although I can see how what I wrote might be
ambiguous
* Robert Sayre [EMAIL PROTECTED] [2006-05-31 19:55]:
On 5/31/06, A. Pagaltzis [EMAIL PROTECTED] wrote:
If you hadn't dropped an asinine jab at him into a completely
unrelated thread you might not have created the problem that
you would then need to solve in the first place.
Actually, those
* Robert Sayre [EMAIL PROTECTED] [2006-05-31 20:25]:
On 5/31/06, A. Pagaltzis [EMAIL PROTECTED] wrote:
My interpretation of these facts is that string comparison
is explicitly expected.
If it was explicit, you wouldn't need to interpret.
Okay, more imprecise wording. Make
* Martin Duerst [EMAIL PROTECTED] [2006-05-30 08:00]:
The conclusion is that a content producer that uses
HTTP://www.IANA.org:80/assignments/relation/alternate at all
does something wrong.
+1
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
would have made RFC 4287 a better spec.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
be used as a valid atom:id value and so long as the
href attribute is also specified.
It would improve interop if multiple disparate publishers
publishing a response to the same resource were led to pick the
same identifier, so I suggest changing this MAY to SHOULD.
Regards,
--
Aristotle Pagaltzis
* James M Snell [EMAIL PROTECTED] [2006-05-20 06:40]:
A. Pagaltzis wrote:
I’d still like thr:when called thr:updated, as it follows the
same semantics as atom:updated and its value is of the same
type.
I'm still stewing over this and haven't quite made up my mind
on it yet. The only
, and we know the problems that this poses in
practice. Extending Atom in ways other than those defined in Sec
6.4. has the same problems as extending RSS 2.0 with namespaced
elements.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
there.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
to retrieve the out-of-band metadata.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
put this metadata out of band, then the
application layer has to take on infrastructure layer
responsibilities.
Note that I’m not arguing against the approach. It seems like an
interesting idea. I’m just pointing out that it does have costs.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
I don’t see why it should not work,
so I find your thought experiment quite amusing.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
or, to borrow
Tim’s turn of phrase, a molehill.
If it works out, just reissue it; if not, there’s room to go back
and fix it.
Sounds reasonable enough to me.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
describe.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
covers nearly
every threading use cases without having to resort to a gaggle of
other extensions and hence weaken FTE’s position, IMO.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
a favour by omitting your interpretation of the
matter as vendor politics.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
* Robert Sayre [EMAIL PROTECTED] [2006-05-16 04:45]:
[…]
+1
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
– cause if
there is, what else would that mean than that we did a shoddy
job? :-)
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
elements in Section 6.4 should have
included atom:link.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
* Tim Bray [EMAIL PROTECTED] [2006-05-05 03:50]:
If it turns out to be useful, it'll stick. Otherwise not.
No doubt; but then why did we need so much verbiage in Sec. 6.4.
and subsections anyway?
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
link, and no
way to indicate a global reply count is available?
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
* Robert Sayre [EMAIL PROTECTED] [2006-05-02 05:25]:
On 5/1/06, A. Pagaltzis [EMAIL PROTECTED] wrote:
* Robert Sayre [EMAIL PROTECTED] [2006-05-02 03:50]:
especially when changes requested by the community are met
with hostility and channel flooding.
Did this happen in more cases than
for
reasons we’ve already been over.
Will have to read this revision and think about it.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
* James M Snell [EMAIL PROTECTED] [2006-05-02 19:45]:
A. Pagaltzis wrote:
Such as?
Aristotle, I appreciate the intention, but please don't bother.
It is painfully clear that Robert has no intention of adding
anything of any real value to the discussion.
I know. However, I despise
the most
precise way to clarify its flaws. It wasn’t until David gave his
criticism that I saw any serious problem.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
* James M Snell [EMAIL PROTECTED] [2006-05-02 22:25]:
A. Pagaltzis wrote:
I have to say that your architecture sounds rather
heavyweight,
Heavyweight? It's Java. need I say more?
Hehe. I stopped just short of asking “is that in Java?” :-)
Does your implementation properly handle
to declare this madness and
refuse to support it.
Maybe we need something like _A Plea for Sanity_ that Joe English
wrote about namespaces, for xml:base.
The draft should specify character-by-character comparison of
the resolved URI's.
Yeah, probably.
Regards,
--
Aristotle Pagaltzis // http
,
--
Aristotle Pagaltzis // http://plasmasturm.org/
?
for that excludes the IETF from defining the problem.
How do you mean? (Question to be taken at face value. I honestly
am not sure what you mean here.)
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
be an ideal place to get this done within a
short timeframe, provided a mob got together.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
to
increase the chance of good implementations? Where are those who
participated in the interminable flamewars brought on by every
rathole that lay on the way to RFC4287? Have they stopped caring
now, or was all that vitriol just bikeshed painting after all?
Regards,
--
Aristotle Pagaltzis // http
out.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
that there be some pressure for the
old approach to die quickly before it gets implemented in enough
venues for the Atom 0.3 Effect to set in.
I understand why you want it, though.
-0.5, I suppose?
I don’t know what to say about this.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
)
Isn’t that what the `type` attribute is for?
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
best practice pattern for
Atom extensions:
Trying to extend `atom:link` is bad. If you need more
semantics than afforded to it by RFC 4287, you should
clone it and tweak the copy.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
possible approach to this issue?
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
the parts
they find convenient or useful.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
such as Atom,
you'd expect xml:base in the envelope to set the base-URI for
the content.
To be honest, I’m not sure about the precise spec interactions
for this case. What I do know however is that Gecko respects
xml:base in XHTML content.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
feed.
If you do this, any xml:base attributes within the copy of the
atom:entry will continue to resolve correctly.
It’s much easier to get right than copying markup without
violating namespace-wellformedness, even.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
tested at all. It makes me nervous that dirty data
based on current incomplete implementation behaviour may become
too widespread for aggregator developers to be able to ignore it.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
the main wiki, as before. Collaboration is the point.
I’m hoping for a way for anyone to pitch in without having to
fight any red tape, so that the test suite can be expanded by
whoever happens to have a spare tuit.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
.
How does ?action=atomtest sound?
Maybe `action=atom`?
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
fixup needs to be done on the
content from the Atom feed so it can be passed to a tag soup
renderer.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
those on either end of the wire.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
cruel parents), not Bertrand Café.
or should I be using the unicode numeric entity instead?
Yes. Or use a literal é as you did in this mail, provided you
emit the feed as UTF-8 (or ISO-8859-1, if you must).
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
Pagaltzis // http://plasmasturm.org/
Pagaltzis // http://plasmasturm.org/
,
--
Aristotle Pagaltzis // http://plasmasturm.org/
1 - 100 of 325 matches
Mail list logo
