I don’t want to overstretch this post, but I came across something while starting my first story I’d like to share. It may be obvious for others, but for me it wasn’t.
Object names are global (as seen above, chapters help to resolve unwanted ambiguities automatically - to be honest, I’d prefer some kind of warning instead or additionally), but when it comes to the parser interpreting the player’s commands, there is some ‘locality’. For example, I can say the following without introducing an ambiguity (my point is the part about understand "bed" as):
Furniture is a kind of thing.
Lab is a room.
The camp bed is furniture in the Lab. Understand "bed" as camp bed.
Tent is a room.
The divan bed is furniture in the Tent. Understand "bed" as divan bed.
test me with "x bed".
Has the result:
Lab
You can see a camp bed here.
>x bed
You see nothing special about the camp bed
It’s absolutely logical that “bed” is evaluated in the player’s context (the room that he or she is in), but to me it wasn’t clear from the beginning that I7 handles that for me.