Features, Resources and Datasets

David Thomas

Perhaps some anxiety could be cleared up if we were all using the same definitions.

I read often in the last week "I don't want (can't afford) any more resources, I just want all the features" (I believe some of this will get even more confusing when the crossgrade(s) are released if we don't understand some common terms!) A went off for me when I learned that Logos considers "datasets" to be "resources"

A user will read something like "L5 will list every time a person is the direct object of a particular verb" and thinks this is a "feature" but doesn't realize that the ability to do this depends upon having a particular "resource" [sidenote: I can search for the word "Timothy" but can't search each time the pronoun "him" refers to Timothy in Scripture. Logos has paid a team to go through and manually made a list (called a DATASET) of each pronoun and who it refers to]

So a user reads the bold text in the last paragraph and thinks "I should be able to generate a list of every time Timothy is the direct object of 'to obey' as a FEATURE of the program." The problem is that to do this requires that the pronoun DATASET is in place. If the DATASET is considered a "resource" and the user doesn't want to [or can't] pay for additional resources then he can't use the feature.

Logos has already stated that they will offer a free ENGINE but has yet to decide which DATASETS they are willing to give away or sell cheap so that FEATURES can be implemented. 

By analogy, my truck has an engine that runs, but my truck doesn't go anywhere unless wheels are on the axels. Wheels  are not part of the engine, but are essential for the vehicle to move. But does that mean that the manufacturer is expected to provide basic functional wheels of some type, or are they expected to put on the 21" custom Chrome Mag wheels with knobby Mudding tires on each truck?