You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are files such as stoa0045.stoa003.perseus-lat2.xml where the xpath expression contains or operators: replacementPattern="#xpath(/tei:TEI/tei:text/tei:body/tei:div/tei:div/*[self::tei:div or self::tei:p or self::tei:l][@n='$1'])" : it is not clear to me exactly why, but it seems that who annotated used a sort of catch-all expression. This underspecification, however, causes a number of issues when extracting passages. My suggestion is that we avoid this and just specify one element.
The text was updated successfully, but these errors were encountered:
@gcelano
Review on this repo is underway so these sorts of irregularities will be addressed when the updates are made.
If there is something that requires more urgent work, I can do that between batches.
There is a lot here that is non-standard.
There are files such as
stoa0045.stoa003.perseus-lat2.xml
where the xpath expression containsor
operators:replacementPattern="#xpath(/tei:TEI/tei:text/tei:body/tei:div/tei:div/*[self::tei:div or self::tei:p or self::tei:l][@n='$1'])"
: it is not clear to me exactly why, but it seems that who annotated used a sort of catch-all expression. This underspecification, however, causes a number of issues when extracting passages. My suggestion is that we avoid this and just specify one element.The text was updated successfully, but these errors were encountered: