From RDFaWiki

Introduction

The RDFa Task Force was chartered to design an easy method of expressing RDF in XHTML 1.1. It was a joint effort between the Semantic Web Deployment Working Group and the XHTML2 Working Group. While the result was a successful W3C Recommendation in October 2008, there continue to be issues that are raised concerning RDFa that the RDFa Task Force was not chartered to address. Listed below are all of the issues that are out of scope for the current RDFa Task Force charter.

This does not mean that the issues won't be addressed, just that it is not a part of the RDFa Task Force charter. The Task Force cannot officially work on these issues without violating the charter (which is, understandably, a big no-no at the W3C).

Security and Trust

How does one prevent bad triples from corrupting a local triple store?

How can you stop hostile sites from generating nasty triples?

There have been a number of suggestions on how to deal with this issue on the Security and Trust section of this wiki. However, dealing with security and trust issues is part of a much larger movement on the Web. This isn't an RDFa problem, it is a general web problem and must be acknowledged as that. RDFa is no more or less secure than HTML, the mechanism that is used to express information on the Web today.

Persistence and Storage

RDFa was created to express RDF in HTML family languages, but can be used in any structured document with attribute support. The storage model is dependent on the implementation language as well as the consuming application and will vary from use-case to use-case.