You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@oodt.apache.org by "Chris A. Mattmann (JIRA)" <ji...@apache.org> on 2010/08/25 18:38:18 UTC

[jira] Created: (OODT-28) OODT use case descriptions

OODT use case descriptions
--------------------------

                 Key: OODT-28
                 URL: https://issues.apache.org/jira/browse/OODT-28
             Project: OODT
          Issue Type: New Feature
          Components: website
            Reporter: Chris A. Mattmann


Bruce Barkstrom sent a message to the OODT email list [1] including a use case that he came up with from OODT. We should figure out a way:

1. to include this use case on the site (convert the ODT file into something like Maven XDOC?)
2. include the ODT as a site ersource and link to it

Or anything else that folks can think of. We'll track the issue here.

[1] http://s.apache.org/9f4

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Re: [jira] Updated: (OODT-28) OODT use case descriptions

Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.
Hey Guys,

I set it originally for 0.2-incubating I think which is the next release of OODT (we haven't made one in Apache yet). I think we're months away from it (and hopefully graduation to TLP comes a lot sooner than our 0.2 release ;) ).

Thanks!

Cheers,
Chris


On 9/28/10 9:22 AM, "Bruce Barkstrom" <br...@gmail.com> wrote:

That's what I thought.  I'd gotten the xdoc specs and it looked pretty
straightforward to convert my material to that format.  I've had a bunch
of other writing to do, so I was just wondering how pressed for time
this issue is.

On Tue, Sep 28, 2010 at 10:42 AM, Cameron Goodale <si...@gmail.com>wrote:

> Bruce and Chris,
>
> I looked into Maven XDOC last night and it should be pretty straight
> forward
> since there are tags to make tables, sections, lists, etc.... which should
> be enough to embed the odt text into the site.  Now I need to build the
> site
> on my local machine and try to work in a place to include the Use Case.
>
> Bruce I will be sure to update the JIRA issue with my progress, but if you
> have any specific questions please let me know.
>
> -Cameron
>
> On Tue, Sep 28, 2010 at 7:03 AM, Mattmann, Chris A (388J) <
> chris.a.mattmann@jpl.nasa.gov> wrote:
>
> > Hey Bruce,
> >
> > There isn't one really - Cameron, one of the other OODT committers got
> > interested in your use case diagram and so he is trying to figure out how
> to
> > convert it from ODT to XDOC, but he hasn't started yet, or is only
> beginning
> > on the effort.
> >
> > If you want to work with him on that, just comment on the issue and
> contact
> > Cameron directly. Otherwise, I think he is going to put up a patch for
> > review in the next few weeks and try to integrate into the website.
> >
> > How you doing - did you get your router stuff fixed? :)
> >
> > Cheers,
> > Chris
> >
> >
> >
> > On 9/28/10 6:59 AM, "Bruce Barkstrom" <br...@gmail.com> wrote:
> >
> > What's the deadline?
> >
> > On Thu, Sep 2, 2010 at 11:48 PM, Chris A. Mattmann (JIRA)
> > <ji...@apache.org>wrote:
> >
> > >
> > >     [
> > >
> >
> https://issues.apache.org/jira/browse/OODT-28?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
> > ]
> > >
> > > Chris A. Mattmann updated OODT-28:
> > > ----------------------------------
> > >
> > >    Fix Version/s: 0.2-incubating
> > >
> > > > OODT use case descriptions
> > > > --------------------------
> > > >
> > > >                 Key: OODT-28
> > > >                 URL: https://issues.apache.org/jira/browse/OODT-28
> > > >             Project: OODT
> > > >          Issue Type: New Feature
> > > >          Components: website
> > > >            Reporter: Chris A. Mattmann
> > > >             Fix For: 0.2-incubating
> > > >
> > > >
> > > > Bruce Barkstrom sent a message to the OODT email list [1] including a
> > use
> > > case that he came up with from OODT. We should figure out a way:
> > > > 1. to include this use case on the site (convert the ODT file into
> > > something like Maven XDOC?)
> > > > 2. include the ODT as a site ersource and link to it
> > > > Or anything else that folks can think of. We'll track the issue here.
> > > > [1] http://s.apache.org/9f4
> > >
> > > --
> > > This message is automatically generated by JIRA.
> > > -
> > > You can reply to this email to add a comment to the issue online.
> > >
> > >
> >
> >
> >
> > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> > Chris Mattmann, Ph.D.
> > Senior Computer Scientist
> > NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> > Office: 171-266B, Mailstop: 171-246
> > Email: Chris.Mattmann@jpl.nasa.gov
> > WWW:   http://sunset.usc.edu/~mattmann/
> > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> > Adjunct Assistant Professor, Computer Science Department
> > University of Southern California, Los Angeles, CA 90089 USA
> > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> >
> >
>



++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: Chris.Mattmann@jpl.nasa.gov
WWW:   http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++


Re: [jira] Updated: (OODT-28) OODT use case descriptions

Posted by Bruce Barkstrom <br...@gmail.com>.
That's what I thought.  I'd gotten the xdoc specs and it looked pretty
straightforward to convert my material to that format.  I've had a bunch
of other writing to do, so I was just wondering how pressed for time
this issue is.

On Tue, Sep 28, 2010 at 10:42 AM, Cameron Goodale <si...@gmail.com>wrote:

> Bruce and Chris,
>
> I looked into Maven XDOC last night and it should be pretty straight
> forward
> since there are tags to make tables, sections, lists, etc.... which should
> be enough to embed the odt text into the site.  Now I need to build the
> site
> on my local machine and try to work in a place to include the Use Case.
>
> Bruce I will be sure to update the JIRA issue with my progress, but if you
> have any specific questions please let me know.
>
> -Cameron
>
> On Tue, Sep 28, 2010 at 7:03 AM, Mattmann, Chris A (388J) <
> chris.a.mattmann@jpl.nasa.gov> wrote:
>
> > Hey Bruce,
> >
> > There isn't one really - Cameron, one of the other OODT committers got
> > interested in your use case diagram and so he is trying to figure out how
> to
> > convert it from ODT to XDOC, but he hasn't started yet, or is only
> beginning
> > on the effort.
> >
> > If you want to work with him on that, just comment on the issue and
> contact
> > Cameron directly. Otherwise, I think he is going to put up a patch for
> > review in the next few weeks and try to integrate into the website.
> >
> > How you doing - did you get your router stuff fixed? :)
> >
> > Cheers,
> > Chris
> >
> >
> >
> > On 9/28/10 6:59 AM, "Bruce Barkstrom" <br...@gmail.com> wrote:
> >
> > What's the deadline?
> >
> > On Thu, Sep 2, 2010 at 11:48 PM, Chris A. Mattmann (JIRA)
> > <ji...@apache.org>wrote:
> >
> > >
> > >     [
> > >
> >
> https://issues.apache.org/jira/browse/OODT-28?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
> > ]
> > >
> > > Chris A. Mattmann updated OODT-28:
> > > ----------------------------------
> > >
> > >    Fix Version/s: 0.2-incubating
> > >
> > > > OODT use case descriptions
> > > > --------------------------
> > > >
> > > >                 Key: OODT-28
> > > >                 URL: https://issues.apache.org/jira/browse/OODT-28
> > > >             Project: OODT
> > > >          Issue Type: New Feature
> > > >          Components: website
> > > >            Reporter: Chris A. Mattmann
> > > >             Fix For: 0.2-incubating
> > > >
> > > >
> > > > Bruce Barkstrom sent a message to the OODT email list [1] including a
> > use
> > > case that he came up with from OODT. We should figure out a way:
> > > > 1. to include this use case on the site (convert the ODT file into
> > > something like Maven XDOC?)
> > > > 2. include the ODT as a site ersource and link to it
> > > > Or anything else that folks can think of. We'll track the issue here.
> > > > [1] http://s.apache.org/9f4
> > >
> > > --
> > > This message is automatically generated by JIRA.
> > > -
> > > You can reply to this email to add a comment to the issue online.
> > >
> > >
> >
> >
> >
> > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> > Chris Mattmann, Ph.D.
> > Senior Computer Scientist
> > NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> > Office: 171-266B, Mailstop: 171-246
> > Email: Chris.Mattmann@jpl.nasa.gov
> > WWW:   http://sunset.usc.edu/~mattmann/
> > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> > Adjunct Assistant Professor, Computer Science Department
> > University of Southern California, Los Angeles, CA 90089 USA
> > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> >
> >
>

Re: [jira] Updated: (OODT-28) OODT use case descriptions

Posted by Cameron Goodale <si...@gmail.com>.
Bruce and Chris,

I looked into Maven XDOC last night and it should be pretty straight forward
since there are tags to make tables, sections, lists, etc.... which should
be enough to embed the odt text into the site.  Now I need to build the site
on my local machine and try to work in a place to include the Use Case.

Bruce I will be sure to update the JIRA issue with my progress, but if you
have any specific questions please let me know.

-Cameron

On Tue, Sep 28, 2010 at 7:03 AM, Mattmann, Chris A (388J) <
chris.a.mattmann@jpl.nasa.gov> wrote:

> Hey Bruce,
>
> There isn't one really - Cameron, one of the other OODT committers got
> interested in your use case diagram and so he is trying to figure out how to
> convert it from ODT to XDOC, but he hasn't started yet, or is only beginning
> on the effort.
>
> If you want to work with him on that, just comment on the issue and contact
> Cameron directly. Otherwise, I think he is going to put up a patch for
> review in the next few weeks and try to integrate into the website.
>
> How you doing - did you get your router stuff fixed? :)
>
> Cheers,
> Chris
>
>
>
> On 9/28/10 6:59 AM, "Bruce Barkstrom" <br...@gmail.com> wrote:
>
> What's the deadline?
>
> On Thu, Sep 2, 2010 at 11:48 PM, Chris A. Mattmann (JIRA)
> <ji...@apache.org>wrote:
>
> >
> >     [
> >
> https://issues.apache.org/jira/browse/OODT-28?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
> ]
> >
> > Chris A. Mattmann updated OODT-28:
> > ----------------------------------
> >
> >    Fix Version/s: 0.2-incubating
> >
> > > OODT use case descriptions
> > > --------------------------
> > >
> > >                 Key: OODT-28
> > >                 URL: https://issues.apache.org/jira/browse/OODT-28
> > >             Project: OODT
> > >          Issue Type: New Feature
> > >          Components: website
> > >            Reporter: Chris A. Mattmann
> > >             Fix For: 0.2-incubating
> > >
> > >
> > > Bruce Barkstrom sent a message to the OODT email list [1] including a
> use
> > case that he came up with from OODT. We should figure out a way:
> > > 1. to include this use case on the site (convert the ODT file into
> > something like Maven XDOC?)
> > > 2. include the ODT as a site ersource and link to it
> > > Or anything else that folks can think of. We'll track the issue here.
> > > [1] http://s.apache.org/9f4
> >
> > --
> > This message is automatically generated by JIRA.
> > -
> > You can reply to this email to add a comment to the issue online.
> >
> >
>
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Chris Mattmann, Ph.D.
> Senior Computer Scientist
> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> Office: 171-266B, Mailstop: 171-246
> Email: Chris.Mattmann@jpl.nasa.gov
> WWW:   http://sunset.usc.edu/~mattmann/
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Adjunct Assistant Professor, Computer Science Department
> University of Southern California, Los Angeles, CA 90089 USA
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
>

Re: [jira] Updated: (OODT-28) OODT use case descriptions

Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.
Hey Bruce,

There isn't one really - Cameron, one of the other OODT committers got interested in your use case diagram and so he is trying to figure out how to convert it from ODT to XDOC, but he hasn't started yet, or is only beginning on the effort.

If you want to work with him on that, just comment on the issue and contact Cameron directly. Otherwise, I think he is going to put up a patch for review in the next few weeks and try to integrate into the website.

How you doing - did you get your router stuff fixed? :)

Cheers,
Chris



On 9/28/10 6:59 AM, "Bruce Barkstrom" <br...@gmail.com> wrote:

What's the deadline?

On Thu, Sep 2, 2010 at 11:48 PM, Chris A. Mattmann (JIRA)
<ji...@apache.org>wrote:

>
>     [
> https://issues.apache.org/jira/browse/OODT-28?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel]
>
> Chris A. Mattmann updated OODT-28:
> ----------------------------------
>
>    Fix Version/s: 0.2-incubating
>
> > OODT use case descriptions
> > --------------------------
> >
> >                 Key: OODT-28
> >                 URL: https://issues.apache.org/jira/browse/OODT-28
> >             Project: OODT
> >          Issue Type: New Feature
> >          Components: website
> >            Reporter: Chris A. Mattmann
> >             Fix For: 0.2-incubating
> >
> >
> > Bruce Barkstrom sent a message to the OODT email list [1] including a use
> case that he came up with from OODT. We should figure out a way:
> > 1. to include this use case on the site (convert the ODT file into
> something like Maven XDOC?)
> > 2. include the ODT as a site ersource and link to it
> > Or anything else that folks can think of. We'll track the issue here.
> > [1] http://s.apache.org/9f4
>
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>
>



++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: Chris.Mattmann@jpl.nasa.gov
WWW:   http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++


Re: [jira] Updated: (OODT-28) OODT use case descriptions

Posted by Bruce Barkstrom <br...@gmail.com>.
What's the deadline?

On Thu, Sep 2, 2010 at 11:48 PM, Chris A. Mattmann (JIRA)
<ji...@apache.org>wrote:

>
>     [
> https://issues.apache.org/jira/browse/OODT-28?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel]
>
> Chris A. Mattmann updated OODT-28:
> ----------------------------------
>
>    Fix Version/s: 0.2-incubating
>
> > OODT use case descriptions
> > --------------------------
> >
> >                 Key: OODT-28
> >                 URL: https://issues.apache.org/jira/browse/OODT-28
> >             Project: OODT
> >          Issue Type: New Feature
> >          Components: website
> >            Reporter: Chris A. Mattmann
> >             Fix For: 0.2-incubating
> >
> >
> > Bruce Barkstrom sent a message to the OODT email list [1] including a use
> case that he came up with from OODT. We should figure out a way:
> > 1. to include this use case on the site (convert the ODT file into
> something like Maven XDOC?)
> > 2. include the ODT as a site ersource and link to it
> > Or anything else that folks can think of. We'll track the issue here.
> > [1] http://s.apache.org/9f4
>
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>
>

Re: [jira] Updated: (OODT-28) OODT use case descriptions

Posted by Bruce Barkstrom <br...@gmail.com>.
OK - that doesn't look too hard.

Thanks for the information.  Also, I'm an outlander
and need to get accustomed to new customs.

Bruce B.

On Fri, Sep 3, 2010 at 11:39 AM, David M Woollard <wo...@jpl.nasa.gov>wrote:

> Bruce,
>
> There are a number of formats for documentation that are easily integrated
> into our existing user's guides, website, etc. As mentioned in the comment,
> one of these formats is xDoc. You can check out this reference [1].
> Otherwise, since it is on the mailing list and has an issue, we will try to
> move on it soon.
>
> Though I think Chris thanked you on the mailing list, I'll do it as well.
> Thanks for the contribution!
>
> -Dave
>
>
> [1] http://maven.apache.org/doxia/references/xdoc-format.html
>
> ---------------------------------------------------------
> David M. Woollard, Software Engineer
> Data Management Systems and Technologies Group (388J)
> NASA Jet Propulsion Laboratory, Pasadena, CA, 91109, USA
> Office: 171-243D      Phone: (818) 354-4291
>
> "Anybody who wants to make a revolution shouldn't grab a gun.
> Just go and start working to change the world by using science
> and technology."    -Stanford Ovshinsky
>
>
>
>
>
> On Sep 3, 2010, at 8:28 AM, Bruce Barkstrom wrote:
>
> > What, if anything do I need to do?
> >
> > On Thu, Sep 2, 2010 at 11:48 PM, Chris A. Mattmann (JIRA)
> > <ji...@apache.org>wrote:
> >
> >>
> >>    [
> >>
> https://issues.apache.org/jira/browse/OODT-28?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
> ]
> >>
> >> Chris A. Mattmann updated OODT-28:
> >> ----------------------------------
> >>
> >>   Fix Version/s: 0.2-incubating
> >>
> >>> OODT use case descriptions
> >>> --------------------------
> >>>
> >>>                Key: OODT-28
> >>>                URL: https://issues.apache.org/jira/browse/OODT-28
> >>>            Project: OODT
> >>>         Issue Type: New Feature
> >>>         Components: website
> >>>           Reporter: Chris A. Mattmann
> >>>            Fix For: 0.2-incubating
> >>>
> >>>
> >>> Bruce Barkstrom sent a message to the OODT email list [1] including a
> use
> >> case that he came up with from OODT. We should figure out a way:
> >>> 1. to include this use case on the site (convert the ODT file into
> >> something like Maven XDOC?)
> >>> 2. include the ODT as a site ersource and link to it
> >>> Or anything else that folks can think of. We'll track the issue here.
> >>> [1] http://s.apache.org/9f4
> >>
> >> --
> >> This message is automatically generated by JIRA.
> >> -
> >> You can reply to this email to add a comment to the issue online.
> >>
> >>
>
>

Re: [jira] Updated: (OODT-28) OODT use case descriptions

Posted by David M Woollard <wo...@jpl.nasa.gov>.
Bruce,

There are a number of formats for documentation that are easily integrated into our existing user's guides, website, etc. As mentioned in the comment, one of these formats is xDoc. You can check out this reference [1]. Otherwise, since it is on the mailing list and has an issue, we will try to move on it soon.

Though I think Chris thanked you on the mailing list, I'll do it as well. Thanks for the contribution!

-Dave


[1] http://maven.apache.org/doxia/references/xdoc-format.html

---------------------------------------------------------
David M. Woollard, Software Engineer
Data Management Systems and Technologies Group (388J)
NASA Jet Propulsion Laboratory, Pasadena, CA, 91109, USA
Office: 171-243D      Phone: (818) 354-4291

"Anybody who wants to make a revolution shouldn't grab a gun. 
Just go and start working to change the world by using science 
and technology."    -Stanford Ovshinsky





On Sep 3, 2010, at 8:28 AM, Bruce Barkstrom wrote:

> What, if anything do I need to do?
> 
> On Thu, Sep 2, 2010 at 11:48 PM, Chris A. Mattmann (JIRA)
> <ji...@apache.org>wrote:
> 
>> 
>>    [
>> https://issues.apache.org/jira/browse/OODT-28?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel]
>> 
>> Chris A. Mattmann updated OODT-28:
>> ----------------------------------
>> 
>>   Fix Version/s: 0.2-incubating
>> 
>>> OODT use case descriptions
>>> --------------------------
>>> 
>>>                Key: OODT-28
>>>                URL: https://issues.apache.org/jira/browse/OODT-28
>>>            Project: OODT
>>>         Issue Type: New Feature
>>>         Components: website
>>>           Reporter: Chris A. Mattmann
>>>            Fix For: 0.2-incubating
>>> 
>>> 
>>> Bruce Barkstrom sent a message to the OODT email list [1] including a use
>> case that he came up with from OODT. We should figure out a way:
>>> 1. to include this use case on the site (convert the ODT file into
>> something like Maven XDOC?)
>>> 2. include the ODT as a site ersource and link to it
>>> Or anything else that folks can think of. We'll track the issue here.
>>> [1] http://s.apache.org/9f4
>> 
>> --
>> This message is automatically generated by JIRA.
>> -
>> You can reply to this email to add a comment to the issue online.
>> 
>> 


Re: [jira] Updated: (OODT-28) OODT use case descriptions

Posted by Bruce Barkstrom <br...@gmail.com>.
What, if anything do I need to do?

On Thu, Sep 2, 2010 at 11:48 PM, Chris A. Mattmann (JIRA)
<ji...@apache.org>wrote:

>
>     [
> https://issues.apache.org/jira/browse/OODT-28?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel]
>
> Chris A. Mattmann updated OODT-28:
> ----------------------------------
>
>    Fix Version/s: 0.2-incubating
>
> > OODT use case descriptions
> > --------------------------
> >
> >                 Key: OODT-28
> >                 URL: https://issues.apache.org/jira/browse/OODT-28
> >             Project: OODT
> >          Issue Type: New Feature
> >          Components: website
> >            Reporter: Chris A. Mattmann
> >             Fix For: 0.2-incubating
> >
> >
> > Bruce Barkstrom sent a message to the OODT email list [1] including a use
> case that he came up with from OODT. We should figure out a way:
> > 1. to include this use case on the site (convert the ODT file into
> something like Maven XDOC?)
> > 2. include the ODT as a site ersource and link to it
> > Or anything else that folks can think of. We'll track the issue here.
> > [1] http://s.apache.org/9f4
>
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>
>

[jira] Updated: (OODT-28) OODT use case descriptions

Posted by "Cameron Goodale (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/OODT-28?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Cameron Goodale updated OODT-28:
--------------------------------

    Attachment: User_Pickup_Interactions.odt

Original .odt file from Bruce R. Barkstrom dated Aug 25, 2010.  This will be the basis for the updates to the OODT site.

> OODT use case descriptions
> --------------------------
>
>                 Key: OODT-28
>                 URL: https://issues.apache.org/jira/browse/OODT-28
>             Project: OODT
>          Issue Type: New Feature
>          Components: website
>            Reporter: Chris A. Mattmann
>            Assignee: Cameron Goodale
>             Fix For: 0.2-incubating
>
>         Attachments: User_Pickup_Interactions.odt
>
>
> Bruce Barkstrom sent a message to the OODT email list [1] including a use case that he came up with from OODT. We should figure out a way:
> 1. to include this use case on the site (convert the ODT file into something like Maven XDOC?)
> 2. include the ODT as a site ersource and link to it
> Or anything else that folks can think of. We'll track the issue here.
> [1] http://s.apache.org/9f4

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (OODT-28) OODT use case descriptions

Posted by "Chris A. Mattmann (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/OODT-28?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris A. Mattmann updated OODT-28:
----------------------------------

    Fix Version/s: 0.2-incubating

> OODT use case descriptions
> --------------------------
>
>                 Key: OODT-28
>                 URL: https://issues.apache.org/jira/browse/OODT-28
>             Project: OODT
>          Issue Type: New Feature
>          Components: website
>            Reporter: Chris A. Mattmann
>             Fix For: 0.2-incubating
>
>
> Bruce Barkstrom sent a message to the OODT email list [1] including a use case that he came up with from OODT. We should figure out a way:
> 1. to include this use case on the site (convert the ODT file into something like Maven XDOC?)
> 2. include the ODT as a site ersource and link to it
> Or anything else that folks can think of. We'll track the issue here.
> [1] http://s.apache.org/9f4

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Assigned: (OODT-28) OODT use case descriptions

Posted by "Cameron Goodale (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/OODT-28?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Cameron Goodale reassigned OODT-28:
-----------------------------------

    Assignee: Cameron Goodale

> OODT use case descriptions
> --------------------------
>
>                 Key: OODT-28
>                 URL: https://issues.apache.org/jira/browse/OODT-28
>             Project: OODT
>          Issue Type: New Feature
>          Components: website
>            Reporter: Chris A. Mattmann
>            Assignee: Cameron Goodale
>             Fix For: 0.2-incubating
>
>
> Bruce Barkstrom sent a message to the OODT email list [1] including a use case that he came up with from OODT. We should figure out a way:
> 1. to include this use case on the site (convert the ODT file into something like Maven XDOC?)
> 2. include the ODT as a site ersource and link to it
> Or anything else that folks can think of. We'll track the issue here.
> [1] http://s.apache.org/9f4

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.