Holger, Thank you :) I'll keep in mind the memory overhead.
Br, Kasia On Tuesday, September 19, 2023 at 10:33:18 AM UTC+2 Holger Knublauch wrote: > There is a technique that allows you to declare any prefix for any API. > > Put the attached file into the workspace. It is a file ending with > .api.ttl. The definitions from these files are added to the ADS APIs for > all context graphs. > > Note you need to press Refresh on the files page in EDG Studio or restart > the server or have an admin do a workspace refresh after adding an .api.ttl > file. > > In this particular file here, I am owl:importing the base EDG namespace > that declares various classes and properties. The file is also declaring > dash:generatePrefixConstants "edg", which is important. > > You could use that file as a starting point and add owl:imports and > dash:generatePrefixConstants to other namespaces of your choice. > > (I have not tested what happens if you owl:import an asset collection, > e.g. Ontology here, and I would assume it is safer to only owl:import other > files) > > Keep in mind that this will increase the size of all generated APIs, so if > you have thousands of asset collections with different combinations of > ontologies, they may cause some memory overhead, and a small overhead in > API generation. > > Holger > > -- The topics of this mailing list include TopBraid EDG and related technologies such as SHACL. To post to this group, send email to [email protected] --- You received this message because you are subscribed to the Google Groups "TopBraid Suite Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/a4d7c267-f94e-46d5-b4e6-aaed4b59b1a3n%40googlegroups.com.
