Author: burton Date: Sat Jan 29 16:29:14 2005 New Revision: 149086 URL: http://svn.apache.org/viewcvs?view=rev&rev=149086 Log: more dox WRT MUST and MUST NOT handling within atom Modified: jakarta/commons/sandbox/feedparser/trunk/xdocs/index.xml
Modified: jakarta/commons/sandbox/feedparser/trunk/xdocs/index.xml Url: http://svn.apache.org/viewcvs/jakarta/commons/sandbox/feedparser/trunk/xdocs/index.xml?view=diff&rev=149086&p1=jakarta/commons/sandbox/feedparser/trunk/xdocs/index.xml&r1=149085&p2=jakarta/commons/sandbox/feedparser/trunk/xdocs/index.xml&r2=149086 ============================================================================== --- jakarta/commons/sandbox/feedparser/trunk/xdocs/index.xml (original) +++ jakarta/commons/sandbox/feedparser/trunk/xdocs/index.xml Sat Jan 29 16:29:14 2005 @@ -202,6 +202,37 @@ </section> --> + <section name="Strict Specification Conformance"> + + <p> + Currently the FeedParser does NOT require that XML feeds meet + RSS and Atom specifications to the letter. While this is part + of liberal feed parsing in general there are secions of the Atom + specification for example which MUST have child elements. + </p> + + <p> + For example: + + <q>atom:entry elements MUST contain exactly one atom:id element.</q> + </p> + + <p> + We try to follow Postel's law here and require allow feeds to + pass in this situation. We may adopt a policy in the future for + both strict XML parsing and strict format compliance which would + trigger exception in the event of a feed not exactly matching + the specification. + </p> + + <p> + In practice if your application requires data from a feed you + need to assert within your code that you have all correct data + before moving forward. + </p> + + </section> + <section name="Future Directions"> <p> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
