Reply to thread

Message

<blockquote data-quote="JamisBuck" data-source="post: 347942" data-attributes="member: 12">Keep in mind that the CADD document is only a very (VERY) partial reference document that refers to a very (VERY) specific problem domain.&nbsp; Also, please keep in mind that, right now, with these discussions, I am actually not trying to write any software.&nbsp; I only trying to define an abstract system that describes not only d20 characters, but also things university students and users of software.&nbsp; Once the properties of these &quot;entities&quot; are known in general, it becomes possible to create either a pseudo-random generator of those entities, or a user-directed generator of those entities, or a mix of the two.It sounds to me that one of your concerns is with validating the data, Sm!rk.&nbsp; However, the data that defines the entity, also defines the valid possibilities that define the entity.&nbsp; I'm talking not just about data, but about metadata.&nbsp; The logic that interprets the data, then, must make sure that any attempt at generating an entity keeps everything within the constraints defined by the metadata.&nbsp; It works in a way similar to how databases prevent you from inserting records with duplicate keys, or (for databases that enforce referential integrity) from deleting a record that other records refer to.&nbsp; The metadata in the database makes sure that illegal operations on the data are not allowed.Sorry I didn't address all your points, Sm!rk, but my son is requiring some supervision and I need to sign off. <img src="https://cdn.jsdelivr.net/joypixels/assets/8.0/png/unicode/64/1f642.png" class="smilie smilie--emoji" loading="lazy" width="64" height="64" alt=":)" title="Smile&nbsp; &nbsp; :)"&nbsp; data-smilie="1"data-shortname=":)" /></blockquote>

[QUOTE="JamisBuck, post: 347942, member: 12"] Keep in mind that the CADD document is only a very (VERY) partial reference document that refers to a very (VERY) specific problem domain. Also, please keep in mind that, right now, with these discussions, I am actually not trying to write any software. I only trying to define an abstract system that describes not only d20 characters, but also things university students and users of software. Once the properties of these "entities" are known in general, it becomes possible to create either a pseudo-random generator of those entities, or a user-directed generator of those entities, or a mix of the two. It sounds to me that one of your concerns is with validating the data, Sm!rk. However, the data that defines the entity, also defines the valid possibilities that define the entity. I'm talking not just about data, but about [i]meta[/i]data. The logic that interprets the data, then, must make sure that any attempt at generating an entity keeps everything within the constraints defined by the metadata. It works in a way similar to how databases prevent you from inserting records with duplicate keys, or (for databases that enforce referential integrity) from deleting a record that other records refer to. The metadata in the database makes sure that illegal operations on the data are not allowed. Sorry I didn't address all your points, Sm!rk, but my son is requiring some supervision and I need to sign off. :) [/QUOTE]

Verification