ISSUE-115

Last Call Comment: issues with @content

State:
CLOSED
Product:
RDFa
Raised by:
Ben Adida
Opened on:
2008-04-03
Description:
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
Related emails:
  1. ISSUE-115: Last Call Comment: issues with @content (from dean+cgi@w3.org on 2008-04-03)
  2. meeting record: 2008-05-01 RDFa telecon (from swick@w3.org on 2008-05-01)

Related notes:

2008-05-08: RESOLVED by adding a short non-normative paragraph approximately as follows "Note that the use of @content prohibits the inclusion of rich markup in your content. If the inline content of an element is what you are trying to convey, then documents should rely upon that rather than duplicating that content using the @content attribute." in telecon http://www.w3.org/2008/05/01-rdfa-minutes.html

2008-06-12: ACTION: Accept

2008-06-12: CHANGE-TYPE: Editorial

2008-06-12: RESOLUTION: added a short non-normative paragraph approximately as follows "Note that the use of @content prohibits the inclusion of rich markup in your content. If the inline content of an element is what you are trying to convey, then documents should rely upon that rather than duplicating that content using the @content attribute."

2008-06-12: PFWG responded that they can live with this resolution: http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2008May/0164.html

2008-06-12: COMMENTER-RESPONSE: can live with it