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
foragemarkuplanguage [2010-10-07 11:41] 145.50.39.12foragemarkuplanguage [2010-10-27 10:39] (current) 145.50.39.11
Line 45: Line 45:
    
 Surely there are better ways to do it. IF AT ALL: should newcomers/outsiders be allowed to plunder the limited resources of a local community? Or publicize the existence of such resources?  Surely there are better ways to do it. IF AT ALL: should newcomers/outsiders be allowed to plunder the limited resources of a local community? Or publicize the existence of such resources? 
 +
 +-Discussion-
 +[Joey] I think a markup language could indeed aid the data problem. But I would recommend some adjustments:
 +1. maybe the tag plant could be changed to edible or species. Since there are related data collections which also mark edibles like fish or other non-plant like edibles/medicine
 +2. I would expand the <picture> tag into a <media> container to support multiple media files (picture, video, perhaps even audio)
 +Maybe even an optional further classification of the type of media, jpg,png,.mp4 ect.
 +this would like like this:
 +
 +<media>
 + <picture format="jpg"></picture>
 + <video format="flash"></video>
 + <audio format="mp3"></audio>
 +</media> 
 +3. Also I would like to support the community aspect more. While the observer is described, it would like to also have further identification of the observer. Like a personal page of id. (facebook?) or just an url on the original foraging site. This way we can give credits to those who should get the credits. An in the future grand them special moderator or even admin rights according to their accuracy and/or amount of contribution
 +So the observer tag could be like this:
 +<observer>
 +   <name>Little Chef</name>
 +   <identification>http://www.boskoi.org/members/101031</identification>
 +</observer>  
 +
 +4. Last I would vote for the KML way of describing a location, since I seems to me easier to implement, and relying on spaces in xml is in my experience a possibility for a lot of errors.
 +  
 +  
 +  
 +  
 +Joey: cheers, all fair points. The observer desires to be observered, also for trust-issues, maybe use <url> instead of description? or is that against best practise? For the media-tag though maybe just use: <media>file.whateverextension</media> and let the parser figure out what it is and if to include it and how? 
 +  It makes sense to broaden the tag from plant to species, but, on the other hand, only plants stay where they are, and the augmentation annotation model works because it localizes resources with extreme precision. Also, when you open up for all species you may want to inlude another tag to record plant, fish, tree of whatever. 
 +  an example file would be:
 +  
 +  <item>
 +  <species>
 +     <latin></latin>
 +     <lan:nl>walnoot</lan:nl>
 +     <lan:eng>walnut</lan:eng>
 +  </species>
 +  <location>
 +      <longitude>39.55375305703105</longitude>  
 +      <latitude>-118.9813220168456</latitude>  
 +  </location> 
 +  <media></media> 
 +  <observation_date>Tue, 22 Jun 2010</observation_date> 
 +  <observer>
 +     <name>Little Chef</name>
 +     <identification>http://www.boskoi.org/members/101031</identification>
 +     </observer>
 +  <description:eng>old tree actively foraged by hungry, mandoline carrying, gypsies with bad temper and bad breath</description>
 +  </item>
 +
 +  
 +   
 +  
 +  
      
  • foragemarkuplanguage.1286451661.txt.gz
  • Last modified: 2010-10-07 11:41
  • by 145.50.39.12
  • Currently locked by: 110.249.201.242