OSLC Lifecycle Integration for Project Mgmt of Contracted Delivery (PROMCODE) TC

  • 1.  Fw: A bug of OSLC version of ReSpec

    Posted 05-22-2015 13:56
    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


  • 2.  Re: Fw: A bug of OSLC version of ReSpec

    Posted 05-22-2015 17:43
    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


  • 3.  Re: Fw: A bug of OSLC version of ReSpec

    Posted 05-25-2015 15:48
    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


  • 4.  Re: Fw: A bug of OSLC version of ReSpec

    Posted 05-26-2015 18:00
    Hello Mikio, hello Steve,  At OASIS, we do not have resources to take on this sort of maintenance, unfortunately. It looks like the problem is straightforward and might not be too difficult for an experienced programmer to solve. Perhaps there is someone else in the TC with the skill set to take on the fix?  /chet On Mon, May 25, 2015 at 11:47 AM, Steve Speicher < sspeiche@gmail.com > wrote: 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


  • 5.  Re: [oslc-promcode] Re: Fw: A bug of OSLC version of ReSpec

    Posted 05-27-2015 00:09
    Naively, I think I may be able to help. (Like lion taming, right?  http://www.ibras.dk/montypython/episode10.htm ) I guess that  https://github.com/sspeiche/respec  is the latest code base for our variant of ReSpec. Looking, I see a few lion’s teeth: the fork claims. “ This branch is 112 commits ahead, 191 commits behind w3c:develop ”. Therefore, whomever adopts this has a merge fest to first tackle. Is there a chance, Steve, that you can get your fork ready for hand over and then one of us (me, perhaps) can adopt it and maintain it? Also, why do we at OASIS have a forked code base? Is there a possibility we can return to use of the mainline code? --  Lonnie VanZandt Sent with Airmail On 26 May 2015 at 12:00:10, Chet Ensign ( chet.ensign@oasis-open.org ) wrote: Hello Mikio, hello Steve,  At OASIS, we do not have resources to take on this sort of maintenance, unfortunately. It looks like the problem is straightforward and might not be too difficult for an experienced programmer to solve. Perhaps there is someone else in the TC with the skill set to take on the fix?  /chet On Mon, May 25, 2015 at 11:47 AM, Steve Speicher < sspeiche@gmail.com > wrote: 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


  • 6.  Re: [oslc-promcode] Re: Fw: A bug of OSLC version of ReSpec

    Posted 05-27-2015 13:08
    Lonnie,
    Perhaps the fork is because OASIS boilerplate,
    content and formatting created by ReSpec is different than that created
    for W3C. I don't know the details, but this fork may be a standards body
    specific variant of ReSpec for OASIS and may not need the merge because
    that would pickup W3C specific content. Steve would have to verify this.


    Jim Amsden, Senior Technical Staff Member
    OSLC and Linked Lifecycle Data
    919-525-6575




    From:      
      Lonnie VanZandt <lvanzandt@sodius.com>
    To:      
      Chet Ensign <chet.ensign@oasis-open.org>,
    Steve Speicher <sspeiche@gmail.com>, Mikio Aoyama <mikio.aoyama@nifty.com>
    Cc:      
      Arthur Ryman <arthur.ryman@gmail.com>,
    Jim Amsden/Raleigh/IBM@IBMUS, Robin Cover <robin.cover@oasis-open.org>,
    PROMCODE TC <oslc-promcode@lists.oasis-open.org>
    Date:      
      05/26/2015 08:09 PM
    Subject:    
        Re: [oslc-promcode]
    Re: Fw: A bug of OSLC version of ReSpec
    Sent by:    
        <oslc-promcode@lists.oasis-open.org>




    Naively, I think I may be able to help.
    (Like lion taming, right? http://www.ibras.dk/montypython/episode10.htm )

    I guess that https://github.com/sspeiche/respec
    is the latest code base for our variant of ReSpec. Looking, I see a few
    lion’s teeth: the fork claims. “ This
    branch is 112 commits ahead, 191 commits behind w3c:develop ”.
    Therefore, whomever adopts this has a merge fest to first tackle.

    Is there a chance, Steve, that you can
    get your fork ready for hand over and then one of us (me, perhaps) can
    adopt it and maintain it?

    Also, why do we at OASIS have a forked
    code base? Is there a possibility we can return to use of the mainline
    code?

    --
    Lonnie VanZandt
    Sent with Airmail

    On 26 May 2015 at 12:00:10, Chet Ensign
    ( chet.ensign@oasis-open.org )
    wrote:
    Hello Mikio, hello Steve,  

    At OASIS, we do not have resources to
    take on this sort of maintenance, unfortunately. It looks like the problem
    is straightforward and might not be too difficult for an experienced programmer
    to solve. Perhaps there is someone else in the TC with the skill set to
    take on the fix?

    /chet

    On Mon, May 25, 2015 at 11:47 AM, Steve
    Speicher < sspeiche@gmail.com >
    wrote:
    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


  • 7.  Re: [oslc-promcode] Re: Fw: A bug of OSLC version of ReSpec

    Posted 05-27-2015 13:55
    HI folks - Jim, I'd say that you hit it on the head. Steve did this variant specifically so that it could be used to publish specifications with OASIS style and cover page contents just as I normally prepare them. So I doubt there is anything of use to offer back to the W3C code base and indeed there might be some conflicts between them.  /chet On Wed, May 27, 2015 at 9:07 AM, Jim Amsden < jamsden@us.ibm.com > wrote: Lonnie, Perhaps the fork is because OASIS boilerplate, content and formatting created by ReSpec is different than that created for W3C. I don't know the details, but this fork may be a standards body specific variant of ReSpec for OASIS and may not need the merge because that would pickup W3C specific content. Steve would have to verify this. Jim Amsden, Senior Technical Staff Member OSLC and Linked Lifecycle Data 919-525-6575 From:         Lonnie VanZandt < lvanzandt@sodius.com > To:         Chet Ensign < chet.ensign@oasis-open.org >, Steve Speicher < sspeiche@gmail.com >, Mikio Aoyama < mikio.aoyama@nifty.com > Cc:         Arthur Ryman < arthur.ryman@gmail.com >, Jim Amsden/Raleigh/IBM@IBMUS, Robin Cover < robin.cover@oasis-open.org >, PROMCODE TC < oslc-promcode@lists.oasis-open.org > Date:         05/26/2015 08:09 PM Subject:         Re: [oslc-promcode] Re: Fw: A bug of OSLC version of ReSpec Sent by:         < oslc-promcode@lists.oasis-open.org > Naively, I think I may be able to help. (Like lion taming, right? http://www.ibras.dk/montypython/episode10.htm ) I guess that https://github.com/sspeiche/respec is the latest code base for our variant of ReSpec. Looking, I see a few lion’s teeth: the fork claims. “ This branch is 112 commits ahead, 191 commits behind w3c:develop ”. Therefore, whomever adopts this has a merge fest to first tackle. Is there a chance, Steve, that you can get your fork ready for hand over and then one of us (me, perhaps) can adopt it and maintain it? Also, why do we at OASIS have a forked code base? Is there a possibility we can return to use of the mainline code? -- Lonnie VanZandt Sent with Airmail On 26 May 2015 at 12:00:10, Chet Ensign ( chet.ensign@oasis-open.org ) wrote: Hello Mikio, hello Steve,   At OASIS, we do not have resources to take on this sort of maintenance, unfortunately. It looks like the problem is straightforward and might not be too difficult for an experienced programmer to solve. Perhaps there is someone else in the TC with the skill set to take on the fix? /chet On Mon, May 25, 2015 at 11:47 AM, Steve Speicher < sspeiche@gmail.com > wrote: 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


  • 8.  Re: [oslc-promcode] Re: Fw: A bug of OSLC version of ReSpec

    Posted 05-27-2015 15:33
    I have opened an issue about refactoring the OASIS respec "template" into a separate module that depends on respec core as an external dependency https://github.com/sspeiche/respec/issues/4 This was talked about before, wanted to get to it, you know the same song and dance. The direct thread where Robin Berjon outlined this approach is at: https://github.com/w3c/respec/issues/300#issuecomment-76697268 I hesitate to make any promises or even hopes I can do it, though I understand I "may" be the most qualified to do it (only because I created the beast we have today). Hope that helps Thanks, Steve Speicher http://stevespeicher.me On Wed, May 27, 2015 at 6:07 AM, Jim Amsden <jamsden@us.ibm.com> wrote: > Lonnie, > Perhaps the fork is because OASIS boilerplate, content and formatting > created by ReSpec is different than that created for W3C. I don't know the > details, but this fork may be a standards body specific variant of ReSpec > for OASIS and may not need the merge because that would pickup W3C specific > content. Steve would have to verify this. > > > Jim Amsden, Senior Technical Staff Member > OSLC and Linked Lifecycle Data > 919-525-6575 > > > > > From: Lonnie VanZandt <lvanzandt@sodius.com> > To: Chet Ensign <chet.ensign@oasis-open.org>, Steve Speicher > <sspeiche@gmail.com>, Mikio Aoyama <mikio.aoyama@nifty.com> > Cc: Arthur Ryman <arthur.ryman@gmail.com>, Jim > Amsden/Raleigh/IBM@IBMUS, Robin Cover <robin.cover@oasis-open.org>, PROMCODE > TC <oslc-promcode@lists.oasis-open.org> > Date: 05/26/2015 08:09 PM > Subject: Re: [oslc-promcode] Re: Fw: A bug of OSLC version of ReSpec > Sent by: <oslc-promcode@lists.oasis-open.org> > ________________________________ > > > > Naively, I think I may be able to help. (Like lion taming, right? > http://www.ibras.dk/montypython/episode10.htm ) > > I guess that https://github.com/sspeiche/respec is the latest code base for > our variant of ReSpec. Looking, I see a few lion’s teeth: the fork claims. > “This branch is 112 commits ahead, 191 commits behind w3c:develop”. > Therefore, whomever adopts this has a merge fest to first tackle. > > Is there a chance, Steve, that you can get your fork ready for hand over and > then one of us (me, perhaps) can adopt it and maintain it? > > Also, why do we at OASIS have a forked code base? Is there a possibility we > can return to use of the mainline code? > > -- > Lonnie VanZandt > Sent with Airmail > > On 26 May 2015 at 12:00:10, Chet Ensign (chet.ensign@oasis-open.org) wrote: > > Hello Mikio, hello Steve, > > At OASIS, we do not have resources to take on this sort of maintenance, > unfortunately. It looks like the problem is straightforward and might not be > too difficult for an experienced programmer to solve. Perhaps there is > someone else in the TC with the skill set to take on the fix? > > /chet > > On Mon, May 25, 2015 at 11:47 AM, Steve Speicher <sspeiche@gmail.com> wrote: > 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


Related Content