[PetiteCloud] partial understanding

[Aryeh Friedman]

Partial understand is the ability to pickout specific components from a
larger structured data set for example PU could be used to select this
message from a set of messages.    It goes farther though and here are the
key concepts of partial understanding:

1. You do not need to understand the entire input to be able to process the
parts you do understand
2. In general people care more about different pieces of data/information
[note] relate to each other then do what the contents of any given "atom" is

For more on the context of how partial understanfing will be used see
http://www.petitecloud.org/dudes.pdf.

FNWE obviously has some ideas on how to implement this but a) it is a
community project and not just ours (the open source components that is)
and b) not to influence peoples thinking prematurely.   Therefore we would
like to know what people think of the idea and how to improve it (or even
if it even makes sense or is needed).

After this init discussion we will get down into the techinical details of
the open requirements process (note to our newer members open requirements
is where we do a formal requirements phase for some component but do it in
the open instead of behind closed doors with everyone able to pitch in new
requirements and/or refine old ones).

Note: For the non-CS readers the difference between data and information is
information is "useful data" (whatever useful means in context) and data in
non-useful data.  (Anya we need help in wording this better!)
-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.petitecloud.nyclocal.net/pipermail/petitecloud-general-petitecloud.nyclocal.net/attachments/20140315/d1040e63/attachment-0002.htm>