Hello Lorenz, I have read these plus some other too. I read the following
query but already we have Steve Jobs nationality on DBpedia, why we needed
Construct query here. We could easily get this data using Select:
dbr:Steve_Jobs dbp:nationality ?nationality
Why we need Construct query here.
CONSTRUCT {
<http://dbpedia.org/resource/Steve_Jobs> <
http://dbpedia.org/property/nationality> ?nationality.
}
WHERE{
<http://dbpedia.org/resource/Steve_Jobs> <
http://dbpedia.org/property/nationality> ?nationality.
On Sun, Jun 25, 2017 at 2:36 PM, Lorenz B. <
buehm...@informatik.uni-leipzig.de> wrote:
> As always, read the SPARQL 1.1 documentation [1]
>
> And to answer it, it generates exactly the data that you define in the
> first part of the CONSTRUCT query such that if there are variables those
> are bound in the WHERE part.
>
> [1] https://www.w3.org/TR/sparql11-query/#construct
> > Hi
> >
> > How a SPARQL construct query works? How it generate data which is not
> > existed in our ontologies? Is it just create the instances of classes
> which
> > does not exist?
> >
> > A simple example will be appreciated as I am reading literature about it
> > from past few days but could not understand how exactly it works.
> >
> > Warm regards
> >
> --
> Lorenz Bühmann
> AKSW group, University of Leipzig
> Group: http://aksw.org - semantic web research center
>
>
