|
[XML-DEV Mailing List Archive Home]
[By Thread]
[By Date]
[Recent Entries]
[Reply To This Message]
Re: Evolving Information by XML Element Mutations
Title: Message
|
>>We see the Vineyard System has
mutated to include a new element, <fjkele>, which has new data,
30fkopcd0. What kind of mutation would be required so that Pickers can
start using this new element and data? Does the stylesheet need to undergo
a mutation? This seems very complicated (especially trying to mutate a
stylesheet). There must be a simpler way to introduce mutations.
What are your
thoughts?<<
Well, if you wanted
to emulate the E Coli system, you need a couple of things: (1) a picker that
starts producing something into the environment. (2) a picker that suddenly
requires that something (3) the ability for the environment to hold that
something.
Perhaps a simple way
to do this would be to come up with a random list of "somethings"-- in the case
of the E Coli it was a chemical. So if you had a random list of chemicals, and
each round had the chance of a mutation (either consumed or produced) then you
could potentially find a match. This is very simplistic though. Not real. But it
may eventually bear an interesting parallel to the business world which is full
of producers and consumers that form interesting relationships. Right now you
have one of these relationships:
Vineyard produces
grapes
Picker consumes
grapes.
Right now, all of
the logic in the stylesheet is directed around this one single relationship of
grapes. However it could be geared around a more generalized list of production
and consumption that can ultimately be "mutated" each generation. Then the logic
of the stylesheet would be geared around the relationships rather than grapes.
Of course to make it interesting mutations should affect metabolism... if a
picker grows a third arm then it will cost him more grapes. This would give a
start for one avenue of mutation-- then again I am not sure what people would
produce that others would need to consume...
<picker>
....
<consumes>
...
</consumes>
<produces>
...
</produces>
</picker>
Out of curiosity
what is the goal here? As Rick said there is already quite a bit of genetic
programming out there, though this is a fun example and though it is iterative
it isn't strictly generational as there is no reproduction of the mutations--
but when do we get to see the pretty output?
Cheers,
Jeff
Rafter
|
|
PURCHASE STYLUS STUDIO ONLINE TODAY!
Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!
Download The World's Best XML IDE!
Accelerate XML development with our award-winning XML IDE - Download a free trial today!
Subscribe in XML format
| RSS 2.0 |
 |
| Atom 0.3 |
 |
| |
Stylus Studio has published XML-DEV in RSS and ATOM formats,
enabling users to easily subcribe to the list from their preferred news reader application.
|
Stylus Studio Sponsored Links are added links designed to provide related and additional information to the visitors of this website.
they were not included by the author in the initial post. To view the content without the Sponsor Links please
click here.
|
|
Cart
