This would also allow judges to input their own judgments.

----
Publius Scribonius Scholasticus

On Fri, May 19, 2017 at 7:32 PM, Gaelan Steele <g...@canishe.com> wrote:

> How is the CFJ database stored now? If it's flat files, you could upload
> it to GitHub under AgoraNomic (I can invite you)
>
> Gaelan
>
> > On May 19, 2017, at 2:25 PM, Kerim Aydin <ke...@u.washington.edu> wrote:
> >
> >
> >
> > Happy to have help!  I'm not starting in on this immediately (didn't
> mean to be discouraging,
> > just wanted to be clear what's involved).  Hmm, I'd have to figure out a
> place to put them online,
> > not going to happen this week.  But feel free to start anywhere, if you
> produce a document that's
> > just
> >
> > CFJ XXXX:  [general principle]
> > CFJ YYYY:  [general principle]
> >
> > we'll find a home for it (or maybe Gaelan has other ideas on what would
> be useful?)
> > The FLR CFJ annotations are a good guide.  (even just getting those up
> to date is worth doing).
> >
> >> On Fri, 19 May 2017, Publius Scribonius Scholasticus wrote:
> >> I would be happy to help with this, if you would allow me to. How
> should I share the summaries with you?
> >>
> >> ----Publius Scribonius Scholasticus
> >>
> >> On Fri, May 19, 2017 at 5:07 PM, Kerim Aydin <ke...@u.washington.edu>
> wrote:
> >>
> >>
> >>
> >>>      On Fri, 19 May 2017, Publius Scribonius Scholasticus wrote:
> >>> I would be happy to help clean up the data and/or run a parser if you
> could explain what is needed?
> >>
> >>      It's more complicated than that, it's taking a specific judgement
> ("it's FALSE that Quazie
> >>      transferred a Shiny to me yesterday") and turning it into a
> general principle that can help
> >>      guide play ("Due to a conflict with Rule XXXX, players can't
> transfer shinies as described
> >>      in Rule YYYY").
> >>
> >>      Pretty much have to go through each judgement with thought, and
> figure out how to generalize
> >>      each result into a basic principle (for some it's easy, for others
> not so much).
> >
> >
>

Reply via email to