Sign In/My Account | View Cart  
advertisement

Article:
 Handling Atom Text and Content Constructs
Subject: Text is text
Date: 2005-12-08 21:02:24
From: qdn
Response to: Text is text

Yeah, not so much, Uche -- I can't say I agree with your interpretation at all. First, there's really no "spirit" of the spec; the Atom spec is very overt when it explains that text is for literal display of text, and even uses an example that demonstrates that an ampersand-encoded less-than sign should remain as such. Second, your assumption that "unmarked, escaped tags are not meant for human reading" is a bit presumptuous -- they're certainly meant for reading in many given contexts, like in programming, data streams, and the like. One of the largest purposes of Atom -- you can read this over and over in the discussions that happened right out in the open -- is to take away the ambiguity of situations like this by providing explicit types that content providers can specify, and then telling Atom consumers that they must abide by those types if they wish to faithfully represent the content. If a <title> with a type of text has an escaped less-than sign in it, then the Atom consumer must not decode it; anything less is making an assumption that's just plain wrong.

No Previous Message Previous Message Move up to Parent Message Up Next Message Next Message


Titles Only Titles Only Newest First
  • Text is text
    2005-12-08 21:39:29 Uche Ogbuji

    My reply "There is text and there is text and..." above was meant to be in response to the above comment.



Sponsored By: