Re: AllowedValues not visible in the specs
|
David Honey2
Looking at oslc_qm:status in the TestResultShape shows:
Also the value type is: oslc:valueType xsd:string ;
That seems like an error to me. All of those allowed values are specific to IBM’s ETM application. The description of that property says: “Used to indicate the state of the Test Result based on values defined by the service provider. Most often a read-only property.” Using allowed values for a string value goes against general linked data guidance that says that enumeration values should have URIs. This means that the allowed values should be URIs, and may have a specific type that might defined as the oslc:range of that property.
I think you should submit a defect against that resource shape. Those allowed value should be removed.
David.
From: oslc-op@... <oslc-op@...>
On Behalf Of Jad El-Khoury
Hi I was looking for examples of AllowedValues, and noticed that these values are not directly visible in the HTML version of the specs, yet they are well defined in the RDF version. For example, in https://oslc-op.github.io/oslc-specs/specs/qm/quality-management-shapes.ttl ZjQcmQRYFpfptBannerStart
ZjQcmQRYFpfptBannerEnd Hi
I was looking for examples of AllowedValues, and noticed that these values are not directly visible in the HTML version of the specs, yet they are well defined in the RDF version.
For example, in https://oslc-op.github.io/oslc-specs/specs/qm/quality-management-shapes.ttl, I can see the allowedValue list for a TestResult. But this is not seen in https://oslc-op.github.io/oslc-specs/specs/qm/quality-management-shapes.html#TestResultShape
I think such information is important to show in the specs that the people read. Does it make sense to add such info?
regards ______________________________ Jad El-khoury, PhD KTH Royal Institute of Technology School of Industrial Engineering and Management, Mechatronics Division Brinellvägen 83, SE-100 44 Stockholm, Sweden Phone: +46(0)8 790 6877 Mobile: +46(0)70 773 93 45
|
||||
|
|