Hi Luis, after you have imported that graph, try Transform > Convert OWL Axioms to SHACL Constraints (keeping the OWL axioms). This should assert the missing rdfs:subClassOf triples. Classes without any named superclass cannot be navigated to in the class hierarchy, even if they do exist in general.
Like any ontology that was originally designed for RDF Schema or OWL, note that this may still not look perfect. For example DC Terms seems to require DC Core for sub-property relationships. So this graph will be needed too. Holger > On 8 Oct 2024, at 1:57 PM, 'Luis Enrique Ramos García' via TopBraid Suite > Users <topbraid-users@googlegroups.com> wrote: > > Hi Carl, > > Thanks for your answer, and sorry for my late reply. > > i followed the procedure you indicated: " You could also create an actual > Ontology asset collection for it in EDG and then import the TTL into this," > > more precisely, this file: > https://www.dublincore.org/specifications/dublin-core/dcmi-terms/dublin_core_terms.ttl. > > But, I can not visualize anything in there: > > <edgissue.png> > while in protégé editor I have the following result: > > <protege.png> > > Thus, I wonder what should I be doing wrong?. > > > Best regards > > > Luis Ramos > > > > > On Saturday, August 31, 2024 at 3:43:42 PM UTC+2 Carl Burnett wrote: >> Yes, I have downloaded the DCMI Metadata Terms vocabulary in Turtle format >> and made it available for inclusion in my Ontologies via Files. You could >> also create an actual Ontology asset collection for it in EDG and then >> import the TTL into this, if you wanted it to be easily editable in EDG. >> >> On Wednesday, August 28, 2024 at 12:03:01 AM UTC-7 Luis Enrique Ramos García >> wrote: >>> Dear all, >>> >>> I have an ontology class representing a document. >>> and I would like to add some dc properties to this class like. >>> contributor >>> <https://www.dublincore.org/specifications/dublin-core/dcmi-terms/#http://purl.org/dc/elements/1.1/contributor>, >>> coverage >>> <https://www.dublincore.org/specifications/dublin-core/dcmi-terms/#http://purl.org/dc/elements/1.1/coverage>, >>> creator >>> <https://www.dublincore.org/specifications/dublin-core/dcmi-terms/#http://purl.org/dc/elements/1.1/creator>, >>> date >>> <https://www.dublincore.org/specifications/dublin-core/dcmi-terms/#http://purl.org/dc/elements/1.1/date>, >>> description >>> <https://www.dublincore.org/specifications/dublin-core/dcmi-terms/#http://purl.org/dc/elements/1.1/description>, >>> format >>> <https://www.dublincore.org/specifications/dublin-core/dcmi-terms/#http://purl.org/dc/elements/1.1/format>, >>> identifier >>> <https://www.dublincore.org/specifications/dublin-core/dcmi-terms/#http://purl.org/dc/elements/1.1/identifier>, >>> language >>> <https://www.dublincore.org/specifications/dublin-core/dcmi-terms/#http://purl.org/dc/elements/1.1/language>, >>> publisher >>> <https://www.dublincore.org/specifications/dublin-core/dcmi-terms/#http://purl.org/dc/elements/1.1/publisher>, >>> relation >>> <https://www.dublincore.org/specifications/dublin-core/dcmi-terms/#http://purl.org/dc/elements/1.1/relation>, >>> rights >>> <https://www.dublincore.org/specifications/dublin-core/dcmi-terms/#http://purl.org/dc/elements/1.1/rights>, >>> source >>> <https://www.dublincore.org/specifications/dublin-core/dcmi-terms/#http://purl.org/dc/elements/1.1/source>, >>> subject >>> <https://www.dublincore.org/specifications/dublin-core/dcmi-terms/#http://purl.org/dc/elements/1.1/subject>, >>> title >>> <https://www.dublincore.org/specifications/dublin-core/dcmi-terms/#http://purl.org/dc/elements/1.1/title>, >>> type >>> <https://www.dublincore.org/specifications/dublin-core/dcmi-terms/#http://purl.org/dc/elements/1.1/type> >>> >>> Then, I assume this vocabulary should be available in tbc, but I do not >>> find a way to include it in my ontology. >>> >>> Thus, I wonder which should be the best practice to get it done? >>> >>> Should I download the ontology and directly include it into tbc? >>> >>> >>> Best regards >>> >>> >>> Luis Ramos > > > -- > The topics of this mailing list include TopBraid EDG and related technologies > such as SHACL. > To post to this group, send email to topbraid-users@googlegroups.com > --- > 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 > <mailto:topbraid-users+unsubscr...@googlegroups.com>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/topbraid-users/f7340296-7537-4beb-8a44-dfc73944341an%40googlegroups.com > > <https://groups.google.com/d/msgid/topbraid-users/f7340296-7537-4beb-8a44-dfc73944341an%40googlegroups.com?utm_medium=email&utm_source=footer>. > <edgissue.png><protege.png> -- The topics of this mailing list include TopBraid EDG and related technologies such as SHACL. To post to this group, send email to topbraid-users@googlegroups.com --- 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/6026D45A-6E79-480D-AAFB-A6ACE3A4402A%40topquadrant.com.
