w3c / w3c/adapt

RDFa annotates pages not elements

Open
#53 1 comment 0 reactions 1 assignee View on GitHub

@michael-n-cooper is already working on this.

Since Mar 12, 2018.

implementation
Dominant language
JavaScript
Stars
53
Forks
17
PR merge metrics
No merged PRs in 30d

Description

I recently submitted a pull request #50 to describe how to use the personalization semantics vocabulary in HTML Microdata and RDFa. I have since been told by a RDFa expert that RDFa does not add semantics to the element it is used on; instead, it describes how to use content from that element to add semantics to the page as a whole. This would mean that RDFa would not be a useful metadata language for most of the use cases we have for personalization semantics. I still need to learn more about this but wanted to log an issue.

If RDFa only annotates the page as a whole, then we should explore if there are features of personalization semantics for which that is useful. My guess would be that personalization at a page level would be a different kind of module from the others, and we might say RDFa could be used only for that module. This is likely to benefit use cases that impact search engines (e.g., pointers to alternate versions of content and the nature of the alternative) rather than direct user experience in user agents.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.