Then maybe this rev. 3 has got it:
Referencing element
An element that identifies a referenced element in the value of an addressing attribute. The addressing attributes include href, conref, conrefend, keyref, conkeyref, mapref, longdescref, and anchorref. See referenced element. This term may also be used for an <object> element insofar as its archive, classid, and data attributes are used to specify the data, resources, and implementation of a non-XML object.
Referenced element
The element that a referencing element identifies in the value of one of the addressing attributes. The addressing attributes include href, conref, conrefend, keyref, conkeyref, mapref, longdescref, and anchorref. See referencing element.
ø¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø
Does this hook us into making "addressing attribute" a defined term? I hope we can stop with defining it locally like this.
I don't know if we actually use source/target anywhere that we talk about <object> (we don't seem to in the lang ref), but someone might use referring/referenced in the future. I omitted @codebase since it only sets a base URL to which the other URLs are relative (when that base URL is other than that of the current document).
Question:
The "text description of the graphic or object" that @longdescref references--is that text contained in a DITA element? If not (or if not necessarily) it might call for an "also used" sentence like that for @archive, etc.
