Improved type specification for `sc:Parameter` placeholders

[zyzzyxdonta]

Currently, a sc:Parameter placeholder can only describe its type via a single value which can be xsd:integer, xsd:string, ..., or rdf:List. It can also only handle literals or lists of literals.

In order to properly describe what a placeholder is for, we need to provide the possibility to describe the "inner" type, i.e. literals (xsd:string, xsd:integer, ...), as well as the "outer" type that explains the "cardinality" of the placeholder.

I suggest the following properties (and possible values) for sc:Parameter

• sc:parameterType is removed

• sc:parameterOuterType is added

  • sc:Scalar for single values (there doesn't seem to be a type for this in rdf: or rdfs:)
  • rdf:List, rdf:Seq, rdf:Bag, rdf:Alt for collections of values

• sc:parameterInnerType is added

  • xsd:integer, xsd:float, xsd:string, ... for naive data types → the value from the config is parsed to a literal of the specified type
  • rdfs:Resource → the value from the config is interpreted as a reference to a more complex resource

• sc:parameterConfigPath remains unchanged

• sc:parameterDefaultValue remains unchanged

[zyzzyxdonta]

Or use xsd:QName instead of rdfs:Resource?

[zyzzyxdonta]

It seems like xsd:QName may only look like prefix:suffix. And if the prefix is not known to Software CaRD, we can not use this for anything.

So it's probably better to use rdfs:Resource and enforce the usage of "fully qualified"(?) URLs. I.e. https://example.com/#Example rather than ex:Example.

[zyzzyxdonta]

I made the first steps towards this in #35.