#36 Crosswalk issues

[BODARD Gabriel]

Various crosswalk issues need addressed:

(1) InsAph have invented a series of <rs> elements for
EAGLE/EDH compatibility; that this be generalised for
EpiDoc guidelines?

(2) Is crosswalk compatibility going to be compulsory?

(3) measurements in particular are going to need
special handling to be compatible with EDH.

[BODARD Gabriel]

Logged In: YES
user_id=597407

on (3) see GB's comments:

There are a couple of important issues with
measurements that need to be addressed in order to get
our crosswalks to (e.g.) EDH working. (1) is the fact
that in EDH the stone dimensions need to (a) be
literally numerical, and (b) a single number, not
multiple numbers, a range, circa, vel sim.;
(letter-heights, on the other hand, can be a text
field). (2) is the question of tagging the dimensions
within a single element--I'd strongly suggest <rs
type="dimensions">--so that it can be extracted by
the crosswalk wherever this data appears, even in the
teiHeader.

[BODARD Gabriel]

Logged In: YES
user_id=597407

Cf. 1472496 Measurements: ranges

[BODARD Gabriel]

I think this ticket is pretty obsolete.

The dimensions discussion is now at http://www.stoa.org/epidoc/gl/dev/supp-descdimensions.html

The crosswalk discussion is largely superceded by other documents (and will be surfaced in the Guidelines via the various appendices).