Difference between revisions of "InstaGov/syntax"

from HTYP, the free directory anyone can edit if they can prove to me that they're not a spambot
Jump to navigation Jump to search
(extracted SMW syntax to SMW page)
(updating to reflect what I seem to be actually implementing)
 
Line 1: Line 1:
==Displaying Lists==
+
Currently, all in-page functionality is implemented via the {{xmltag|igov}} tag, which has the following options:
* '''answers''':
 
** &lt;igov list=answers name=igov target="<u>name of question</u>" vpage=<u>output var name</u> &gt;''w3tpl code to display each result''&lt;/igov&gt;
 
  
==Voting==
+
* '''show''': displays various information
&lt;igov type=vote&gt;<u>attribute being voted on</u>&lt;/igov&gt;
+
** '''show=answers''': list answers for a set of criteria
* show vote status for this item, and accept votes from qualified users
+
*** '''q='''(question ID)
* parameters:
+
*** '''u='''(user ID or name)
** '''text''' or tag contents: text describing what attribute is being voted on (quality of writing, quality of argument, agree with conclusion, belongs in category, importance, etc.)
+
*** '''name='''(name of output array for each row)
* display format will be fixed at first, later based on templates from which user can choose in preferences
+
*** '''vpage='''[name of var in which to store each page name]
 +
** '''show=question''': show summary and status of a given question (vote totals and statistics), and link to Special page for voting on it
 +
*** '''q='''(question ID)
 +
==show = question==
 
* default display format should show:
 
* default display format should show:
 
** your vote
 
** your vote
Line 16: Line 17:
 
*** later: list of individual votes
 
*** later: list of individual votes
 
*** later: voting history for this item
 
*** later: voting history for this item
 
+
==Implement later==
The rigorous way to do this would be for vote to be tied to a particular revision of a page. I am hoping that community monitoring will turn out to be more effective at preventing malicious topic-modification than revision control would be -- e.g. users can vote on whether an edit reflects a significant change to a page's meaning, and whether it should have been posted as a separate page. That will also take some development, but won't be as much of a usability obstacle as making everyone vote ''again'' every time there's a minor tweak to an answer's content.
+
* If the tag-pair has any contents, use that as a format for displaying the data; otherwise use a default format.
 
 
In any case, I'm taking the approach of developing the simplest system that's usable, but trying to anticipate problems and having ideas fleshed out for dealing with them if they happen.
 

Latest revision as of 17:18, 30 December 2012

Currently, all in-page functionality is implemented via the <igov> tag, which has the following options:

  • show: displays various information
    • show=answers: list answers for a set of criteria
      • q=(question ID)
      • u=(user ID or name)
      • name=(name of output array for each row)
      • vpage=[name of var in which to store each page name]
    • show=question: show summary and status of a given question (vote totals and statistics), and link to Special page for voting on it
      • q=(question ID)

show = question

  • default display format should show:
    • your vote
    • sum of all votes (including yours)
      • later: weighted sum based on credibility ratings
      • later: how your proxies voted
      • later: list of individual votes
      • later: voting history for this item

Implement later

  • If the tag-pair has any contents, use that as a format for displaying the data; otherwise use a default format.