|
May be late attending or unable to attend today's OSLC OP meeting
We have an ELM development all-hands meeting starting at the same time as the OSLC OP meeting. So at the least, I will be late joining. At the worst, I may be unable to join at all. Best regards, Davi
We have an ELM development all-hands meeting starting at the same time as the OSLC OP meeting. So at the least, I will be late joining. At the worst, I may be unable to join at all. Best regards, Davi
|
By
David Honey2
· #899
·
|
|
Can't make the call today
Gray, forwarded you the meeting invite. Unlikely today’s call will happen as Jim, Ed, and I cannot attend.
Gray, forwarded you the meeting invite. Unlikely today’s call will happen as Jim, Ed, and I cannot attend.
|
By
David Honey2
· #893
·
|
|
Can't make the call today
A meeting has moved and now conflicts, so I cannot attend the OSLC OP meeting today.
A meeting has moved and now conflicts, so I cannot attend the OSLC OP meeting today.
|
By
David Honey2
· #891
·
|
|
Stepping down as a co-chair
Hi Andrii, I echo the comments of others. Your contribution over the years has been stellar and most appreciated. It’s quite understandable that you need to focus on your PhD. I regret that I’ve not b
Hi Andrii, I echo the comments of others. Your contribution over the years has been stellar and most appreciated. It’s quite understandable that you need to focus on your PhD. I regret that I’ve not b
|
By
David Honey2
· #869
·
|
|
Link profiles
Thu 2nd June is a UK public holiday, so I won’t be attending the OSLC OP meeting. I will look at this next week.
Thu 2nd June is a UK public holiday, so I won’t be attending the OSLC OP meeting. I will look at this next week.
|
By
David Honey2
· #851
·
|
|
Link profiles
Re: We should reify the concept of link beyond just a single predicate OSLC avoids and discourages the use of reification. It can make querying problematic, especially for OSLC query. I don’t think we
Re: We should reify the concept of link beyond just a single predicate OSLC avoids and discourages the use of reification. It can make querying problematic, especially for OSLC query. I don’t think we
|
By
David Honey2
· #840
·
|
|
Link profiles
As you suggest Jim, we could add a new property of an oslc:Property to indicate the reverse predicate for a link. This is not without its problems. Say we added a oslc:inversePropertyDefinition proper
As you suggest Jim, we could add a new property of an oslc:Property to indicate the reverse predicate for a link. This is not without its problems. Say we added a oslc:inversePropertyDefinition proper
|
By
David Honey2
· #839
·
|
|
Link profiles
Always trying to create both forward and back links seems like the wrong thing to do, even in opt-out mode. Servers are free to either silently ignore RDF properties it doesn’t support, or to fail the
Always trying to create both forward and back links seems like the wrong thing to do, even in opt-out mode. Servers are free to either silently ignore RDF properties it doesn’t support, or to fail the
|
By
David Honey2
· #832
·
|
|
OSLC query for resources where a property is not set
Hi Jad, Yes – see https://github.com/oslc-op/oslc-specs/issues/454 OSLC query doesn’t support the richness of a full-blown query. Its original design was never intended to, and this was to constrain t
Hi Jad, Yes – see https://github.com/oslc-op/oslc-specs/issues/454 OSLC query doesn’t support the richness of a full-blown query. Its original design was never intended to, and this was to constrain t
|
By
David Honey2
· #808
·
|
|
OSLC query for resources where a property is not set
Not possible in the current OSLC query. There is no support for querying properties that do not exist.
Not possible in the current OSLC query. There is no support for querying properties that do not exist.
|
By
David Honey2
· #806
·
|
|
Survey among OSLC TRS implementers
Most IBM Rational ELM TRS implementations have specific code to construct the RDF representation of TRS events rather than relying on Jena’s automatic conversion of Java types to literals. The underly
Most IBM Rational ELM TRS implementations have specific code to construct the RDF representation of TRS events rather than relying on Jena’s automatic conversion of Java types to literals. The underly
|
By
David Honey2
· #797
·
|
|
AllowedValues not visible in the specs
Hi Jad, You can find best practice here described at https://jazz.net/wiki/bin/view/LinkedData/UseUrisForEnums. If it were an enumerated value in the spec, which it is not, then values might indeed in
Hi Jad, You can find best practice here described at https://jazz.net/wiki/bin/view/LinkedData/UseUrisForEnums. If it were an enumerated value in the spec, which it is not, then values might indeed in
|
By
David Honey2
· #766
·
|
|
AllowedValues not visible in the specs
They are not URIs. The values are of type xsd:string. I personally think the QM spec may have got it wrong here. If the intent was for the value to be an enumeration, it should have defined them as su
They are not URIs. The values are of type xsd:string. I personally think the QM spec may have got it wrong here. If the intent was for the value to be an enumeration, it should have defined them as su
|
By
David Honey2
· #764
·
|
|
AllowedValues not visible in the specs
Looking at oslc_qm:status in the TestResultShape shows: oslc:allowedValue "com.ibm.rqm.execution.common.state.failed" , "com.ibm.rqm.execution.common.state.inconclusive" , "com.ibm.rqm.execution.commo
Looking at oslc_qm:status in the TestResultShape shows: oslc:allowedValue "com.ibm.rqm.execution.common.state.failed" , "com.ibm.rqm.execution.common.state.inconclusive" , "com.ibm.rqm.execution.commo
|
By
David Honey2
· #762
·
|
|
AllowedValues not visible in the specs
I think the HTML rendered shapes should be consistent with the RDF of the shapes. I believe the former is created from the latter by Respec. Perhaps this is a Respec issue.
I think the HTML rendered shapes should be consistent with the RDF of the shapes. I believe the former is created from the latter by Respec. Perhaps this is a Respec issue.
|
By
David Honey2
· #761
·
|
|
Can/Should property constraints be non-local resources?
An olsc:Property referenced by an oslc:ResourceShape with olslc:property must be in the same RDF graph as the resource shape. This has been a requirement since OSLC core 1.0. Best regards David Get Ou
An olsc:Property referenced by an oslc:ResourceShape with olslc:property must be in the same RDF graph as the resource shape. This has been a requirement since OSLC core 1.0. Best regards David Get Ou
|
By
David Honey2
· #758
·
|