Thanks. I'm using TBE-SE, not -ME. On Fri, Feb 1, 2019 at 12:06 PM Irene Polikoff <[email protected]> wrote:
> Mark, > > There are several different pre-built URI generation options in TopBraid > EDG (based on the default namespace of the graph plus either a label, > counter or system generated UUID plus, optionally, some delimiter) and you > can also plug in your custom options. However, in TBC the only available > option is the one you described. > > If you are using TBC-ME, you have a local version of TopBraid EDG. So, you > could take advantage of the different options. > > You can access EDG from TBC by going to TopBraid Applications menu in TBC > and then TopBraid EDG. For the URI generation options, go to Server > Administration -> EDG Configuration Parameters -> URI Construction Rules. I > am pretty sure that the pre-built options will let you use the sequential > counter that is global for all instances. However, schema level resources > (classes and properties) are different. It is a best practice to have more > meaningful URIs for them and not to use numbers. The co-mingling schema and > data in the way you are describing is a particularly questionable practice. > As a principle, we start with implementing a best practice and then make it > possible to diverge from it. > > Thus, currently the pre-built URI construction rules options only apply to > graphs with instance data in EDG (taxonomies, data graphs, reference > datasets, etc.), not to ontologies. But the options can be customized to > apply to ontologies and we are working on expanding pre-built URI > construction options even more for 6.2. > > There is also an option to create a SHACL primary key constraint that > contains a URI pattern plus a field which value to attach to the specified > URI pattern. When a resource is created, user needs to provide a value for > the field. The field should contain a locally (within the pattern) unique > value. > > Regards, > > Irene > > > > On Feb 1, 2019, at 10:18 AM, Mark Miller <[email protected]> wrote: > > I have used Protege to author ontologies in the past. Protege has a "new > entity" preferences screen, where you can specify a base, delimiter and > auto-incrementing suffix for new terms. So I can make :myProj_0001 and > :myProj_0002 in one session (no matter whether they are classes, properties > or individuals). Then I can close the application and resume some other > time, and the next new term will be :myProj_0003. > > In TBC, it seems like the default behavior is to create new terms based on > the URI of the asserted class, with a suffix like "_n". > > Is there a way to generate URIs in TBC that is more like the Protege style > I described? > > Thanks, > Mark > > -- > 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]. > For more options, visit https://groups.google.com/d/optout. > > > -- > 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]. > For more options, visit https://groups.google.com/d/optout. > -- 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]. For more options, visit https://groups.google.com/d/optout.
