Closed robons closed 1 year ago
Cheers, qb:order
was a quick addition and I didn't take enough care adding it rather than it being a fundamental misunderstanding. Hopefully corrected that now, added a section on the data structure definition, the component specification (which has qb:order
) and then the component properties themselves.
Have swapped out the range.
Fundamental Misunderstanding of Components
The 'components' discussed in the components section are actually the component's properties. There is some misunderstanding in the document as to what a component is. See the DSD section in the spec for more information.
Components have the order, not the component properties
See
Example 4
in the the DSD section in the spec. It's the components which have the order, not the component properties. In example 4 we see that the component properties (the dimensions are things likeeg:refArea
), but it's the component itself which has theqb:order
triple.Dimension can't have string range and a code list
As per the spec:
The following RDF contained in the application profile is incorrect as it declares an inappropriate range given it has a code list: