I noticed this also; in Abdera we simply ignore it and treat all child
elements of atom:category and atom:link the same, regardless of namespace.
- James
Bill de hOra wrote:
Looking for a refresher on RFC4287 atom:category child constaints. Is it
by design that atom:category cannot contain atom:* child markup? The
spec text says nothing about restricting children of atom:category to
non Atom markup, but here's the RNC says its illegal:
atomCategory =
element atom:category {
atomCommonAttributes,
attribute term { text },
attribute scheme { atomUri }?,
attribute label { text }?,
undefinedContent
}
undefinedContent = (text|anyForeignElement)*
anyForeignElement =
element * - atom:* {
(attribute * { text }
| text
| anyElement)*
}
The feedvalidator follows the RNC and marks this construct as an error
<category term='holidays' label='Holidays'>
<link rel='alternate' type='application/atom+xml'
href='https://example.org/dehora/categories/holidays' />
</category>
Why - it would be nice to supply a feed link for a category, and not do
weird things with the scheme/term attributes. And I note that atom:link
has the same restriction in the RNC.
Bill
