With this, I think it is important to look at both the original intent
of the spec and what clients are most likely to support. While the
schema is non-normative, the fact that atom:name is clearly and
specifically marked as "text" in the schema makes the intent clear. You
*might* be able to stretch really far and claim that escaped HTML is
permitted, but if that was the intent, the spec would more than likely
say so.
If you want the Person construct to contain ruby text, the best approach
would be to define an extension element designed for the purpose of
providing a "display" version of the name, e.g.
<author>
<name>name</name>
<x:display-name>
<ruby xmlns="http://www.w3.org/1999/xhtml";>
<rb>name</rb><rp>(</rp><rt>ruby</rt><rp>)</rp>
</ruby>
</x:display-name>
...
</author>
This would allow existing clients to continue to operate as they always
have.
- James
Brian Smith wrote:
David Powell wrote:
Brian Smith wrote:
If we really need support for Ruby and bidi in <atom:name>,
and we aren't immediately intending to supercede RFC4287, I
think we would be better adding an additional entry/person
metadata element that supports HTML names. But to be honest,
I'd like to see people knocking on our doors before we start
writing drafts to solve potential problems.
I have Japanese users and Japanese language learners that make extensive use of
Ruby markup as an instructional device for teaching Kanji (the complex Japanese
characters).
http://tools.ietf.org/html/rfc4287#section-6.4: Atom allows foreign markup
anywhere in an Atom document, except where it is explicitly forbidden.
http://tools.ietf.org/html/rfc4287#section-3.2.1: The "atom:name" element's content
conveys a human-readable name for the person. The content of atom:name is Language-Sensitive.
Person constructs MUST contain exactly one "atom:name" element.
http://tools.ietf.org/html/rfc4287#section-6.3: Atom Processors that encounter foreign markup in a location that is legal according to this specification MUST NOT stop processing or signal an error.
So, the following is legal already, according to RFC 4287:
<author xmlns='http://www.w3.org/2005/Atom'
xmlns:html='http://www.w3.org/1999/xhtml'>
<name>
<html:span dir='rtl'>foo</html:span>
</name>
</author>
And, I can't find anything that disallows the "type" attribute either:
<author xmlns='http://www.w3.org/2005/Atom'
xmlns:html='http://www.w3.org/1999/xhtml'>
<name type='xhtml'>
<html:span dir='rtl'>foo</html:span>
</name>
</author>
Keep in mind that the Relax NG schema in RFC 4287 is non-normative, and
Appendix B already admits that the schema is too restrictive.
- Brian
