bigdata-developers

[Bigdata-developers] InlineURIFactory change

[Stas M. <sma...@wi...>]

Hi!

I've noticed that in 2.0 InlineURIFactory code changed, namely when
previously the handlers were stored in a List, now they are stored in
map indexed by namespace. This change, however, prevents one from having
a handler that would apply to more than one prefix (such as one applying
to both http:// and https:// URIs, for example). Also, it kind of
assumes in init() that prefix and vocabulary namespace are the same.
I could hack around this but I wonder what is the recommended way of
handling this?
-- 
Stas Malyshev
sma...@wi...

Re: [Bigdata-developers] InlineURIFactory change

[Bryan T. <br...@sy...>]

Could you register the same handler multiple times, once for each namespace?

On Wednesday, January 6, 2016, Stas Malyshev <sma...@wi...>
wrote:

> Hi!
>
> I've noticed that in 2.0 InlineURIFactory code changed, namely when
> previously the handlers were stored in a List, now they are stored in
> map indexed by namespace. This change, however, prevents one from having
> a handler that would apply to more than one prefix (such as one applying
> to both http:// and https:// URIs, for example). Also, it kind of
> assumes in init() that prefix and vocabulary namespace are the same.
> I could hack around this but I wonder what is the recommended way of
> handling this?
> --
> Stas Malyshev
> sma...@wi... <javascript:;>
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Bigdata-developers mailing list
> Big...@li... <javascript:;>
> https://lists.sourceforge.net/lists/listinfo/bigdata-developers
>


-- 
----
Bryan Thompson
Chief Scientist & Founder
SYSTAP, LLC
4501 Tower Road
Greensboro, NC 27410
br...@sy...
http://blazegraph.com
http://blog.blazegraph.com

Blazegraph™ <http://www.blazegraph.com/> is our ultra high-performance
graph database that supports both RDF/SPARQL and Tinkerpop/Blueprints
APIs.  Blazegraph is now available with GPU acceleration using our disruptive
technology to accelerate data-parallel graph analytics and graph query.

CONFIDENTIALITY NOTICE:  This email and its contents and attachments are
for the sole use of the intended recipient(s) and are confidential or
proprietary to SYSTAP. Any unauthorized review, use, disclosure,
dissemination or copying of this email or its contents or attachments is
prohibited. If you have received this communication in error, please notify
the sender by reply email and permanently delete all copies of the email
and its contents and attachments.

Re: [Bigdata-developers] InlineURIFactory change

[Stas M. <sma...@wi...>]

Hi!

> Could you register the same handler multiple times, once for each namespace?

No, because it indexes by handler.getNamespace() and this can return
only one value:

    protected void addHandler(final InlineURIHandler handler) {

    	//        this.handlers.add(handler);
        handlersByNamespace.put(handler.getNamespace(), handler);
    }

-- 
Stas Malyshev
sma...@wi...

Re: [Bigdata-developers] InlineURIFactory change

[Bryan T. <br...@sy...>]

It is going to me more efficient to have lookup by namespace in a map
rather than scanning a list, which is why I made this change. At the time
that I made it I was not thinking about the impact on the WDQS.  Can you
split up your handler into one handler per namespace or does that cause
problems?

Thanks,
Bryan

----
Bryan Thompson
Chief Scientist & Founder
SYSTAP, LLC
4501 Tower Road
Greensboro, NC 27410
br...@sy...
http://blazegraph.com
http://blog.blazegraph.com

Blazegraph™ <http://www.blazegraph.com/> is our ultra high-performance
graph database that supports both RDF/SPARQL and Tinkerpop/Blueprints
APIs.  Blazegraph is now available with GPU acceleration using our disruptive
technology to accelerate data-parallel graph analytics and graph query.

CONFIDENTIALITY NOTICE:  This email and its contents and attachments are
for the sole use of the intended recipient(s) and are confidential or
proprietary to SYSTAP. Any unauthorized review, use, disclosure,
dissemination or copying of this email or its contents or attachments is
prohibited. If you have received this communication in error, please notify
the sender by reply email and permanently delete all copies of the email
and its contents and attachments.

On Wed, Jan 6, 2016 at 6:37 PM, Stas Malyshev <sma...@wi...>
wrote:

> Hi!
>
> > Could you register the same handler multiple times, once for each
> namespace?
>
> No, because it indexes by handler.getNamespace() and this can return
> only one value:
>
>     protected void addHandler(final InlineURIHandler handler) {
>
>         //        this.handlers.add(handler);
>         handlersByNamespace.put(handler.getNamespace(), handler);
>     }
>
> --
> Stas Malyshev
> sma...@wi...
>

Re: [Bigdata-developers] InlineURIFactory change

[Stas M. <sma...@wi...>]

Hi!

> It is going to me more efficient to have lookup by namespace in a map
> rather than scanning a list, which is why I made this change. At the
> time that I made it I was not thinking about the impact on the WDQS. 
> Can you split up your handler into one handler per namespace or does
> that cause problems?

I think I can split them, and override init() so that it won't complain
about missing vocabulary type, I just wondered if there was a better way.

Thanks,
-- 
Stas Malyshev
sma...@wi...