[Don't merge] Microdata Test #1068
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| var usedTypes = []; | ||
| for (var i=0; i<schemaItems.length; i++) { | ||
| schemaItems[i].itemid = schemaItems[i].getAttribute("itemid") || | ||
| (schemaItems[i].getAttribute("id") ? url+"#"+schemaItems[i].getAttribute("id") : url+"#itemid="+i); |
There was a problem hiding this comment.
This is just to have some (meaningful) itemid also when the attribute is missing. I thought that the fragment identifier might be a good idea to have something which is unique.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The website of the French newspaper Le Figaro uses schema.org as Microdata. While working for a translator for that newspaper I tried to traverse the Microdata and use it. The Microdata on that page does not follow the standards and therefore I ended up to scrape the data with some manually adjusted XPath, see #1067.
However, the Microdata translator here works and maybe a start for some general approach. I added some statements which will output the used types and properties. This can help to see quickly how the Microdata on a page looks like. My impression is that for our purposes only some small subset of the Microdata might be useful at all.
The issue for a microdata translator is here #366.