ISSUE-115: Last Call Comment: issues with @content

ISSUE-115: Last Call Comment: issues with @content

http://www.w3.org/2006/07/SWD/track/issues/115

Raised by: Ben Adida
On product: RDFa

raised by PFWG in [1]

"""
2.2 Issues with @content (section 6.3.1.1)

@content may be used to indicate a plain literal which would overwrite the
element content for RDF generation purposes.


(a) What is the rationale for having the @content value replace the element
content in terms of RDF statements?  Why not make the @content value an
alternative object in the statement (with the element content being the other
alternative object)?  - This would give the end user the option to choose
between the two alternatives.


(b) The use of @content bears the drawback that its value cannot be marked up. 
The most prominent need for markup of text for assistive technology is the
indication of language.  The spec addresses this issue (section 6.3.1.1.1) by
making a sibling @xml:lang reign over @content.  However, this does not solve
the problem of language changes inside the @content value (foreign words).   We
propose to add a note that warns about the drawback of @content with regard to
marking up foreign words within its value, and recommend using the (marked-up)
element content instead of @content, wherever possible.
"""

[1] http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2008Apr/0031.html

Received on Thursday, 3 April 2008 17:14:42 UTC