Juan wrote:
So…
I've been recording the happenings relevant to the Registrar and
Absurdor in a JSON format for years now. They share a common format,
but each has some specificities. I decided to try and transform this
into a specification.
I want to gauge enthusiasm for this sort of thing. Note that I am not
saying that the specs should be included in the rules or whatever. It's
just something I find interesting, and might be useful for other people.
If you want to check it out, take a look at the repo:
https://juanmeleiro.mat.br/git/agoran-logs-spec/log.html
There is sample data in both the Absurdor and Registrar repos.
I an excitedly waiting for responses.
Thanks!
Seems straightforward enough.
My web pages for ADoP and Tailor (linked from the agoranomic.org
subdomains) include JSON exports, which are just direct data dumps
from the underlying PostgreSQL tables. Exporting something complying
with this spec would look something like:
select
cast(extract(epoch from e.event_timestamp) as integer) as when,
'https://johnpeters.us.to/adop/event_details.json?event_id='
+ cast(e.event_id as varchar) as what,
p.player_name as who,
e.event_id as seq
from events e
left join players p on p.player_id = e.acting_player_id;
events.event_id indicates the order in which I recorded events, so it's
not always in chronological order across the board - I have separate
local folders for a-b and a-o, and generally process a-b first - but
should always be in chronological order for events within a single
message.
There's currently no record of Message-Id values, hence the omission of
'where'.
I also wondered if "log of historical events" was something common
enough to already have a widely-used global spec, but a quick web search
only turned up one (CloudEvents) that's apparently geared toward message
queues, and another geared toward calendar events (with attributes like
duration and physical location).
--
[ANSC H:GE V:G B:0]
