Here’s an edited for content and length, but not the size of your tv, log of my talk with Graham, RE: map-time genesis:
(21:19:22) Matt J Alexander: also: I need a hip, pomo name.
(21:19:34) Matt J Alexander: Because a project without a name is nothing.
(21:19:49) Graham: will, you could insert meta into the title
(21:20:07) Graham: mapistry?
(21:21:19) Graham: metamap
(21:21:41) Graham: maplysses
(21:22:09) Matt J Alexander: hrm.
(21:22:25) Matt J Alexander: maplysses is interesting, but syntatically vague on proper pronunciation
(21:22:57) Graham: mapberto eco
(21:23:59) Matt J Alexander: I like the direction this is going in
(21:24:48) Graham: 100 years of map solitude
(21:25:05) Graham: maptavio paz
(21:25:39) Graham: maps joyce
(21:27:29) Matt J Alexander: So the current implementation idea is based on Event atom (or class,or whatever).
(21:27:49) Ravelite: ok, so an event moves a border then?
(21:27:58) Matt J Alexander: A border would be an Event.
(21:28:12) Matt J Alexander: An Event can be one or more Events, or a vector/tuple.
(21:28:19) Matt J Alexander: Vector being:
(21:28:38) Ravelite: ahhhh, so a border event is a vector of border vertices
(21:28:59) Matt J Alexander: {(where: GIS date[lat.,long.elev.]), time, country/tribe, person, short/long descriptions, causes, image/connector images, accuracy}
(21:29:05) Ravelite: so events have a limited time of validity,
(21:29:13) Ravelite: and are replaced by more current ones?
(21:29:27) Matt J Alexander: Yeah. I’m not sure if this is covered by accuracy or would need something like "lifespan"
(21:29:41) Ravelite: Well, probably you don’t need lifespan,
(21:29:46) Ravelite: just chose the most recent.
(21:29:51) Matt J Alexander: I’m also not sure if this ends up with overly large dataset.
(21:29:56) Ravelite: that partitions the timelime well enough
(21:30:07) Matt J Alexander: Since a border would necessitate several events as points just to define all the curves.
(21:30:15) Ravelite: yes
(21:30:42) Matt J Alexander: Is there a more elegant way, or can I just fall back on the mantra of SPACE IS CHEAP, TIME IS EXPENSIVE
(21:31:10) Ravelite: Well, go for simplest to make a prototype.,
(21:31:18) Ravelite: avoid premature optimization
(21:31:28) Ravelite: assume you will throw away this prototype
(21:32:08) Matt J Alexander: Historically, are even the most ardously planned out prototypes thrown out?
(21:32:19) Matt J Alexander: Or do arduously planned prototypes just never get created :p
(21:32:38) Ravelite: well, it’s just one of my design philosophies
(21:32:48) Ravelite: I just think it’s hardest to create something from the start
(21:32:50) Matt J Alexander: One Luke shares
(21:32:59) Ravelite: and you will learn many obvious things once it is build
(21:33:07) Ravelite: that you can’t imagine about right now
(21:33:12) Matt J Alexander: True: certainly I don’t have any domain knowledge about mapping currently
(21:33:25) Matt J Alexander: And only barely so in history
(21:33:39) Ravelite: I agree with your point, the more planning, the harder to do and the greater chance it doesn’t happen
(21:33:59) Ravelite: and most planning will be made irrelevant unless you know a lot about the domain
(21:34:08) Ravelite: and since your app is highly experimental,
(21:34:18) Ravelite: almost no one knows about the domain right now