Ok thanks a lot Lorenz.

<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon>
Virus-free.
www.avast.com
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

On Mon, Aug 7, 2017 at 10:59 AM, Lorenz Buehmann <
buehm...@informatik.uni-leipzig.de> wrote:

>
>
> On 06.08.2017 13:14, javed khan wrote:
> > **The better way would be to add labels for the resources and search in
> > the labels instead.**
> >
> > By label you mean rdfs:label?  In that case, how it can be searched then
> > when user provide their inputs via UI i-e a text field in my case.?
> Ehm, simply using the FILTER on the label value?!
> >
> > <https://www.avast.com/sig-email?utm_medium=email&utm_
> source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon>
> > Virus-free.
> > www.avast.com
> > <https://www.avast.com/sig-email?utm_medium=email&utm_
> source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link>
> > <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
> >
> > On Sun, Aug 6, 2017 at 1:23 PM, Lorenz B. <
> > buehm...@informatik.uni-leipzig.de> wrote:
> >
> >> Then you have to use a REGEX (or CONTAINS - not sure how you want to
> >> match) in the FILTER and search in the String of the URI
> >>
> >> FILTER(REGEX(STR(?var), "TOKEN"))
> >>
> >>
> >> But in general that's bad practice for sure.
> >>
> >> The better way would be to add labels for the resources and search in
> >> the labels instead.
> >>
> >>> Lorenz yes I know object properties connect resources of two classes
> and
> >> it
> >>> must be URIs..
> >>>
> >>> In our ontology we have object property "hasPublications" which has
> >> domain
> >>> Person and range Publication class (Publication instances can be a
> Book,
> >>> Paper or Article) . Users need to type a person publication by typing
> its
> >>> name in a text box "Cloud computing security"  and we have to find it.
> >>>
> >>> So in that case in order to use it as Filter in query, we need to use
> >> both
> >>> object property and data property like
> >>>
> >>>  Person hasPublications somepublication   and then data property as
> >> string
> >>>  publicationName "String value"
> >>>
> >>> On Sat, Aug 5, 2017 at 10:49 AM, Lorenz B. <
> >>> buehm...@informatik.uni-leipzig.de> wrote:
> >>>
> >>>>> For example, if we have to use filter keyword with a java variable
> >>>> (filter
> >>>>> ?var='javaVariable) in our semantic web application, is it mandatory
> to
> >>>> use
> >>>>> it as "data property" in our ontology and use it as String type?
> >>>> Obviously, but it depends on the content of javaVariable ... you can
> >>>> also compare other datatypes like int, double, etc. and for some you
> >>>> have to provide the datatype explcitely, i.e. "VALUE"^^<DATATYPE_URI>
> >>>> But yes, if it would be an object property you have to use a URI - I
> >>>> hope this is clear, this is very basic Semantic Web knowledge, you
> >>>> should already know that object properties "connect" resources which
> are
> >>>> denoted by URIs.
> >>>>> Like, name as data property in the ontology and then we use in our
> >>>> (SPARQL
> >>>>> Filter) query when a user enter the name in a text box.
> >>>>>
> >>>>> Some time we need some object properties (as string) to use it as
> >> filter
> >>>> in
> >>>>> our queries.
> >>>>>
> >>>>>
> >>>>> <https://www.avast.com/sig-email?utm_medium=email&utm_
> >>>> source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon>
> >>>>> Virus-free.
> >>>>> www.avast.com
> >>>>> <https://www.avast.com/sig-email?utm_medium=email&utm_
> >>>> source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link>
> >>>>> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
> >>>>>
> >>>> --
> >>>> Lorenz Bühmann
> >>>> AKSW group, University of Leipzig
> >>>> Group: http://aksw.org - semantic web research center
> >>>>
> >>>>
> >> --
> >> Lorenz Bühmann
> >> AKSW group, University of Leipzig
> >> Group: http://aksw.org - semantic web research center
> >>
> >>
>
>

Reply via email to