> On 3 Sep 2020, at 16:25, Tim Smith <[email protected]> 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.
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/topbraid-users/C1689A88-2ED0-44B4-933F-8AF6AFE2C4FB%40topquadrant.com.
