Open danbri opened 4 years ago
Given that this is a little drafty, I will file it in the brainstorming repo for now.
We (Google) have both an opensource proof-of-concept demo (parsing using https://github.com/google/schemarama) ready to share, and other signs of implementation seriousness, so I will move this back into the main repository.
This issue is being tagged as Stale due to inactivity.
Given that Dublin Core has dct:tableOfContents, would it be possible to extend the scope of tocEntry to cover gereric CreativeWork, and maybe to allow textual value?
I'm now implementing a large bibliographic database with schema.org vocab. While table of contens go to schema:description with leading label "目次:" (table of contents:) on the initial stage, some user comments suggested that a dedicated property for the toc would be more useful for the data consumption.
Sounds like a good idea! And your database sounds interesting too - will it be public?
On Thu, 8 Dec 2022 at 01:17, KANZAKI, Masahide @.***> wrote:
Given that Dublin Core has dct:tableOfContents, would it be possible to extend the scope of tocEntry to cover gereric CreativeWork, and maybe to allow textual value?
I'm now implementing a large bibliographic database with schema.org vocab. While table of contens go to schema:description with leading label "目次:" (table of contents:) on the initial stage, some user comments suggested that a dedicated property for the toc would be more useful for the data consumption.
— Reply to this email directly, view it on GitHub https://github.com/schemaorg/schemaorg/issues/2766#issuecomment-1341837104, or unsubscribe https://github.com/notifications/unsubscribe-auth/AABJSGKNN47ASE22E3EDFGTWMEZK3ANCNFSM4TYJW4VQ . You are receiving this because you authored the thread.Message ID: @.***>
Thanks! Yes, it will be public next spring :)
I found it a bit disappointing that Schema.org v17 did not extend the scope of tocEntry. What steps are necessary to make progress? Here is an implementation example from the database mentioned above: https://ld.webcatplus.jp/snorql/?describe=https%3A%2F%2Fld.webcatplus.jp%2Fdata%2F169876
Let’s fix that!
On Sun, 28 May 2023 at 14:54, KANZAKI, Masahide @.***> wrote:
I found it a bit disappointing that Schema.org v17 did not extend the scope of tocEntry. What steps are necessary to make progress? Here is an implementation example from the database mentioned above:
https://ld.webcatplus.jp/snorql/?describe=https%3A%2F%2Fld.webcatplus.jp%2Fdata%2F169876
— Reply to this email directly, view it on GitHub https://github.com/schemaorg/schemaorg/issues/2766#issuecomment-1566149079, or unsubscribe https://github.com/notifications/unsubscribe-auth/AABJSGJL7UEHJKUGRU33PETXINKJXANCNFSM4TYJW4VQ . You are receiving this because you authored the thread.Message ID: @.***>
This issue is being nudged due to inactivity.
This is a proposal from Google to make it easier (e.g. in a voice assistant context) to navigate within audio and video content, providing a kind of "table of contents" with cues and links.
Example:
This would involve:
There are a few details left to work through but I wanted to surface our thinking here for discussion.
Related vocabulary includes Clip, PodcastEpisode, .