Avoid tripping over JSONLD serialisations co-existing with TTL

[robatki...@gmail.com]

Hi

I want to work in an existing repository where there are large numbers of TTL files, but also there are JSONLD serialisations of these also present.

TBC complains "The base URI X  from X.jsonld is already used in file X.ttl , so use of this base URI may cause difficulties. Please change one or other. (TBC case)"

Also, there is a case where the JSONLD is experimental, and may or may not be broken (I want to explore different JSON-LD serialisation patterns) - and I dont want TBC to pay attention to these.

Another related case is where I have many XSD files and want to generate OWL or SHACL views of these schemas.

In all cases I want to tell TBC to only look at .ttl sources. 

Is there some tweak or trick I can use to configure this?  

[Holger Knublauch]

I cannot think of a solution for that. There is no way to deactivate certain file types.

Holger

--
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/fa1c73e5-d72d-4773-b90d-c0a5b737deb0n%40googlegroups.com.

[Rob Atkinson]

is this an eclipse thing?  

is there perhaps some blacklist strategy possible  like .gitignore 

To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/31ef6197-0e93-2037-9739-11990b9ed079%40topquadrant.com.

[robatki...@gmail.com]

OK did a little experiment - it is possible to set a resource filter on the project..

<filteredResources>

        <filter>

            <id>1616045897719</id>

            <name></name>

            <type>5</type>

            <matcher>

                <id>org.eclipse.ui.ide.multiFilter</id>

                <arguments>1.0-name-matches-false-false-*.ttl*</arguments>

            </matcher>

        </filter>

    </filteredResources>

TBC then opens it OK and shows only .ttl*  files.  

I havent yet explored what this means when deploying the project to an EDG server - any ideas? 

[Holger Knublauch]

You cannot rely on Eclipse for this moving forward. EDG (server-side) will already use a different workspace implementation that goes against the file system directly.

Holger

To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/44456064-9d1a-4712-ac73-63a86e403953n%40googlegroups.com.

[Rob Atkinson]

OK - thanks for the warning.  You might want to consider the issue of deploying a project with resources that you dont want to introspect over automatically then :-)

To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/548c12fa-61b2-3e44-198f-a5a80d07db86%40topquadrant.com.

[Pat Doyle]

We have a yarn script in our UI extension example project that prepares it for EDG server upload, excluding all of the unnecessary config files and node modules and such. 

        "zip": "(cd ../; zip sample-app.zip -r sample-app -x \"*README*\" -x \"*assets*\" -x \"*.yarnrc\" -x \"*yarn.lock*\" -x \"*babel.config.js*\" -x \"*package.json*\" -x \"*.eslintrc.js\"  -x \"*.prettierrc\" -x \"*webpack.*.js*\" -x \"*webpackConfig.js*\"  -x\"*.keep*\" -x \"*node_modules*\" -x \"*.DS_Store\"  -x \"*.gitignore\" -x\"*.git*\" )"

You could use a similar process to filter out the .jsonld ones.

To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/CACfF9LyR5qFxqikqM_ad8zgyokBWvcDi5VufhC-9StOesmHyEg%40mail.gmail.com.