Relative Path in Parameter of Components

[TimmRuppert]

Hello,

is it possible to use a relative path (URI) as an FMU parameter? Specifically, I would like it to be resolved relative to the SSD file, similar to how an FMU path (source) can be specified.

<ssd:Component type="application/x-fmu-sharedlibrary" source="./fmus/myFMU.fmu"..

Obviously the following V1.0 snippet would not work as the String would simply be exposed to the fmu (which might or might not resolve it relative to itself) :

     <ssd:Elements>
           <ssd:Component....>
                <ssd:ParameterBindings>
                   <ssd:ParameterBinding>
                       <ssd:ParameterValues>
                           <ssv:ParameterSet version="1.0" name="Internal Parameter-Set">
                               <ssv:Parameters>
                                   <ssv:Parameter name="xosc_path">
                                       <ssv:String
                                           value="./xosc/my_example.xosc" />
                                   </ssv:Parameter>
                               </ssv:Parameters>
                           </ssv:ParameterSet>
                       </ssd:ParameterValues>
                   </ssd:ParameterBinding>
                   ...
              </ssd:Component>
     </ssd:Elements>

[pmai]

is it possible to use a relative path (URI) as an FMU parameter? Specifically, I would like it to be resolved relative to the SSD file, similar to how an FMU path (source) can be specified.

<ssd:Component type="application/x-fmu-sharedlibrary" source="./fmus/myFMU.fmu"..

As an aside, the whole ./ part here is fully redundant, as source="fmus/myFMU.fmu" is already a relative URI and will be resolved the same as the non-idiomatic use of ./ in front of that.

That being said, neither FMI nor SSP currently has a concept of path or URI parameters, but only string parameters, with no attached semantics. Hence the rules for what an FMU expects and can resolve are always custom. There has been some talk that adding something like this to FMI would be nice to have, and then importers could make use of that. Similarly we might consider this topic for SSP 2.1, however would likely make the most sense if FMI also started to support this, otherwise the approach is likely to be brittle...

[TimmRuppert]

Thank you for the thorough response! I had a feeling this might not be possible. I can see how balancing generalized and specialized parameters without inflating the standard could be challenging. However, for the use case where "My FMU requires an external file, and I want to specify it relative to the SSD file," this remains an important consideration - at least for me ;)