4 of the 5 attributes provided by att.ranging have the word “measurement” in their definitions. Yet, to my surprise, <measure> is not a member! (The members of att.ranging are [1], but some of those really should be removed from this class. See #299, which I just realized is still assigned to me, but probably should be assigned to @hcayless.)
Seems to me it is important to be able to express ranges with <measure>. Take the phrase
provided more than $120m in aid to Ukrainians
(something I just found on the web). If you are encoding measurements of money in this corpus, you can easily say
… provided more than <measure unit="USD" commodity="currency" quantity="120000000">$120m</> in aid to Ukrainians.
But if you want to encode it as a limit (perhaps for comparisons to other contributions), you can’t say
… provided <measure unit="USD" commodity="currency" atLeast="120000000">more than $120m</> in aid to Ukrainians.
4 of the 5 attributes provided by att.ranging have the word “measurement” in their definitions. Yet, to my surprise,
<measure>is not a member! (The members of att.ranging are [1], but some of those really should be removed from this class. See #299, which I just realized is still assigned to me, but probably should be assigned to @hcayless.)Seems to me it is important to be able to express ranges with
<measure>. Take the phrase(something I just found on the web). If you are encoding measurements of money in this corpus, you can easily say
But if you want to encode it as a limit (perhaps for comparisons to other contributions), you can’t say
That seems silly to me.
Notes [1]
<add>,<addSpan>,<age>,<birth>,<damage>,<damageSpan>,<date>,<death>,<del>,<delSpan>,<depth>,<dim>,<dimensions>,<ellipsis>,<ex>,<floruit>,<gap>,<geogFeat>,<height>,<mod>,<num>,<offset>,<origDate>,<population>,<precision>,<redo>,<restore>,<retrace>,<secl>,<space>,<state>,<subst>,<substJoin>,<supplied>,<surplus>,<time>,<trait>,<unclear>,<undo>, and<width>.