Differences

This shows you the differences between two versions of the page.

--- foragemarkuplanguage [2010-08-17 13:02] – 145.50.39.12
+++ foragemarkuplanguage [2010-08-17 13:06] – 145.50.39.12
@@ Line 1: / Line 1: @@
 ====Forage Mark-Up Language====
-With all these edible city/urban forage projects mushrooming all over the place, as the latest fad for artists, environmentalists and culinary type, I notice a certain perpeptual reinvention of the wheel. All that data on where to find edible foodstuffs is locked-up in different formats usable only for that specific project. A little active consideration on how to make this data sharable would do us all good. Perhaps, instead of kickstarting the same thing thousand times for a thousand little projects the edible city community could bootstrap itself into a worldwide network able to create data beyond today and beyond the local.
+With all these edible city/urban forage projects mushrooming all over the place, as the latest fad for artists, environmentalists and culinary types, I notice a certain perpeptual reinvention of the wheel. All that data on where to find edible foodstuffs is locked-up in different formats usable only for that specific project. A little active consideration on how to make this data sharable would do us all good. Perhaps, instead of kickstarting the same thing thousand times for a thousand little projects the edible city community could bootstrap itself into a worldwide network able to create data beyond today and beyond the local.
-What we need is a uniform way of storing data that could be easily translated to others formats (KML/google map applications especially). I hear people talk about recording where what species can be found, adding to this layers  of information like the most likely time to harvest, what parts can be used and what parts not, recipes, medical uses, but also known problems with pollution and/or ownership in a given erea.
+What we need is a uniform way of storing data that could be easily translated to other formats (KML/google map applications especially). I hear people talk about recording where what species can be found, adding to this layers  of information like the most likely time to harvest, what parts can be used and what parts not, recipes, medical uses, but also known problems with pollution and/or ownership in a given erea. Some of these things should be included, some of these things belong elsewhere.
-Something like this maybe already exists and, thinking aloud, what about adopting our own quasi-RSS: FML: Forage Mark-Up Language:
+what follows probably already exists elsewhere but, just thinking aloud for my own fun, here are some notes on a quasi-RSS for foraging: FML: Forage Mark-Up Language:
-The first part (the channel tag in RSS); who provides the data:
+The first part (the channel tag in RSS) tells who is providing the data:
   <name>libarynth cookery department</name>