I will adopt the notion of a "global prefix" but that will break the minute an external ontology overlaps with a prefix I already use. Hopefully better prefix handling is on the development roadmap, particularly where a prefix issue is preventing a webservice from being invoked using the prefix. Diagnosing my issue was especially difficult since the Available Web Services page showed my service as available with the prefix in the syntax.
Thanks for your help, Tim On Thu, Sep 3, 2020 at 12:05 PM dprice <dpr...@topquadrant.com> wrote: > > > On 3 Sep 2020, at 16:38, Richard Cyganiak <rich...@topquadrant.com> wrote: > > > > On 3 Sep 2020, at 16:25, Tim Smith <smith.ts...@gmail.com> wrote: > > I can see where using the same prefix for two different graphs would be a > problem if they were imported into the same import closure (not the case > here). Should it have been a problem since the two graphs never connected > other than being in the same workspace? If using the same prefix is an > issue and TBC is scanning the files to harvest prefixes, is it possible to > generate a warning when duplicate prefixes are found? > > > I don't know, to be honest. The behaviour of prefixes is... complicated... > and in some cases seems to be more the result of accident than design. > There are several oddities that I'm aware of, and I'll have to add the one > you describe to that list. What works for me is being very careful when > declaring a new prefix, and then never changing it to a different URI. > Basically, act as if there was only a single global prefix mapping, and > each graph has a subset of the mapping. > > > I explain the idea of a “global prefix” set as a best practice to all the > customer projects in which I’m involved. > > I also always define *the* prefix in the originating graph (i.e. don’t > default), then no other graph has to re-defined a prefix for anything it > imports reducing the chance of error. > > Cheers, > David > > > Richard > > -- > 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 topbraid-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/topbraid-users/C1689A88-2ED0-44B4-933F-8AF6AFE2C4FB%40topquadrant.com > . > > > UK +44 (0) 7788 561308 > US +1 (336) 283-0808 > > -- > 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 topbraid-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/topbraid-users/47E38F13-9FB7-4C5B-A3B1-9CF16058BC1A%40topquadrant.com > <https://groups.google.com/d/msgid/topbraid-users/47E38F13-9FB7-4C5B-A3B1-9CF16058BC1A%40topquadrant.com?utm_medium=email&utm_source=footer> > . > -- 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 topbraid-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/CAF0WbnJp6_%2BWJ8e%3DfZ6wpvPhPDk60FCa9ji1kB6-YhQqqAGDzA%40mail.gmail.com.
