. . . "Recommended best practice is to identify the related resource by means of a string conforming to a formal identification system. "@en-us . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . "2008-01-14"^^ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . "Relation"@en-us . . . . . . . . . "A related resource."@en-us . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . "Recommended practice is to identify the related resource by means of a URI. If this is not possible or feasible, a string conforming to a formal identification system may be provided."@en . . . . . . . "2008-01-14" . . . . . . . . . . . . . . . . . . . . . . . . . . . . "A related resource."@en . . . . . . . . . . . . . . . . . . . . . . . . . . . "2008-01-14" . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . "Relation"@en . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . "This term is intended to be used with non-literal values as defined in the DCMI Abstract Model (http://dublincore.org/documents/abstract-model/). As of December 2007, the DCMI Usage Board is seeking a way to express this intention with a formal range declaration."@en-us . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .