revise class hierarchy considering paragraphs and sentences

[kosloot]

At the moment, the accepted data considering sentence and/or paragraph is a bit rigid and unclear

For example:
A Caption may contain a Sentence, but not a Paragraph.
But that means that it also may contain several Sentences.
But isn't that just a Paragraph?

An Entry may NOT contain Sentence or Paragraph, but it may contain a Term, which may contain both.

An Utterance may contain a Sentence, but not a Paragraph, which somehow makes sense, but it may contain a Quote too, which accepts both.

The ratio is unclear to me.

[kosloot]

This is related to: LanguageMachines/ucto#40

[proycon]

I made it a bit more flexible, but that comes at a risk too, something I don't want to allow but which we currently can't enforce yet is a pattern like (xpath): //p/somethingelse/p

[kosloot]

Yeah. There are several 'fair use' or 'sensible' policies for FoLiA, but enforcing them can be troublesome.
I'm not sure if DTD's or XmlSchema can rule this.
Otherwise we could implement some run-time checks.
e.g checking whether a <p> is embedded directly or indirectly in another <p> is not that hard.
Maybe MOST tags cannot be 'recursive'. So maybe we could make a property that allows this for the few that can? <div> comes to mind. <part> maybe?