Menu
News
All News
Dungeons & Dragons
Level Up: Advanced 5th Edition
Pathfinder
Starfinder
Warhammer
2d20 System
Year Zero Engine
Industry News
Reviews
Dragon Reflections
White Dwarf Reflections
Columns
Weekly Digests
Weekly News Digest
Freebies, Sales & Bundles
RPG Print News
RPG Crowdfunding News
Game Content
ENterplanetary DimENsions
Mythological Figures
Opinion
Worlds of Design
Peregrine's Nest
RPG Evolution
Other Columns
From the Freelancing Frontline
Monster ENcyclopedia
WotC/TSR Alumni Look Back
4 Hours w/RSD (Ryan Dancey)
The Road to 3E (Jonathan Tweet)
Greenwood's Realms (Ed Greenwood)
Drawmij's TSR (Jim Ward)
Community
Forums & Topics
Forum List
Latest Posts
Forum list
*Dungeons & Dragons
Level Up: Advanced 5th Edition
D&D Older Editions, OSR, & D&D Variants
*TTRPGs General
*Pathfinder & Starfinder
EN Publishing
*Geek Talk & Media
Search forums
Chat/Discord
Resources
Wiki
Pages
Latest activity
Media
New media
New comments
Search media
Downloads
Latest reviews
Search resources
EN Publishing
Store
EN5ider
Adventures in ZEITGEIST
Awfully Cheerful Engine
What's OLD is NEW
Judge Dredd & The Worlds Of 2000AD
War of the Burning Sky
Level Up: Advanced 5E
Events & Releases
Upcoming Events
Private Events
Featured Events
Socials!
EN Publishing
Twitter
BlueSky
Facebook
Instagram
EN World
BlueSky
YouTube
Facebook
Twitter
Twitch
Podcast
Features
Top 5 RPGs Compiled Charts 2004-Present
Adventure Game Industry Market Research Summary (RPGs) V1.0
Ryan Dancey: Acquiring TSR
Q&A With Gary Gygax
D&D Rules FAQs
TSR, WotC, & Paizo: A Comparative History
D&D Pronunciation Guide
Million Dollar TTRPG Kickstarters
Tabletop RPG Podcast Hall of Fame
Eric Noah's Unofficial D&D 3rd Edition News
D&D in the Mainstream
D&D & RPG History
About Morrus
Log in
Register
What's new
Search
Search
Search titles only
By:
Forums & Topics
Forum List
Latest Posts
Forum list
*Dungeons & Dragons
Level Up: Advanced 5th Edition
D&D Older Editions, OSR, & D&D Variants
*TTRPGs General
*Pathfinder & Starfinder
EN Publishing
*Geek Talk & Media
Search forums
Chat/Discord
Menu
Log in
Register
Install the app
Install
Upgrade your account to a Community Supporter account and remove most of the site ads.
Community
General Tabletop Discussion
*Geek Talk & Media
d20Engine: Core Mechanic
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="JBowtie" data-source="post: 2144450" data-attributes="member: 1810"><p>Hi, joining this from the other thread. Semi-random comments follow.</p><p></p><p>I don't yet have a formal ontology for my project (using generic RDF at the moment) but it is pretty clearly the right way to go. If someone wants to propose or generate one, that would be a good place to start analysis - but not necessarily here on the forum.</p><p></p><p>1) AI engines consume RDF (and, by extension, OWL). For our purposes, that means we can feed rules into an engine to detect contradictions and discover implicit relationships.</p><p></p><p>2) RDF understands URLs and can be written as XML, so rules can be scattered around the web and still be pulled together.</p><p></p><p>3) It's perfectly fine to start concrete work with raw XML and later turn it into RDF. Just use URLs as the rule identifiers, and hrefs to refer to rules. So brainstorming stuff in XML works just fine.</p><p></p><p>4) Not everything needs to be defined in the core ontology, and we should ignore stuff that is not in the SRD for the initial version. Future work can extend and generalize.</p><p></p><p>To elaborate on the last point - I don't think we need to generalize the core mechanic. Every program can (and probably will) hard-code that assumption. I don't have any books that require dice pools, and when I get one I can owl:import the core ontology and create some new terms and relationships. Unlike OO programming, I can retroactively add superclasses and properties.</p><p></p><p>On language choices, everyone is entitled to their own opinion. I think initially it would make sense to use Python because:</p><p>1) It's cross-platform.</p><p>2) It's dynamic - early on we'll do lots of prototyping and refactoring; having static types will trip up people.</p><p>3) Code snippets are short and readable.</p><p>4) A lot of the existing RDF/OWL tools are written in Python, short-circuiting the parser problem. Sparta in particular is a cool little library.</p><p></p><p>For collaboration, a wiki makes the most sense. I'll put together a wiki, mailing list, and source code repository this weekend if no one else has done so by then (space on my website permitting).</p></blockquote><p></p>
[QUOTE="JBowtie, post: 2144450, member: 1810"] Hi, joining this from the other thread. Semi-random comments follow. I don't yet have a formal ontology for my project (using generic RDF at the moment) but it is pretty clearly the right way to go. If someone wants to propose or generate one, that would be a good place to start analysis - but not necessarily here on the forum. 1) AI engines consume RDF (and, by extension, OWL). For our purposes, that means we can feed rules into an engine to detect contradictions and discover implicit relationships. 2) RDF understands URLs and can be written as XML, so rules can be scattered around the web and still be pulled together. 3) It's perfectly fine to start concrete work with raw XML and later turn it into RDF. Just use URLs as the rule identifiers, and hrefs to refer to rules. So brainstorming stuff in XML works just fine. 4) Not everything needs to be defined in the core ontology, and we should ignore stuff that is not in the SRD for the initial version. Future work can extend and generalize. To elaborate on the last point - I don't think we need to generalize the core mechanic. Every program can (and probably will) hard-code that assumption. I don't have any books that require dice pools, and when I get one I can owl:import the core ontology and create some new terms and relationships. Unlike OO programming, I can retroactively add superclasses and properties. On language choices, everyone is entitled to their own opinion. I think initially it would make sense to use Python because: 1) It's cross-platform. 2) It's dynamic - early on we'll do lots of prototyping and refactoring; having static types will trip up people. 3) Code snippets are short and readable. 4) A lot of the existing RDF/OWL tools are written in Python, short-circuiting the parser problem. Sparta in particular is a cool little library. For collaboration, a wiki makes the most sense. I'll put together a wiki, mailing list, and source code repository this weekend if no one else has done so by then (space on my website permitting). [/QUOTE]
Insert quotes…
Verification
Post reply
Community
General Tabletop Discussion
*Geek Talk & Media
d20Engine: Core Mechanic
Top