Open Tpt opened 8 years ago
Thanks @Tpt!
Where in the pipeline do you think such a description would make sense? As output of an API?
Yes, it would be very nice as API output but it also could be used as the documents format inside of Elasticsearch.
Ok, let's keep it in mind for the API!
For Elasticsearch I don't think there would be any benefit. We should optimize for Elasticsearch storage and that will look very different from json-ld.
There is this google tool which extracts more than json-ld : https://search.google.com/structured-data/testing-tool
Some documentation about it : https://developers.google.com/search/docs/guides/enhance-site
I'm not sure if it is relevant but it may be interesting to use json-ld [1] for document description, may be even with the schema.org [2] vocabulary.
For example https://en.wikipedia.org/wiki/Jean-François_Champollion could be represented by (in an amazing future when Common search will be able to guess page topics):
[1] http://json-ld.org [2] http://schema.org