[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: Fw: A bug of OSLC version of ReSpec
Doing a quick look at the code [1], it doesn't expect an array of
ranges so it just uses the single value it has. It shouldn't take
someone too much to change add this support. It would be good to log
the issue as well [2].
Robin Berjon, at one point, maintained the core ReSpec and W3C
template. He doesn't have anything to do with the OASIS
extension/module, where this code is.
My current responsibilities don't have me working on OSLC related
tasks, I may be able to provide a change in coming weeks but no
promises.
[1]: https://github.com/sspeiche/respec/blob/feature/oasis-style/js/oasis/templates/shape.html#L28
,
https://github.com/sspeiche/respec/blob/feature/oasis-style/js/oasis/shape.js#L179
[2]: https://github.com/sspeiche/respec/issues
Thanks,
Steve Speicher
http://stevespeicher.me
On Fri, May 22, 2015 at 10:43 AM, Arthur Ryman <arthur.ryman@gmail.com> wrote:
> All,
>
> Here is what I know.
>
> 1. Kaz is correct. oslc:range is multi-valued. Therefore the Resource
> Shape plugin to ReSpec is wrong. Seems like a minor fix if you
> understood the _javascript_ code.
>
> 2. Steve Speicher wrote the plugin, but he left IBM and is no longer
> involved with OSLC, AFAIK.
>
> 3. Robin Berjon is the author of ReSpec, but I do not know if he has
> the bandwidth to pick up Steve's work.
>
> 4. Understanding ReSpec is on my todo stack. I may be able to help.
>
> -- Arthur Ryman
>
> On Fri, May 22, 2015 at 9:55 AM, Mikio Aoyama <mikio.aoyama@nifty.com> wrote:
>> Dear Chet:
>>
>> I'm contacting you by the advice of Dr. Jum Amsden.
>> It seems a bug of ReSpec adopted to OASIS.
>> The details are reported below by Mr. Funakoshi.
>> Could you advise us any procedure to solve the problem?
>> Thanks.
>>
>> Best Regards,
>>
>> Mikio
>> -----Original Message----- From: Kazuhiro Funakoshi
>> Sent: Friday, May 22, 2015 2:23 PM
>> To: Mikio Aoyama ; Arthur Ryman
>> Cc: oslc-promcode@lists.oasis-open.org
>> Subject: A bug of OSLC version of ReSpec
>>
>> Prof. Aoyama, and Arthur,
>>
>> I think we met a bug of ReSpec.
>>
>> In my understanding, in Resource Shape 2.0, specifying a range property of a
>> relation allows us to restrict to one of multiple
>> resource types.
>> However, with current OSLC version of ReSpec, it shows only the last range
>> resource type instead of all of them.
>>
>> For example in [1], ldp:contains relation from ManagedItemContainer states
>> its range as Issue(oslc_promcode:Issue) in the generated
>> table.
>> On the other hand, in its rdf+turtle definition[2], it is:
>> """
>> oslc:range oslc_promcode:ScopeItem, oslc_promcode:WorkItem,
>> oslc_promcode:Artifact, oslc_promcode:Risk, oslc_promcode:Issues;
>> """
>>
>> I think this is a bug of ReSpec. Could you please forward to corresponding
>> person (it's not Steve now, right)?
>>
>> [1]
>> https://tools.oasis-open.org/version-control/browse/wsvn/oslc-promcode/shape/trunk/spec.html#manageditemcontainer
>> [2]
>> https://tools.oasis-open.org/version-control/browse/wsvn/oslc-promcode/shape/trunk/manageditemcontainershape.ttl
>>
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]