It is quite a common scenario, I am afraid - see dct and dcterms. So
printing out a warning each time this is found is probably an overkill
(although we do print similar warnings on the Namespaces tab when an
owl:Ontology is selected).
May I ask why this issue affects you? The triples are the same when the
file is re-read. Is it for cosmetic reasons?
Holger
On 15/05/2018 17:09, Bohms, H.M. (Michel) wrote:
Hi Holger,
Thx. That was it indeed (somewhere 3 levels deep imported from the web…).
Is there some best practice to deal with this issue.
Not only Dublin core but also ofr other common resources like
geosparql typically multiple prefixes are used.
Thx Michel
Dr. ir. H.M. (Michel) Böhms
Senior Data Scientist
T +31888663107
M +31630381220
E [email protected] <mailto:[email protected]>
Location
<https://www.google.com/maps/place/TNO+-+Locatie+Delft+-+Stieltjesweg/@52.000788,4.3745183,17z/data=%213m1%214b1%214m5%213m4%211s0x47c5b58c52869997:0x56681566be3b8c88%218m2%213d52.000788%214d4.376707>
<http://www.tno.nl/>
This message may contain information that is not intended for you. If
you are not the addressee or if this message was sent to you by
mistake, you are requested to inform the sender and delete the
message. TNO accepts no liability for the content of this e-mail, for
the manner in which you use it and for damage of any kind resulting
from the risks inherent to the electronic transmission of messages.
*Van:*[email protected]
<[email protected]> *Namens *Holger Knublauch
*Verzonden:* dinsdag 15 mei 2018 01:37
*Aan:* [email protected]
*Onderwerp:* Re: [topbraid-users] dublin core prefixes
Please check again whether one of the imported graphs defines the dce
prefix. If multiple prefixes exist for the same namespace then the
rendering is unpredictable (dcterms and dct is a common example that
often goes wrong).
Holger
On 14/05/2018 20:40, Bohms, H.M. (Michel) wrote:
I have only one prefix…
Here it looks fine.
When I now switch to Source Code view I get:
So dc is changed somehow to dce…..
Isn’t that weird 😊?
Dr. ir. H.M. (Michel) Böhms
Senior Data Scientist
T +31888663107
M +31630381220
E [email protected] <mailto:[email protected]>
Location
<https://www.google.com/maps/place/TNO+-+Locatie+Delft+-+Stieltjesweg/@52.000788,4.3745183,17z/data=%213m1%214b1%214m5%213m4%211s0x47c5b58c52869997:0x56681566be3b8c88%218m2%213d52.000788%214d4.376707>
<http://www.tno.nl/>
This message may contain information that is not intended for you.
If you are not the addressee or if this message was sent to you by
mistake, you are requested to inform the sender and delete the
message. TNO accepts no liability for the content of this e-mail,
for the manner in which you use it and for damage of any kind
resulting from the risks inherent to the electronic transmission
of messages.
*Van:*[email protected]
<mailto:[email protected]>
<[email protected]>
<mailto:[email protected]> *Namens *Holger Knublauch
*Verzonden:* maandag 14 mei 2018 12:27
*Aan:* [email protected]
<mailto:[email protected]>
*Onderwerp:* Re: [topbraid-users] dublin core prefixes
Maybe your file defines two prefixes for the same namespace URI?
Nothing TBC does by itself.
Holger
Sent from my iPad
On 14 May 2018, at 19:55, Bohms, H.M. (Michel)
<[email protected] <mailto:[email protected]>> wrote:
When using dc prefix
I see that tbc changes it to (in format tab):
eurotl:MyDocument
rdf:type eurotl:Document ;
***dce*:format "mime:text/turtle" <mime:text/turtle> ;
rdfs:label "LocationByCoordinates" ;
.
Does anybody know why?
Thx michel
Dr. ir. H.M. (Michel) Böhms
Senior Data Scientist
T +31888663107
M +31630381220
E [email protected] <mailto:[email protected]>
Location
<https://www.google.com/maps/place/TNO+-+Locatie+Delft+-+Stieltjesweg/@52.000788,4.3745183,17z/data=%213m1%214b1%214m5%213m4%211s0x47c5b58c52869997:0x56681566be3b8c88%218m2%213d52.000788%214d4.376707>
<image001.gif> <http://www.tno.nl/>
This message may contain information that is not intended for
you. If you are not the addressee or if this message was sent
to you by mistake, you are requested to inform the sender and
delete the message. TNO accepts no liability for the content
of this e-mail, for the manner in which you use it and for
damage of any kind resulting from the risks inherent to the
electronic transmission of messages.
--
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]
<mailto:[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]
<mailto:[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]
<mailto:[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]
<mailto:[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]
<mailto:[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.
