-
Notifications
You must be signed in to change notification settings - Fork 822
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
schema org applied to visualisations: proper markup and valid workaround to describe dynamic charts #979
Comments
This is not an area that has had much attention / discussion. I know that SVG historically supported inline metadata, but I don't know much about how that has been used in practice. Do you have any overview or data on the current conventions, issues, needs etc? |
Yes I would like to understand a best practice to describe content in a page structures like:
Each topic, or entity, carries its own visualisation that display its context. 1# Need
2# Tech Issues:
As example for the picture above, something like:
This snippet could be provided server side in the html page, avoiding possible issues for indexing ajax. So far any entity I display could point to wikipedia or other websites, I wonder if it is good practice or could be considered as a "copy" by a search engine and penalise the site. 3# Creating an ItemID for each visualisation? In https://bib.schema.org/Atlas and itemID is used to point to a book.
|
This issue is being tagged as Stale due to inactivity. |
Hello,
I read maps, charts, plates or tables, physical or in media form illustrating any subject.
Is it a proper descriptor for objects representing "knowledge maps" and "references" and other media?
If not, which?
E.g. in this example http://bib.schema.org/Atlas the snipper show a book, I would like to create an ID for my own object
The idea is to provide a description which can be read from bots, while the objective of the description would be explained by the visualisation (that is, the user have a "visual" description of elements in SVG rather than "textual of elements for bots").
The text was updated successfully, but these errors were encountered: