The EDG Datatypes collection type was designed to contain instances of edg:Datatype only, which are higher level domain classes than RDFS datatypes. If you are not using these edg:Datatypes, why not create an Ontology collection for your datatypes? Or the reverse question is why use a EDG Datatypes collection here?

Holger


On 30/05/2019 3:17 pm, Rob Atkinson wrote:

The project type of the include is a edg:DatatypesProjectType

it is included at creation time of a edg:DataAssetsProjectType, not in the imported datafile (but it should be able to be included explicitly IMHO)

and so I mean
OWL (or SHACL) to edg:DatatypesProjectType


On Thursday, 30 May 2019 13:33:03 UTC+10, Holger Knublauch wrote:


    On 30/05/2019 1:16 pm, Rob Atkinson wrote:
    We are modelling a system where datatypes themselves are modelled
    in OWL, but when referenced from a data asset collection these
    models cause import to fail:


    v 6.2


      File Import Failed

    Import Failed. The file declares classes, properties or shapes
    which is not supported for this asset collection type. You should
    import these into an Ontology. Unsupported resources found:

    This seems to be an over-aggressive enforcement of policy to
    separate ontologies from instances -

    a) i the check should be applied to the imported data, not the
    include closure
    So are the datatypes defined in an owl:import of the RDF file that
    you are importing?
    b) datatypes ought to be allowed to be expressed using OWL or
    SHACL models
    Could you clarify what you mean? You can imagine there is quite a
    cost in trying to support multiple ways of doing the same thing.

    (a canonical SHACL transformation of OWL models into datatype
    elements would be a good thing as well! )

    Do you mean for example turning owl:withRestrictions into
    sh:maxExclusive, such as done by the OWL2SHACL rule set, see
    owl2shacl:xsdMaxExclusive2shMaxExclusive?

    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 [email protected] <javascript:>.
    To view this discussion on the web visit
    
https://groups.google.com/d/msgid/topbraid-users/a9531bad-5aea-432f-8c72-fc8e63eb5308%40googlegroups.com
    
<https://groups.google.com/d/msgid/topbraid-users/a9531bad-5aea-432f-8c72-fc8e63eb5308%40googlegroups.com?utm_medium=email&utm_source=footer>.
    For more options, visit https://groups.google.com/d/optout
    <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] <mailto:[email protected]>. To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/5620b6d0-0661-47d0-a591-7122205cec3d%40googlegroups.com <https://groups.google.com/d/msgid/topbraid-users/5620b6d0-0661-47d0-a591-7122205cec3d%40googlegroups.com?utm_medium=email&utm_source=footer>.
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].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/topbraid-users/288cdb42-6196-a1fb-1756-7552fe2de761%40topquadrant.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to