Include vs Copy

15 views
Skip to first unread message

Branson, GaBriella C

unread,
Aug 28, 2024, 12:49:08 PMAug 28
to topbrai...@googlegroups.com

Hi – when do you recommend using Copy over Include? If you wouldn’t ever do that, what are the use cases where you would use Copy?

 

Thanks!

 

GaBriella

 

Holger Knublauch

unread,
Sep 1, 2024, 5:27:32 AMSep 1
to 'Luis Enrique Ramos García' via TopBraid Suite Users
Hi GaBriella,

I assume you are referring to using Include (owl:imports) in EDG vs importing an RDF file and thus copying its triples into an asset collection.

The difference would be that if the data is copied into an asset collection then it could be edited and processed like any other asset collection.

Files that are owl:imported are assumed to be stable and only changed by experts. This is usually the better option for anything edited outside of TopBraid, such as external namespaces.

In general, using Include (owl:imports) keeps things more cleanly separated and potentially avoids redundancies.

Holger


-- 
The topics of this mailing list include TopBraid EDG and related technologies such as SHACL.
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/CO6PR09MB73192F99995939D43694BC8ADA952%40CO6PR09MB7319.namprd09.prod.outlook.com.

David Price

unread,
Sep 3, 2024, 6:46:05 AMSep 3
to 'Felix Sasaki' via TopBraid Suite Users
Hi GaBriella,

I think the use case for Copy I have seen most often is when feeding schema or data into downstream apps or tools that do not care about/understand the partitioning used to govern the data/schema.

For example, if a code generator (e.g. SHACL schema to Java or C++) is in use then people often prefer one TTL will all classes and properties in it so that the owl:imports statements do not have to be processed by the generator to find all visible classes and properties.

Cheers,
David
Reply all
Reply to author
Forward
0 new messages