search

Multi-User-Domain / mud-jena

0 stars 0 forks source link

TransitDescriber #10

Open calummackervoy opened 3 years ago

calummackervoy commented 3 years ago

Requires #3 to be resolved first

The end goal is to be able to request a description for my Transit task, and receive back some content of what I see as I travel

Probably to start with this will look at the destination and generate random events based on that, pulling from a content dataset

Populating such a dataset would be a lot easier with Fuseki. I've also been having a look at AtomGraph's solution and it looks promising (see https://github.com/Multi-User-Domain/LinkedDataHub)

At some point it would be awesome to have it consider the mode of transport, and the progress made in the transit (e.g. knowing that I will currently be walking through woodland), but this will require hefty changes to other features so should be left out of scope for now

calummackervoy commented 3 years ago

generate random events based on that

We're shifting from describers generating events to having a buildScene stage generate events before the describer process. I think that this will change the design of this one, too

calummackervoy commented 3 years ago

We could add an inTransit property to the character, a sub-property of hasTask

This will be useful when describing characters ("they are travelling somewhere")

Of course we could do this by getting the object at the end of hasTask (a sensible default to try if I don't know). Getting the property would be faster