On 26/04/2019 5:29 am, [email protected] wrote:
I think I have the same question. I understand that we'll want to make
the transition from managing custom SWA forms "by hand" in TBC to
managing them as SHACL forms in EDG, but how do we actually do that?
Do we have to re-create each form manually in EDG? Can we then deploy
these custom forms somehow between EDG servers?
SHACL form definitions are the way forward, and SWA form definitions are
no longer used from 6.2 onwards (except in cases where the SHACL forms
are switched off and the current Ontology editor). We don't have an
automated translator from SWA forms to SHACL because users typically
need to do more than just copy the structure - SHACL shapes also need
the sh:datatype, cardinality etc that used to be stored in OWL/RDFS. So
even if we provided some converter, it wouldn't be sufficient and I'd
rather have users review their data models properly on this occasion.
(TopBraid does include converters from RDFS/OWL to SHACL to get you
started but then you'd need to add the property groups yourself and also
make sure the property shapes get inherited correctly.
It's some work but a one-time effort and hopefully in everybody's best
interest because SHACL is a W3C standard and you'll be more likely to
benefit from the shape definitions in other TopBraid features and 3rd
party tools as well.
One further question: If the new forms do not work in the Ontology
editor, do we need to continue to use SWA forms for Ontology projects?
In 6.2 yes. I guess it would affect the case where you have instances in
ontologies. While this is work in progress and I probably shouldn't be
talking about this yet, I am currently working on a redesigned and much
slicker forms API. This is using the same shape-based layout info, so
nothing will change for the user. However, the new forms will drop the
requirements to have a GraphQL schema for your data model, and thus also
dropping requirements for things like graphql:publicClass and
graphql:name unless you want to use the current tabular search component
or web service API access for them. Instead these new forms will use a
generic GraphQL schema that also works for Ontologies and any declared
shape, regardless of the public/protected/private status of the shape.
You can then edit any kind of instance even in ontologies. This release
is however several months away.
Holger
Thanks,
Carl
On Thursday, April 25, 2019 at 2:32:25 AM UTC-7, Elise Lustenhouwer
wrote:
Hi Holger,
We had a lot of SWA forms. The transition to SHACL is maintainable
if we convert the forms per ontology and not all at the same time.
I can download the uiconfig.ui.ttl from the server and delete a
SWA form when there's a SHACL form created instead. But how can I
upload this edited file? Is this possible via TBCME or via the
interface of EDG 6.1.1?
Thanks,
Elise
--
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.
