Make sure you are pulling from the *development* branch! -- Master is in a bad state until our upcoming first release. david.
On Fri, Jun 10, 2016 at 12:40 PM, David Lotts <[email protected]> wrote: > What error/response are you getting? > > I did this, should be equivalent to your query: > > > http://192.168.33.10:8080/web.rya/queryrdf?query.infer=&query.auth=&query.resultformat=xml&padding=&query=PREFIX+d%3A+%3Chttp%3A%2F%2Flearningsparql.com%2Fns%2Fdata%23%3E%0D%0Aselect+*+where+{+d%3A0432+%3Fpredicate+%3Fobject+.+} > <http://192.168.33.10:8080/web.rya/queryrdf?query.infer=&query.auth=&query.resultformat=xml&padding=&query=PREFIX+d%3A+%3Chttp%3A%2F%2Flearningsparql.com%2Fns%2Fdata%23%3E%0D%0Aselect+*+where+%7B+d%3A0432+%3Fpredicate+%3Fobject+.+%7D> > > Works fine for me. > > Here is what I get, nothing was matched as I expected: > > <?xml version='1.0' encoding='UTF-8'?><sparql > xmlns='http://www.w3.org/2005/sparql-results#'> <head> <variable > name='predicate'/> <variable name='object'/> </head> > <results> </results></sparql> > > > david. > > On Fri, Jun 10, 2016 at 10:42 AM, Puja Valiyil <[email protected]> wrote: > >> I didn't know of this limitation -- I have successfully used this in the >> past. How are you issuing the query -- through the jsp site that comes >> with rya or through a browser call or programmatically? >> >> On Fri, Jun 10, 2016 at 9:42 AM, Ly, Kiet <[email protected]> wrote: >> >> > http://10.162.96.77:8000/web.rya/queryrdf?query=PREFIX d: < >> > http://learningsparql.com/ns/data#>\n select * where { d:0432 >> ?predicate >> > ?object . } >> > >> > It seems I can’t use prefix in REST call. Is this the limitation? It >> works >> > in blazegraph. >> > >> > >> > Confidentiality Notice:: This email, including attachments, may include >> > non-public, proprietary, confidential or legally privileged information. >> > If you are not an intended recipient or an authorized agent of an >> intended >> > recipient, you are hereby notified that any dissemination, distribution >> or >> > copying of the information contained in or transmitted with this e-mail >> is >> > unauthorized and strictly prohibited. If you have received this email >> in >> > error, please notify the sender by replying to this message and >> permanently >> > delete this e-mail, its attachments, and any copies of it immediately. >> You >> > should not retain, copy or use this e-mail or any attachment for any >> > purpose, nor disclose all or any part of the contents to any other >> person. >> > Thank you. >> > >> > >
