Comrade Angles utilise witches.town. Vous pouvez læ suivre et interagir si vous possédez un compte quelque part dans le "fediverse".
Comrade Angles @Angle

Hmm. Anyone have any suggestions for good primers on knowledge representation? I have a relatively complicated web of knowledge I want to write up for my games procedural generators and feel my current methods leave something to be desired. :/

@er1n Not sure what you mean. Can I get a link? :/

@er1n That might be useful for a personal reference, but I want something that I can use to store data that I feed into my program. :/

@Angle How about.. as a series of Agora 2866 nodes?

@Angle
What kind of knowledge are you trying to represent, specifically? (Like, predicates? Relations? Sets of possible details?)

@natecull is more likely to have specific recommendations for texts than I am, I think.

programming nonsense Afficher plus

programming nonsense Afficher plus

programming nonsense Afficher plus

programming nonsense Afficher plus

programming nonsense Afficher plus

programming nonsense Afficher plus

programming nonsense Afficher plus

programming nonsense Afficher plus

programming nonsense Afficher plus

programming nonsense Afficher plus

programming nonsense Afficher plus

@enkiv2 @Angle

I don't have a lot of recommendations because I'm still feeling my way around a similar problem. (Adventure games with semi-smart AI agents). I've resorted to Prolog, but it's not quite ideal.

You might find JSON is acceptable for small sets of data - worst case, you can probably just shove stuff in a big old array if it won't fit in an object.

Longterm, I think Lisp/Scheme is the most flexible for weird data sets, but it's hard to use.

Would love to know what works for you!

@natecull @enkiv2 I'm already using JSON. I was hoping maybe there'd be a better way? I'll look at prolog though, maybe it'll give me some ideas. Same with lisp/scheme. :/

@Angle @natecull
You're still going to be stuck listing these associations.

The benefit of Prolog, Lisp, and RDF is that you can use an off-the-shelf planner to navigate the associations and produce reasonable results.

The benefit of tracery is the above plus it's pretty compact (since it's json), but on the other hand you don't have backtracking.

@natecull @Angle
If your data is sufficiently general-purpose / matches well with reality, there are some data sets that might be able to fill in gaps.

OpenCYC is a project where, since the early 80s, a team of people have been writing an ontology for "common sense" in a scheme dialect. They're not done.

github.com/dariusk/corpora has some data sets that are more specific.

@Angle for most games and simulations things the data model will naturally gravitate towards "relational database lite" - like, unless you're specifically doing a tree or graph structure the most coherent option would be to use SQL and design a schema that fits boyce-codd normal form. But it's "lite" because practical systems are more ad-hoc and will hardcode their data structures and queries for optimization purposes.

(This also makes it a good target for code generation)

@Triplefox @Angle
+1 for a somewhat denormalised relational DB, loaded with data from spreadsheets

I like to mock up an editor UI before I go too crazy on the data model front.

You're talking about weapons, so you'll probably care about weapon balance. Traditionally spreadsheets work well for balancing - nice tabular format, formulas, graphs.