Tom,
Looking at the outline, a few things jump out at me.
1. Architectural concepts behind OODT
OODT was defined by an initial set of architectural principles that I
believe still hold today. A key one being the separation of the software
components from the information model. It's my belief that this is why
OODT could be applied to so many different domains.
In addition, there are some key architectural patterns behind OODT but two
very prominent ones:
(1) Information capture, processing, etc - In the early days this was
first implemented by the Palomar Testbed Interferometer and SeaWinds)
which defined the CAS
(2) Data discovery, access, distribution, integration, of highly
distributed, heterogeneous systems - This was defined by projects like
NASA/PDS, NCI/EDRN, etc
Many of the architectural decisions made the foundation of OODT as a data
science ecosystem and have allowed for it to be applied not only to
different domains, but also to allow it to scale and integrate with
different technologies and standards including messaging systems, cloud
infrastructures, different database backends, etc. In fact, this allowed
NASA to move away from being tightly coupled to a vendor ground data
systems to use OODT an open source processing infrastructure for Earth
Science back in 2003.
It would be good to include this in Part I. Much of it right now is in
academic papers.
2. Section 5.x - OODT's web grid components are much less about
computation/processing and more about data intensive capabilities of
discovery (e.g., Profile Services) , access, transformation, and
distribution (e.g., Product Services). I would stress the distributed
deployment of OODT to integrate highly distributed, heterogeneous systems.
This is how PDS, EDRN, and some other biomedical data networks are using
it.
We've kept Profile/Product and CAS components as separate so I would think
that 5.1, 5.2, 5.3, and 5.6 should move up to section 4 or a new section
should be create to address the information integration aspects with the
web grid pieces moving into it.
3. Section 10 - EDRN is certainly example of integrating heterogeneous,
distributed systems together but PDS and others can be discussed. For
EDRN and PDS, it's much less about distributed data entry and much more
focused on how to integrate, transform, and distribute data across highly
distributed systems.
Hope this helps.
Dan
On 5/26/15 7:38 AM, "Tom Barber" <[email protected]> wrote:
>Thanks Chris.
>
>Eva, I think we can probably include that stuff within one of the existing
>tutorial sections as your ideas aren't too crazy ;)
>
>Tom
>
>On Tue, May 26, 2015 at 3:07 PM, Mattmann, Chris A (3980) <
>[email protected]> wrote:
>
>> you have to have a chapter on NASA earth science missions :)
>> I added it..good luck!
>>
>> ________________________________________
>> From: Tom Barber [[email protected]]
>> Sent: Tuesday, May 26, 2015 2:52 AM
>> To: [email protected]
>> Subject: Re: OODT book proposal
>>
>> Alright chaps this is pretty last minute as I have to chat to the guy
>>from
>> Manning tomorrow so if anyone has 5 minutes, can you scan:
>>
>>
>>https://docs.google.com/document/d/1dGVf0j25WzXZCyTyuX9aMmmQ06yAPLOFtuTFZ
>>e-0aXk/edit?usp=sharing
>> and add anything you think is missing. The link is open to all so you
>> should be able to add/change entries, just italicise them or something
>>so I
>> can spot them.
>>
>> Thanks
>>
>> Tom
>>
>> On Wed, May 20, 2015 at 7:14 PM, Tom Barber <[email protected]>
>> wrote:
>>
>> > Thanks for the feedback guys.
>> >
>> > The chat I had with the chap was certainly around a full book as I
>>have
>> to
>> > pitch 9 - 14 chapters. He did say they are trying to move away from
>> generic
>> > platform books so I think pitching it in the style of a look at all
>>the
>> > main components and heavy on the real world how-to and use cases
>>would be
>> > the way I'm tending to go along with a load of stuff on the value of
>> > metadata etc.
>> >
>> > We discussed use case ideas and I went over some of the crazy NASA
>>stuff
>> > which he said I should include and also a bunch of real world use
>> > cases(smart meters/regulatory compliance application and stuff from my
>> day
>> > job), but of course, you lot don't live in the real world so you'll
>>have
>> to
>> > leave that to me ;)
>> >
>> > On 1.0 I'm sure it will come out during the time we would spend
>>writing a
>> > book.
>> >
>> > I'll come back with a draft toc tonight or tomorrow and those
>>interested
>> > can add their 10 cents.
>> >
>> > Tom
>> > On 20 May 2015 18:26, "Lewis John Mcgibbney"
>><[email protected]>
>> > wrote:
>> >
>> >> Spoke to Tom White a while ago @ApacheCon about this very topic folks
>> with
>> >> one interesting outcome.
>> >> Many publishers (I don't know about Manning, however Chris will
>>likely
>> >> know) are interested in Microbooks or picket guides as well.
>> >> An example is the following
>> >> http://shop.oreilly.com/product/9780596007430.do
>> >> I don't know if this fits for something like OODT but you guys can
>> >> consider.
>> >> Lewis
>> >>
>> >> On Wed, May 20, 2015 at 10:11 AM, Chris Mattmann <
>> >> [email protected]>
>> >> wrote:
>> >>
>> >> > Thanks Mike. I don¹t think 1.0 is required
>> >> > *before* writing the book, but can happen
>> >> > while the book is going on (and be pushed in
>> >> > many cases by the book!) :)
>> >> >
>> >> > We had the same scenario with Tika in Action.
>> >> >
>> >> > Cheers,
>> >> > Chris
>> >> >
>> >> > ------------------------
>> >> > Chris Mattmann
>> >> > [email protected]
>> >> >
>> >> >
>> >> >
>> >> >
>> >> > -----Original Message-----
>> >> > From: Michael Starch <[email protected]>
>> >> > Reply-To: <[email protected]>
>> >> > Date: Wednesday, May 20, 2015 at 10:10 AM
>> >> > To: <[email protected]>
>> >> > Subject: Re: OODT book proposal
>> >> >
>> >> > >I am definitely up for this. Are we going to push for an OODT-1.0
>> >> > >"polished" released before we write a book? There seem to be a
>>lot
>> of
>> >> > >very
>> >> > >nice features in the pipe, which will affect the content of a
>>book.
>> >> > >
>> >> > >Regardless, I believe the following may be helpful for the book.
>> >> > >
>> >> > > - Setting Up OODT
>> >> > > - Major OODT Components
>> >> > > - Extending OODT
>> >> > > - OODT in Operations
>> >> > >
>> >> > >-Michael
>> >> > >
>> >> > >On Wed, May 20, 2015 at 9:24 AM, Freeborn, Dana J (398G) <
>> >> > >[email protected]> wrote:
>> >> > >
>> >> > >> Hi Tom,
>> >> > >>
>> >> > >> This is great. I would be happy to contribute to the book if my
>> >> level
>> >> > >>of
>> >> > >> experience with OODT (which is high) is helpful. It's not
>>clear to
>> >> me
>> >> > >>your
>> >> > >> focus for the book, so you'll just have to tap me if I can
>> >> contribute.
>> >> > >> Paul and Chris will know if I do. Otherwise, I will cheer on
>>your
>> >> > >> efforts. :-)
>> >> > >>
>> >> > >> Thanks,
>> >> > >> Dana
>> >> > >>
>> >> > >>
>> >> > >> From: Tom Barber
>> >> > >><[email protected]<mailto:[email protected]>>
>> >> > >> Reply-To: "[email protected]<mailto:[email protected]>" <
>> >> > >> [email protected]<mailto:[email protected]>>
>> >> > >> Date: Wednesday, May 20, 2015 2:02 AM
>> >> > >> To: "[email protected]<mailto:[email protected]>"
>> >> > >><[email protected]
>> >> > >> <mailto:[email protected]>>
>> >> > >> Subject: OODT book proposal
>> >> > >>
>> >> > >> Hi guys,
>> >> > >>
>> >> > >> I was on the phone to Manning today about an OODT book that me,
>> Chris
>> >> > >>and
>> >> > >> Mike Starch mulled over in Texas.
>> >> > >>
>> >> > >> I've been tasked with coming up with a TOC as the proposal so
>>I'll
>> >> knock
>> >> > >> something together and share it later in the week, but on this
>> topic.
>> >> > >>
>> >> > >> a) Does anyone have anything they'd especially like to see in an
>> OODT
>> >> > >>book?
>> >> > >> b) Does anyone want to help donate some hours writing a bit of
>>the
>> >> book
>> >> > >> (won't be any time soon and takes months so don't worry about
>>it,
>> >> and I
>> >> > >> wont hold you to it, just looking for interest)
>> >> > >>
>> >> > >>
>> >> > >> Tom
>> >> > >>
>> >> > >>
>> >> >
>> >> >
>> >> >
>> >>
>> >>
>> >> --
>> >> *Lewis*
>> >>
>> >
>>
