During the discussion of ID: 3496494, I raised an apparently somewhat controversial point with reference to the following statement:
"@from specifies the beginning of the passage being annotated; if not accompanied by a @to attribute, then specifies the entire passage." 
This statement licenses using the @from attribute as defining a span, rather than identifying the initial point thereof (as an innocent speaker of English would think). It seems to me that this is a rather evil example of attribute abuse, even if sanctified by use (is it?), maybe even more evil for that, because it opens the way to similarly abusing e.g. data.pointer attributes just because they are able to both identify points and identify ranges.
Instead of using the obligatory @from and optional @to, I would like to suggest introducing an obligatory choice: ( @from and @to ) OR @range
The new @range (data.pointer) attribute would do the same job as the @from is now (evilly) licensed to do, except without any abuse of the semantics. As it is now, actually, @from that refers to a series of characters (whatever they are enclosed in) is ambiguous: it may indicate that (1) some word that @from points at is the initial edge of a span, but unfortunately also (2) that the characters of that element *are* the span, and its interpretation would only depend on whether @to is missing. Introducing @range would remove this ambiguity.