- From: Thomas Francart <thomas.francart@sparna.fr>
- Date: Fri, 25 Aug 2017 16:35:57 +0200
- To: Richard Wallis <richard.wallis@dataliberate.com>
- Cc: Karen <karen.cravens@gmail.com>, "schema.org Mailing List" <public-schemaorg@w3.org>
- Message-ID: <CAPugn7Uo9jBSHkJK4q1p9U_mo7zknQUnKDanEVd-rqeU24U_TQ@mail.gmail.com>
2017-08-25 16:17 GMT+02:00 Richard Wallis <richard.wallis@dataliberate.com>: > In an effective Schema.org implemented site all the entities (persons, > organisations, creative works, etc.) will be described and be given their > own identifiers using Schema. The web crawlers should be invited to crawl > all these entity pages on the site > How ? How can the crawler be "invited" to crawl all the entities ? what are the recommended approaches for this ? Thomas > It is in those knowledge graphs that the connections would be made. > > Equally it may well not be in the scope of the dataset describing person > to have the knowledge of the works they may have authored. However in > another dataset (potentially on another site somewhere) describing works, > the only knowledge of the author may be a link to an authority (such as > VIAF, or Wikidata). If that relationship is at least described in one > direction, and both sites have been crawled and loaded into a knowledge > graph, that graph can be used to identify the connections in both > directions as Piero describes. > > So to sum up - if the relationships are all held in a local dataset, > single direction connections are sufficient to support querying in either > direction. If you are dependant on the data being crawled into another > system (knowledge graph) the same is true provided the systems holding both > entity descriptions have ben crawled. > > ~Richard. > > > > Richard Wallis > Founder, Data Liberate > http://dataliberate.com > Linkedin: http://www.linkedin.com/in/richardwallis > Twitter: @rjw > > On 25 August 2017 at 14:19, Karen <karen.cravens@gmail.com> wrote: > >> On Thu, Aug 17, 2017 at 9:37 AM, Piero Savastano < >> piero.savastano@gmail.com> wrote: >> >>> >>> So long story short, instead of thinking about reverse properties, just >>> reverse the query ;) >>> >>> >> The problem, though, is that instead of thinking about a query, I'm >> thinking about the spider that collects the information for the database. >> When all you've found is the Person, no amount of querying will make the >> works show up. >> > > -- *Thomas Francart* -* SPARNA* Web de *données* | Architecture de l'*information* | Accès aux *connaissances* blog : blog.sparna.fr, site : sparna.fr, linkedin : fr.linkedin.com/in/thomasfrancart tel : +33 (0)6.71.11.25.97, skype : francartthomas
Received on Friday, 25 August 2017 14:36:42 UTC