Local or remote link: Handle file locations of the file

[royscheeren]

Scope

We need to know where the asset file is going to live.

Definition of done

• [ ] Extract the datalink property
• [ ] Determine if its a "local" or remote link
• [ ] Use this to create the metadata.json used for the NFT

[jdsika]

Open manifest.json and check if it is a remote or local uri:

"manifest:data": [
        {
          "@type": "manifest:Link",
          "manifest:relativePath": {
            **"@value": "./data/Gaia_X_Example_Asset_TestfeldNiedersachsen_ALKS_ODR.xodr"**,
            "@type": "xsd:anyURI"
          },
          "manifest:type": "Data",
          "manifest:format": "xodr",
          "manifest:accessRole": "owner"
        },
        {
          "@type": "manifest:Link",
          "manifest:relativePath": {
            **"@value": "./data/Gaia_X_Example_Asset_TestfeldNiedersachsen_ALKS_ODR_offset.xodr",**
            "@type": "xsd:anyURI"
          },
          "manifest:type": "Data",
          "manifest:format": "xodr",
          "manifest:accessRole": "owner"
        }
      ],

[jdsika]

Important: The process definition and necessary software/libraries for "incremental authorization" need to be available and documented because the owner of the REMOTE is responsible to provide access to the file through this process. The same way ENVITED is providing the access for the self-hosted data