TEI Stand-Off Markup WG 2002-09-19 Conference Call Notes

Agenda inadvertantly not sent to list.

Business from previous call; cryptic point in minutes about time-based stuff — DD says yes at some point not today.

FV: 1. Claudio Tasso got master's degree hours ago — congratulations from group.

FV: 2. some XLST++ info has just been posted to list w/o waiting for full paper. [Yay!]

DD wants us to redo deliverables as a list, and thinks that things listed as ‘low priority’ should just be, for now, out. Thus tutorials out.

DD suggesting using XPointer as value of, say, next= and prev=

FV does not like putting XPointer stuff anywhere other than href= of an XLink; DD argues that, esp. in case of next= & prev=, they are really not like any standard hpertext link, and thus an XLink not as apropos.

JH asks about how you use ana= in SOM.

Do we consider XPointer as replacement for all ID/IDREFs?

DD: advantage is that we can now avoid the step of indirection needed if the target is in an external document.

Also processors do not need to go find the DTD. [??]

Problem: only 1 href= attr per XLink, so we can't handle all of 'em. Some solutions include keeping indirection, making 'em subelements, using XPointer instead of IDREFs w/o XLink.

FV: proposes that ID/IDREF should be replaced with URIs; only those attrs that really have notion of linking to external document are expressed as full XLink. DD agrees would not want to use URIs w/o XPointer.