Optional constraints for Visualize profile

[tpluscode]

• dimension's nodeKind is not required, but should be there (if ns.sh.nodeKind === ns.sh.Literal dimension is treated as literal dimension, otherwise as namedNode dimension). If nodeKind is absent, we treat dimension as Literal dimension,
• dimension's scaleType is not required, but should be there so we can properly categorize dimension type (ns.qudt.NominalScale, ns.qudt.OrdinalScale, ns.qudt.RatioScale or ns.qudt.IntervalScale),
• dimension's sh:in property should be specified to avoid sending additional queries to fetch available dimension values,
• dimension should have:
  • localized ns.schema.name,
  • localized ns.schema.description,
  • ns.rdf.type === ns.cube.KeyDimension if it's a key dimension,
  • ns.rdf.type === ns.cube.MeasureDimension if it's a measure,
  • optionally have ns.qudt.hasUnit property,
  • ns.sh.order property to sort the dimensions e.g. in table preview,

Originally posted by @bprusinowski in #114 (comment)

[tpluscode]

The second point because is technically already required by the standalone-constraint-constraint however it allows an additional qudt:EnumerationScale.

cube-link/validation/standalone-constraint-constraint.ttl

Lines 44 to 49 in 23357ab

	sh:property [
	sh:path qudt:scaleType;
	sh:in ( qudt:IntervalScale qudt:NominalScale qudt:EnumerationScale qudt:RatioScale qudt:OrdinalScale) ;
	sh:maxCount 1;
	sh:message "If qudt:scaleType is used it needs to be within ( qudt:IntervalScale qudt:NominalScale qudt:EnumerationScale qudt:RatioScale qudt:OrdinalScale )"
	];

qudt:EnumerationScale is not actually mentioned by cube.link spec nor Cube Creator wiki. cc @Rdataflow