ISSUE-147: RDFa Processors should preserve markup by default

Preserve markup by default

RDFa Processors should preserve markup by default

State:
CLOSED
Product:
RDFa 1.1 in HTML5
Raised by:
Manu Sporny
Opened on:
2012-12-28
Description:
This issue was raised by Sebastian Heath:

HTML5 and its variants such as XHTML5 provide a rich set of elements that content creators use to indicate many aspects of the texts they are representing. When processing RDF in attributes, the "RDFa 1.1 in HTML5" specification [1] should by default require preservation of all intentional markup. This is good practice. In particular, the working group should not assume that elements in content marked with the @property attribute are there by mistake. Nor should the replication of namespaces in the output be considered garbage.

Full reasoning is here:

http://lists.w3.org/Archives/Public/public-rdfa-wg/2012Dec/0074.html

This issue is being re-opened because of the following statements:

"This is good practice. In particular, the working group should not assume that elements in content marked with the @property attribute are there by mistake. Nor should the replication of namespaces in the output be considered garbage."

The working group should re-examine if:

1) Preservation of markup is good practice for RDFa Processors.
2) The inclusion of HTML markup by authors was not a mistake and the feature is causing problems in RDFa 1.1 based on 6+ months of deployment experience.
3) The replication of namespaces should be considered garbage (I don't think the WG ever said this, and the assertion is most likely due to a mis-communication at some point).
4) Changing the rules at this point would cause an undue burden on authors and implementers due to conflicting rules between RDFa Core and HTML+RDFa.
Related Actions Items:
No related actions
Related emails:
  1. Re: ISSUE-150 (Property Copying in Core): Move the Property Copying feature from HTML+RDFa to RDFa Core [RDFa 1.2+] (from ivan@w3.org on 2013-05-28)
  2. Re: ISSUE-150 (Property Copying in Core): Move the Property Copying feature from HTML+RDFa to RDFa Core [RDFa 1.2+] (from sebastian.heath@gmail.com on 2013-05-28)
  3. Re: ISSUE-150 (Property Copying in Core): Move the Property Copying feature from HTML+RDFa to RDFa Core [RDFa 1.2+] (from ivan@w3.org on 2013-05-28)
  4. Re: ISSUE-150 (Property Copying in Core): Move the Property Copying feature from HTML+RDFa to RDFa Core [RDFa 1.2+] (from sebastian.heath@gmail.com on 2013-05-27)
  5. Telecon Agenda - January 10th 2012, 1500 UTC (from msporny@digitalbazaar.com on 2013-01-10)
  6. Re: ISSUE-147: PROPOSAL for rdfa:defaultDatatype (from sebastian.heath@gmail.com on 2013-01-09)
  7. Re: ISSUE-147: PROPOSAL for rdfa:defaultDatatype (from ivan@w3.org on 2013-01-08)
  8. ISSUE-147: PROPOSAL for rdfa:defaultDatatype (from sebastian.heath@gmail.com on 2013-01-08)
  9. Re: Resolving remaining issues in the issue tracker (from ivan@w3.org on 2013-01-07)
  10. Re: Resolving remaining issues in the issue tracker (from ivan@w3.org on 2013-01-07)
  11. Resolving remaining issues in the issue tracker (from msporny@digitalbazaar.com on 2013-01-06)
  12. Re: ISSUE-147 (preserve markup by default): RDFa Processors should preserve markup by default [RDFa 1.1 in HTML5] (from msporny@digitalbazaar.com on 2012-12-29)
  13. Re: ISSUE-147 (preserve markup by default): RDFa Processors should preserve markup by default [RDFa 1.1 in HTML5] (from gregg@greggkellogg.net on 2012-12-29)
  14. Re: ISSUE-147 (preserve markup by default): RDFa Processors should preserve markup by default [RDFa 1.1 in HTML5] (from ivan@w3.org on 2012-12-29)
  15. Re: ISSUE-147 (preserve markup by default): RDFa Processors should preserve markup by default [RDFa 1.1 in HTML5] (from sebastian.heath@gmail.com on 2012-12-29)
  16. Re: ISSUE-147 (preserve markup by default): RDFa Processors should preserve markup by default [RDFa 1.1 in HTML5] (from ivan@w3.org on 2012-12-29)
  17. Re: ISSUE-147 (preserve markup by default): RDFa Processors should preserve markup by default [RDFa 1.1 in HTML5] (from sebastian.heath@gmail.com on 2012-12-28)
  18. Re: ISSUE-147 (preserve markup by default): RDFa Processors should preserve markup by default [RDFa 1.1 in HTML5] (from sebastian.heath@gmail.com on 2012-12-28)
  19. Re: ISSUE-147 (preserve markup by default): RDFa Processors should preserve markup by default [RDFa 1.1 in HTML5] (from gregg@greggkellogg.net on 2012-12-28)
  20. Re: ISSUE-147 (preserve markup by default): RDFa Processors should preserve markup by default [RDFa 1.1 in HTML5] (from ahby@aptest.com on 2012-12-28)
  21. Re: ISSUE-147 (preserve markup by default): RDFa Processors should preserve markup by default [RDFa 1.1 in HTML5] (from gregg@greggkellogg.net on 2012-12-28)
  22. ISSUE-147 (preserve markup by default): RDFa Processors should preserve markup by default [RDFa 1.1 in HTML5] (from sysbot+tracker@w3.org on 2012-12-28)

Related notes:

After a very long discussion on the topic:

http://www.w3.org/2010/02/rdfa/meetings/2013-01-10#ISSUE__2d_147__3a__Preserve_markup_by_default

No resolution to preserve markup by default carried. The only resolution that did carry was the following:

RESOLVED: Allow RDFa processor authors to add a flag that allows a default datatype for complex markup to be set when invoking the processor.

http://www.w3.org/2010/02/rdfa/meetings/2013-01-10#resolution_1

Manu Sporny, 19 Jan 2013, 17:31:49

Display change log ATOM feed

Chair, Staff Contact
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: 147.html,v 1.1 2015/03/27 14:12:21 vivien Exp $