Because in SPARQL there is always only a single resource bound to a variable, in your case ?member and not the whole list
On 18.05.2017 12:18, Bardo Nelgen wrote: > > Hi all, > > why does the CONSTRUCT SPARQL of > >> PREFIX rdf:<http://www.w3.org/1999/02/22-rdf-syntax-ns#> >> PREFIX xsd:<http://www.w3.org/2001/XMLSchema#> >> PREFIX as:<https://www.w3.org/ns/activitystreams#> >> PREFIX list: <http://jena.hpl.hp.com/ARQ/list#> >> >> CONSTRUCT {<http://resources.semaworx.eu/activity/user/BNNuserPAR> >> as:items ( ?members ) .} >> >> WHERE{<http://resources.semaworx.eu/activity/user/BNNuserPAR> >> as:items [ list:member ?members ] .} > produce > >> <rdf:Description >> rdf:about="http://resources.semaworx.eu/activity/user/BNNuserPAR";> >> <as:items rdf:parseType="Collection"> >> <rdf:Description >> rdf:about="http://resources.semaworx.eu/activity/user/BNNuserPAR/SHA512UIDdateUID004"/> >> </as:items> >> <as:items rdf:parseType="Collection"> >> <rdf:Description >> rdf:about="http://resources.semaworx.eu/activity/user/BNNuserPAR/SHA512UIDdateUID003"/> >> </as:items> >> <as:items rdf:parseType="Collection"> >> <rdf:Description >> rdf:about="http://resources.semaworx.eu/activity/user/BNNuserPAR/SHA512UIDdateUID002"/> >> </as:items> >> <as:items rdf:parseType="Collection"> >> <rdf:Description >> rdf:about="http://resources.semaworx.eu/activity/user/BNNuserPAR/SHA512UIDdateUID001"/> >> </as:items> >> </rdf:Description> > rather than > >> <rdf:Description >> rdf:about="http://resources.semaworx.eu/activity/user/BNNuserPAR";> >> <as:items rdf:parseType="Collection"> >> <rdf:Description >> rdf:about="http://resources.semaworx.eu/activity/user/BNNuserPAR/SHA512UIDdateUID004"/> >> <rdf:Description >> rdf:about="http://resources.semaworx.eu/activity/user/BNNuserPAR/SHA512UIDdateUID003"/> >> <rdf:Description >> rdf:about="http://resources.semaworx.eu/activity/user/BNNuserPAR/SHA512UIDdateUID002"/> >> <rdf:Description >> rdf:about="http://resources.semaworx.eu/activity/user/BNNuserPAR/SHA512UIDdateUID001"/> >> </as:items> >> </rdf:Description> > ?? > > It’s obviously not the same and caused by the iteration over the query > results. > > But how could I prevent it from happening without having to create a > separate query for the construction ? > > As always, input and references are highly appreciated. > > Regards, > > Bardo > >
