<refloc> Reference Location

<refloc> is a linking element that provides the location of a <ref> that is a resource in an extended link. It may occur within <daogrp> and <linkgrp>.

Attributes

  • ALTRENDER – not required. Use if the content of the element should be displayed or printed differently than the rendering established in a style sheet for other occurrences of the element.
  • AUDIENCE – not required. Use to set whether the element’s contents will be visible to external users or to internal ones. Possible values are: “internal” and “external.”
  • ID – not required. Creates an ID for element. Can be used for linking.
  • HREF – not required. The locator for a remote resource in a simple or extended link. An HREF takes the form of a Uniform Resource Identifier (URI). If no URI is specified, the locator is assumed to be within the document that contains the linking element.
  • LABEL – not required. May use a related name token.
  • LINKTYPE – fixed. Value must be “locator.”
  • ROLE – not required. Information that explains to application software the part that a remote resource plays in a link.
  • TARGET – not required. Points to the ID of another element. Must be an ID reference.
  • TITLE – not required. A viewable caption.
  • XPOINTER – not required. The locator for a remote resource in a simple or locator link. The XPOINTER attribute takes the form of a Uniform Resource Identifier plus a reference, formulated in XPOINTER syntax, to a sub-resource of the remote resource. XPOINTER enables linking to specific sections of a document that are relative, i.e., based on their position in the document or their content, rather than by reference to a specific identifier such as an ID.

Subelements

<refloc> may contain PCDATA as well as <abbr>, <address>, <blockquote>, <chronlist>, <corpname>, <date>, <emph>, <expan>, <extptr>, <famname>, <function>, <genreform>, <geogname>, <lb />, <list>, <name>, <note>, <num>, <occupation>, <origination>, <persname>, <ptr>, <repository>, <subject>, <table>, <unitdate>, and <unittitle>.

Examples

<archdesc level="collection">
	<did>[...]</did>
	<arrangement>
		<p>This collection is organized into two major sections.  The Original
		Gift portion reflects the materials originally donated to the Society by Mr.
		Provenance, while the Additions portion contains records transferred following
		his death.  As these two groups of documents have not been physically interfiled,
		materials on any given topic may appear in either or both sections, each of
		which is divided into four parallel series.
		<linkgrp>
			<refloc target="a9"></refloc>
			<refloc target="s1"></refloc>
			<refloc target="s7"></refloc>
		</linkgrp>
	</p>
	<p id="a9">Personal Correspondence></p>
	<p id="a10">Financial Records</p>
	<p id="a11">Diaries</p>
	<p id="a12">Literary Manuscripts</p>
	</arrangement>
	<dsc type="combined">
		<head>Original Gift</head>
		<c01 id="s1">
			<did>
				<unittitle>Personal correspondence, </unittitle>
				<unitdate>1917-1965.</unitdate>
			</did>
		</c01> . . .
	</dsc>
	<dsc type="combined">
		<head>Additions</head>
		<c01 id="s7">
			<did>
				<unittitle>Personal correspondence, </unittitle>
				<unitdate>1922-1945.</unitdate>
			</did>
		</c01> . . .
	</dsc>
</archdesc>

EAD tag library entry for <refloc>.