Having said that, I myself prefer to stick to the pure FYN approach and require that only from senders, receivers, consumers. However, that's unfortunately not the most optimal grounds for different scenarios. It is perfectly feasible to lower the barrier for receivers because the "publishers" already have some data on the Web. We want to bring in the possibility where they can simply enrich their existing stuff with minimal amount of work. That may or may not be the headers or the content body. Undoubtedly some will think headers are easier and the others the body. This is not the point to debate about IMO. The thing to acknowledge is that, there are different types of roles in the publishing pipeline. For instance, who is the owner of the resource? Is it only the one that gets to describe it in the body or would the headers count as well? There is nothing written in stone about this anywhere. So, we are definitely not trying to make the call on that either.