LinkShape alows to define or describe there an link to the location of the asset

[jtdemer]

In the general domain we have defined an LinkShape which alows to define or describe there an link to the location of the asset.

I have folllowing concerns about that:

• Is this the right place to provide the asset location link?
• How do we protect the asset from unauthorized downloads?
• Should be that link availible in a public catalogue?

general:LinkShape a sh:NodeShape ;
    sh:property [ sh:datatype xsd:string ;
            sh:in ("Document" "Image" "Model" "Routing" "Video" "3DPreview" "Asset") ;
            sh:message "Validation of type failed!"@en ;
            sh:description "Choose type of link." ;
            sh:name "type"@en ;
            sh:order 1 ;
            sh:maxCount 1 ;
            sh:minCount 1 ;
            sh:path general:type ],
        [ sh:datatype xsd:anyURI ;
            sh:message "Validation of url failed!"@en ;
            sh:description "Enter link as URL or DID." ;
            sh:name "url"@en ;
            sh:order 0 ;
            sh:maxCount 1 ;
            sh:minCount 1 ;
            sh:path general:url ] ;
    sh:targetClass general:Link .

An example of how data providers interpret this is already available here: https://github.com/GAIA-X4PLC-AAD/hd-map-asset-example/blob/main/metadata/Gaia_X_Example_Asset_TestfeldNiedersachsen_ALKS_ODR_offset.json

[rcrswld]

@jtdemer I have created in issue going in the same direction as yours here: https://github.com/GAIA-X4PLC-AAD/hd-map-asset-example/issues/7

@robertschubert proposed some ways of solving the issue over there.

[jtdemer]

@jtdemer I have created in issue going in the same direction as yours here: GAIA-X4PLC-AAD/hd-map-asset-example#7

@robertschubert proposed some ways of solving the issue over there.

Thx @rcrswld but I think we should fix it here in the general ontology as well

[robertschubert]

@jtdemer please see my comment in the other repo. please close the issue if ok for you. If not, we should talk.

[rcrswld]

Would it help if we add in the documentation that data providers shall not use the 'url'-property to directly refer to their asset (apart from open-data)?