URI generator options

29 views
Skip to first unread message

Roland Wingerter

unread,
Jan 24, 2023, 1:07:05 PM1/24/23
to vocbench-user
Dear VB3 team,

I have a question concerning the URI generators in VB3.

From the Project page, it is possible to choose and configure a URI generator (either on project creation or later). The dialog form offers three generators, but two of them are almost identical (see screenshots attached).

Is that's the way it's supposed to be?

Kind regards
Roland





 
URI generator - CODA-based templated URI generator.PNG
URI generator - Native template-based.PNG

Roland Wingerter

unread,
Jan 24, 2023, 1:11:58 PM1/24/23
to vocbench-user
This screenshot shows them side by side.
URI generators - side by side.PNG

Manuel Fiorelli

unread,
Feb 8, 2023, 12:27:28 PM2/8/23
to Roland Wingerter, vocbench-user
Hi Roland,


ST URIGenerators are related to CODA Converters, as they can be used for the same purpose in each platform: producing new resource IRIs (in fact, converters have a broader scope, since they can be used to produce literals, as well). So, since ST and CODA are integrated, it makes sense to integrate these two components, as well.

Now, the CODA URI Generator uses CODA to execute a CODA converter, to produce an IRI: the configuration on the left entails the use of the template-based converter.

The Native Template URI Generator is similarly template-based, but does not claim any compliance with CODA and its converters; nonetheless, it currently use the same template-based converter mentioned before, but in a lightweight manner as an ordinary Java class.

In my opinion, it's better to use the latter, since it should be lightweight and -- maybe in the future -- with additional capabilities. A different story is for the Any Converter configuration, which enables the use of any converter (that implements the coda:randIdGen) as a URI Generator.

Please note that the integration works in the other way round, by exposing the current URI Generator as a coda converter to CODA. This is perhaps more useful, as it binds the current project URI Generator to the contract coda:randIdGen, which indeed is the true analogous of URIGenerators in CODA. Thanks to this integration, you can write PEARL rules that use coda:randIdGen so that when executed inside ST, they use the URI Generator bound to the current project, being it implemented using a CODA Converter or not.

Regards,
Manuel

--
You received this message because you are subscribed to the Google Groups "vocbench-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vocbench-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vocbench-user/6c4f9109-e125-46b7-821f-f746ecf1f6dan%40googlegroups.com.


--
Manuel Fiorelli

Roland Wingerter

unread,
Feb 9, 2023, 5:27:45 AM2/9/23
to vocbench-user
Hi Manuel,

Good to know they are two different beasts. Thank you very much for the enlightenment.

Kind regards
Roland
Reply all
Reply to author
Forward
0 new messages