I realize that you’re still experimenting with markup and your schema, and that you still need to harmonize your markup decisions, but as you’re doing that, please also harmonize your filenames. For example, it isn’t an error (that is, it doesn’t raise an error message and cause your processing to burst into flames) to have the names of some poems begin with a lowercase letter and others with an uppercase letter. But it’s nonetheless a mistake because that makes it harder for human developers to keep track of what they’re doing. For example, some filesystems are case-sensitive, so raven.xml and Raven.xml would be different files, and they could co-exist in the same directory, while in other files one would overwrite the other. Your specific filename convention is up to you (except for the usual avoidance of spaces and most punctuation in filenames), but you’ll want to follow a consistent protocol.
I realize that you’re still experimenting with markup and your schema, and that you still need to harmonize your markup decisions, but as you’re doing that, please also harmonize your filenames. For example, it isn’t an error (that is, it doesn’t raise an error message and cause your processing to burst into flames) to have the names of some poems begin with a lowercase letter and others with an uppercase letter. But it’s nonetheless a mistake because that makes it harder for human developers to keep track of what they’re doing. For example, some filesystems are case-sensitive, so raven.xml and Raven.xml would be different files, and they could co-exist in the same directory, while in other files one would overwrite the other. Your specific filename convention is up to you (except for the usual avoidance of spaces and most punctuation in filenames), but you’ll want to follow a consistent protocol.