Reply to thread

Message

<blockquote data-quote="JBowtie" data-source="post: 2142282" data-attributes="member: 1810">Here's an example of how I would model the &quot;+1 vs goblinoids&quot; so it can be resolved by an engine. This is off the top of my head and probably won't withstand closer analysis.First, we'll need to define a goblinoid. Note that this could actually be an anonymous class defined as part of the bonus rather than a named class as in the example.If something has creature subtype goblin and is a humanoid, we're calling it a goblinoid. A more accurate definition would use oneOf to enumerate the full list of subtypes IIRC.[CODE]&lt;owl:Class rdf:ID=&quot;http://example.org/srd#goblinoid&quot;&gt;&nbsp; &lt;owl:intersectionOf rdf:parseType=&quot;Collection&quot;&gt;&nbsp; &nbsp; &lt;owl:Class rdf:about=&quot;http://example.org/srd#humanoid&quot;&gt;&nbsp; &nbsp; &lt;owl:Restriction&gt;&nbsp; &nbsp; &nbsp; &lt;owl:onProperty rdf:resource=&quot;http://example.org/core#creatureSubtype&quot; /&gt;&nbsp; &nbsp; &nbsp; &lt;owl:hasValue rdf:resource=&quot;http://example.org/srd#goblin&quot; /&gt;&nbsp; &nbsp; &lt;/owl:Restriction&gt;&nbsp; &lt;/owl:intersectionOf&gt;&lt;/owl:Class&gt;[/CODE]Now, let's define the bonus. It's anonymous as it will typically be defined as part of some other rule, such as a racial trait.[CODE]&lt;core:Bonus&gt;&nbsp; &nbsp; &lt;core:appliesTo resource=&quot;http://example.org/core#attack&quot; /&gt;&nbsp; &nbsp; &lt;core:type resource=&quot;http://example.org/srd#racial&quot; /&gt;&nbsp; &nbsp; &lt;core:Condition&gt;&nbsp; &nbsp; &nbsp; &nbsp; &lt;rdfs:label&gt;vs goblinoids&lt;/rdfs:label&gt;&nbsp; &nbsp; &nbsp; &nbsp; &lt;core:conditionType rdf:resource=&quot;http://example.org/core#runtime&quot; /&gt;&nbsp; &nbsp; &nbsp; &nbsp; &lt;srd:goblinoid&gt;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &lt;runtime:Role rdf:about=&quot;http://example.org/core#target&quot; /&gt;&nbsp; &nbsp; &nbsp; &nbsp; &lt;/srd:goblinoid&gt;&nbsp; &nbsp; &lt;/core:Condition&gt;&nbsp; &nbsp; &lt;core:formula&gt;1&lt;/core:formula&gt;&lt;/core:Bonus&gt;[/CODE]So, at runtime, when a creature of subtype goblinoid is assigned the &quot;target&quot; role relative to the character, the formula is evaulated and applied to the attack roll subject to stacking rules for bonus types.Here, I'm telling the processor this condition can be checked at runtime. If, at that time, there is a goblinoid with the 'target' role, apply this bonus.Some conditions can realistically only be evaluated by a DM (see the preqs for assassins, for example). For those I would stick with a simple text description like my original example.Now, this is a lot of work, so I'm sticking to a small, well-defined ontology to begin with (stuff in the &quot;core&quot; namespace, above), and building tools to extend the ontologies on top of that. So all the stuff in the SRD namespace would be the result of using my BookBuilder application. Definitions like goblinoid can be built by example rather than typed out (I haven't even thought about the book builder UI yet).</blockquote>

[QUOTE="JBowtie, post: 2142282, member: 1810"] Here's an example of how I would model the "+1 vs goblinoids" so it can be resolved by an engine. This is off the top of my head and probably won't withstand closer analysis. First, we'll need to define a goblinoid. Note that this could actually be an anonymous class defined as part of the bonus rather than a named class as in the example. If something has creature subtype goblin and is a humanoid, we're calling it a goblinoid. A more accurate definition would use oneOf to enumerate the full list of subtypes IIRC. [CODE] <owl:Class rdf:ID="http://example.org/srd#goblinoid"> <owl:intersectionOf rdf:parseType="Collection"> <owl:Class rdf:about="http://example.org/srd#humanoid"> <owl:Restriction> <owl:onProperty rdf:resource="http://example.org/core#creatureSubtype" /> <owl:hasValue rdf:resource="http://example.org/srd#goblin" /> </owl:Restriction> </owl:intersectionOf> </owl:Class> [/CODE] Now, let's define the bonus. It's anonymous as it will typically be defined as part of some other rule, such as a racial trait. [CODE] <core:Bonus> <core:appliesTo resource="http://example.org/core#attack" /> <core:type resource="http://example.org/srd#racial" /> <core:Condition> <rdfs:label>vs goblinoids</rdfs:label> <core:conditionType rdf:resource="http://example.org/core#runtime" /> <srd:goblinoid> <runtime:Role rdf:about="http://example.org/core#target" /> </srd:goblinoid> </core:Condition> <core:formula>1</core:formula> </core:Bonus> [/CODE] So, at runtime, when a creature of subtype goblinoid is assigned the "target" role relative to the character, the formula is evaulated and applied to the attack roll subject to stacking rules for bonus types. Here, I'm telling the processor this condition can be checked at runtime. If, at that time, there is a goblinoid with the 'target' role, apply this bonus. Some conditions can realistically only be evaluated by a DM (see the preqs for assassins, for example). For those I would stick with a simple text description like my original example. Now, this is a lot of work, so I'm sticking to a small, well-defined ontology to begin with (stuff in the "core" namespace, above), and building tools to extend the ontologies on top of that. So all the stuff in the SRD namespace would be the result of using my BookBuilder application. Definitions like goblinoid can be built by example rather than typed out (I haven't even thought about the book builder UI yet). [/QUOTE]

Verification