Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
Next revisionBoth sides next revision
foragemarkuplanguage [2010-08-17 13:47] – 145.50.39.12foragemarkuplanguage [2010-09-09 19:27] – 86.95.48.238
Line 1: Line 1:
 ====Forage Mark-Up Language==== ====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 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. +There are so many 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. There is no technical reason why local data collected in Utrecht ([[http://plukdestad.nl/]]) or Amsterdam ([[http://urbanedibles.blogspot.com/]]) can't be dropped on worldwide maps ([[http://www.foodspotting.com/]] and [[http://forage.rs/]]) or why old/dead projects can be imported as an initial dataset for a new project. It makes sense for local communities to maintain their own applications limited to a few streets or a neighbourhood. In fact territories as large as Utrecht (a medium sized city) already seem much too big to faithfully map. Foraging takes time, knowledge and heightened awareness, it can't be done haphazardly. It makes sense to harvest local data to connect it with other data. A little active consideration on how to make this data shareable would do us all good. Perhaps, instead of kickstarting the same thing thousand times for a thousand little projects the edible city community could organize itself modularly.  
  
 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. 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.
Line 13: Line 13:
   <description>the plants in this list have been checked several times</description>    <description>the plants in this list have been checked several times</description> 
   <language>NL</language>   <language>NL</language>
 +  <pubDate>Wed, 25 Aug 2010 07:33:42 GMT</pubDate> 
  
 The second part is a list of elements like these, each containing for each sighting the basic information The second part is a list of elements like these, each containing for each sighting the basic information
  • foragemarkuplanguage.txt
  • Last modified: 2010-10-27 10:39
  • by 145.50.39.11