ISSUE-26: Do we need an error reporting mechanism for RDFa?

Error Reporting Mechanism

Do we need an error reporting mechanism for RDFa?

State:
CLOSED
Product:
RDFa 1.1 Core
Raised by:
Manu Sporny
Opened on:
2010-05-13
Description:
Do we need an error reporting mechanism for RDFa? For instance, when a @profile retrieval fails and a sub-section of a document is not processed, do we need to alert the application that such an error occurred, or should the RDFa Processor carry on quietly? More information here: http://lists.w3.org/Archives/Public/public-rdfa-wg/2010Apr/0189.html on the original @profile issue, the separate discussion on the error mechanism has started in this thread: http://lists.w3.org/Archives/Public/public-rdfa-wg/2010Apr/0192.html
Related Actions Items:
No related actions
Related emails:
  1. RDFa WG telecon minutes for 2010-07-22 (from msporny@digitalbazaar.com on 2010-07-22)
  2. Re: ISSUE-26: We don't need any RDFS vocabulary for error triples! (from ivan@w3.org on 2010-07-22)
  3. Re: ISSUE-26: We don't need any RDFS vocabulary for error triples! (from mark.birbeck@webbackplane.com on 2010-07-22)
  4. Re: ISSUE-26: We don't need any RDFS vocabulary for error triples! (from benjamin.adrian@dfki.de on 2010-07-21)
  5. Re: ISSUE-26: We don't need any RDFS vocabulary for error triples! (from ivan@w3.org on 2010-07-21)
  6. Re: ISSUE-26: We don't need any RDFS vocabulary for error triples! (from benjamin.adrian@dfki.de on 2010-07-21)
  7. Re: ISSUE-26: We don't need any RDFS vocabulary for error triples! (from ivan@w3.org on 2010-07-21)
  8. Telecon Agenda - July 22nd 2010, 1400 UTC (from msporny@digitalbazaar.com on 2010-07-19)
  9. Re: ISSUE-26: We don't need any RDFS vocabulary for error triples! (from benjamin.adrian@dfki.de on 2010-07-19)
  10. RDFa WG telecon minutes for 2010-07-15 (from msporny@digitalbazaar.com on 2010-07-15)
  11. Re: Telecon Agenda - July 15th 2010, 1400 UTC (from benjamin.adrian@dfki.de on 2010-07-15)
  12. Telecon Agenda - July 15th 2010, 1400 UTC (from msporny@digitalbazaar.com on 2010-07-13)
  13. Re: ISSUE-26: RDFa-specific vs. Earl-like Processor Status vocabulary (from ivan@w3.org on 2010-07-08)
  14. Re: ISSUE-26: RDFa-specific vs. Earl-like Processor Status vocabulary (from tai@g5n.co.uk on 2010-07-08)
  15. Re: ISSUE-26: RDFa-specific vs. Earl-like Processor Status vocabulary (from shane@aptest.com on 2010-07-07)
  16. Re: ISSUE-26: RDFa-specific vs. Earl-like Processor Status vocabulary (from ivan@w3.org on 2010-07-07)
  17. Re: ISSUE-26: RDFa-specific vs. Earl-like Processor Status vocabulary (from shane@aptest.com on 2010-07-07)
  18. Re: ISSUE-26: RDFa-specific vs. Earl-like Processor Status vocabulary (from tai@g5n.co.uk on 2010-07-07)
  19. Re: ISSUE-26: RDFa-specific vs. Earl-like Processor Status vocabulary (from msporny@digitalbazaar.com on 2010-07-07)
  20. ISSUE-26: RDFa-specific vs. Earl-like Processor Status vocabulary (from msporny@digitalbazaar.com on 2010-07-07)
  21. Re: On ISSUE-26 : RDFa Error vocabulary (from ivan@w3.org on 2010-07-02)
  22. Re: On ISSUE-26 : RDFa Error vocabulary (from mark.birbeck@webbackplane.com on 2010-07-01)
  23. Re: On ISSUE-26 : RDFa Error vocabulary (from mark.birbeck@webbackplane.com on 2010-07-01)
  24. RDFa WG telecon minutes for 2010-07-01 (from msporny@digitalbazaar.com on 2010-07-01)
  25. Re: On ISSUE-26 : RDFa Error vocabulary (from shane@aptest.com on 2010-07-01)
  26. Re: On ISSUE-26 : RDFa Error vocabulary (from ivan@w3.org on 2010-07-01)
  27. Re: Telecon Agenda - July 1st 2010, 1400 UTC (from mark.birbeck@webbackplane.com on 2010-07-01)
  28. Re: Telecon Agenda - July 1st 2010, 1400 UTC (from benjamin.adrian@dfki.de on 2010-07-01)
  29. Re: On ISSUE-26 : RDFa Error vocabulary (from mark.birbeck@webbackplane.com on 2010-06-30)
  30. Re: On ISSUE-26 : RDFa Error vocabulary (from ivan@w3.org on 2010-06-30)
  31. Re: On ISSUE-26 : RDFa Error vocabulary (from mark.birbeck@webbackplane.com on 2010-06-30)
  32. On ISSUE-26 : RDFa Error vocabulary (from ivan@w3.org on 2010-06-30)
  33. Telecon Agenda - July 1st 2010, 1400 UTC (from msporny@digitalbazaar.com on 2010-06-28)
  34. RDFa WG telecon minutes for 2010-06-24 (from msporny@digitalbazaar.com on 2010-06-24)
  35. Re: Telecon Agenda - June 24th 2010, 1400 UTC (from mark.birbeck@webbackplane.com on 2010-06-24)
  36. Telecon Agenda - June 24th 2010, 1400 UTC (from msporny@digitalbazaar.com on 2010-06-24)
  37. Re: on the error mechanism (from ivan@w3.org on 2010-06-21)
  38. Re: Telecon Agenda - June 17th 2010, 1400 UTC (from knud.moeller@deri.org on 2010-06-16)
  39. Re: Telecon Agenda - June 17th 2010, 1400 UTC (from ivan@w3.org on 2010-06-14)
  40. Telecon Agenda - June 17th 2010, 1400 UTC (from msporny@digitalbazaar.com on 2010-06-13)
  41. Re: Telecon Agenda - June 10th 2010, 1400 UTC (from mark.birbeck@webbackplane.com on 2010-06-10)
  42. Re: Telecon Agenda - June 10th 2010, 1400 UTC (from shane@aptest.com on 2010-06-09)
  43. Telecon Agenda - June 10th 2010, 1400 UTC (from msporny@digitalbazaar.com on 2010-06-09)
  44. Re: Telecon Agenda - June 3rd 2010, 1400 UTC (from knud.moeller@deri.org on 2010-06-03)
  45. Telecon Agenda - June 3rd 2010, 1400 UTC (from msporny@digitalbazaar.com on 2010-06-01)
  46. for the telecon: on ISSUE-26 (error reporting mechanism) (from ivan@w3.org on 2010-05-27)
  47. Telecon Agenda - 27th May 2010, 1400 UTC (from msporny@digitalbazaar.com on 2010-05-24)
  48. ISSUE-26 (Error Reporting Mechanism): Do we need an error reporting mechanism for RDFa? [RDFa 1.1 Core] (from sysbot+tracker@w3.org on 2010-05-13)

Related notes:

RESOLVED: RDFa should have an warning and error reporting mechanism.

http://www.w3.org/2010/02/rdfa/meetings/2010-06-17#resolution_1

Manu Sporny, 17 Jun 2010, 15:31:15

RESOLVED: Accept RDFa Core Error reporting mechanism per the proposal sent to the mailing list, clarify the default mode of operation.

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

RESOLVED: Accept RDFa API Error reporting mechanism per the proposal sent to the mailing list, clarify that both Event-based and Model-based mechanisms MUST be supported.

http://www.w3.org/2010/02/rdfa/meetings/2010-07-01#resolution_2

Manu Sporny, 5 Jul 2010, 03:31:04

RESOLVED: RDFa should have an warning and error reporting mechanism.

http://www.w3.org/2010/02/rdfa/meetings/2010-06-17#resolution_1

Manu Sporny, 5 Jul 2010, 03:32:19

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: 26.html,v 1.1 2015/03/27 14:12:22 vivien Exp $