You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 11, 2019. It is now read-only.
For e.g. serious internationalisation microdata has some pretty fundamental issues - see e.g. #21, #22. It is possible to work around most of these by converting to another format. Since most tools seem to work with both, instead of trying to rewrite microdata which would make it more complex, I think we should just suggest that people use RDFa or JSON-LD if they need their capabilities.
fix#52
WARNING! This may not be complete or accurate.
haven't looked at whether we really need data typing for e.g.
date/times. We *seem* not to need it for URLs...
My understanding is that the Google parsers should currently handle Microdata's itemref, but not RDFa 1.1's rdfa:Pattern property-copying. Is that consistent with what you're seeing?
For e.g. serious internationalisation microdata has some pretty fundamental issues - see e.g. #21, #22. It is possible to work around most of these by converting to another format. Since most tools seem to work with both, instead of trying to rewrite microdata which would make it more complex, I think we should just suggest that people use RDFa or JSON-LD if they need their capabilities.
See also #3, #29
The text was updated successfully, but these errors were encountered: