EDG SKOS support

[Alicia Verno]

My company is currently evaluating the EDG tool, and as we load some test data, we are trying to get a handle on its abilities to handle preexisting datasets from other tools. Does EDG include full SKOS support? If not, what is not covered? Is it better from a SKOS perspective to use the taxonomy or ontology functions to manage existing SKOS-based datasets?

Thanks in advance for any thoughts and suggestions!

[Irene Polikoff]

Alicia,

EDG is organized around asset collections. There are different pre-built asset collection types. And you can define your own. 

Taxonomy is one of the pre-built asset collection type. It is used to govern assets of a type skos:Concept. Each time you create a taxonomy, SKOS will be included into it. Ontology is also an asset collection type. It is used to govern assets of type owl:Class (or rdfs:Class), properties, etc. It could also include instances of classes - although best practice is to separate them.

Many EDG capabilities are common across all asset collection types, but some are specific to a type of collection. For example, certain imports may be specific. EDG offers import of MultiTess and this importer is specific to taxonomies as it converts data in the source files into SKOS concepts. Similarly, a DDL import is specific to the data asset collections as it converts information in the DDL file into resources that are instances of edg:Database, etc. classes.

Another feature specific to taxonomies is that there is a specialized editor application that is optimized for creating and working with SKOS concepts. With this, my first recommendation for you would be to use taxonomies, but the final recommendation may change after I see your datasets. Taxonomies and ontologies can and often do work together. For example, if you have defined any custom (not SKOS) classes and properties, you may put them into an ontology and have only instances in the taxonomy.

Regards,

Irene Polikoff

On Jun 12, 2017, at 1:55 PM, Alicia Verno <alicia...@gmail.com> wrote:

My company is currently evaluating the EDG tool, and as we load some test data, we are trying to get a handle on its abilities to handle preexisting datasets from other tools. Does EDG include full SKOS support? If not, what is not covered? Is it better from a SKOS perspective to use the taxonomy or ontology functions to manage existing SKOS-based datasets?

Thanks in advance for any thoughts and suggestions!

--
You received this message because you are subscribed to the Google Group "TopBraid Suite Users", the topics of which include the TopBraid Suite family of products and its base technologies such as SPARQLMotion, SPARQL Web Pages and SPIN.
To post to this group, send email to topbrai...@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-user...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.