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
I get back only 6 triples, 3 of them just for defining an rdf list for the single Blog element
On the other hand, inspecting the file in Google's testing tool, there are microdata tags for the two BlogPosting items and their contents etc that the parser has missed
is there something I'm missing in my parse statement?
partially related to this, I find if I include the PublicID= mentioned in the help(g.parse) doc, it has no effect in rdfa; not a big issue as the properties can be copied, but is there a trick to overriding the base URI in all parser formats?
This discussion was converted from issue #927 on December 26, 2021 22:21.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I hope I'm using this correctly, but I notice when I issue the following
I get back only 6 triples, 3 of them just for defining an rdf list for the single Blog element
On the other hand, inspecting the file in Google's testing tool, there are microdata tags for the two BlogPosting items and their contents etc that the parser has missed
https://search.google.com/structured-data/testing-tool/u/0/#url=https%3A%2F%2Fblog.teledyn.com
is there something I'm missing in my parse statement?
partially related to this, I find if I include the
PublicID=
mentioned in the help(g.parse) doc, it has no effect in rdfa; not a big issue as the properties can be copied, but is there a trick to overriding the base URI in all parser formats?Beta Was this translation helpful? Give feedback.
All reactions