That is (examples taken from the latest XLink 1.1 spec),
<go ... xlink:arcrole="http://www.example.com/linkprops/auditor" ...>
<my:crossReference ... xlink:role="http://www.example.com/linkprops/studentlist" ...>
what could the content of the http://www.example.com/linkprops/studentlist resource be?
Is it totally arbitrary, only constrained by the developer/platform/etc, or does it have to have a specific format (e.g., XML, conforming to a specific schema, etc.)?
Based on the quote below, I would say that it is arbitrary, but I couldn't find any examples yet:
Also, from XML in a Nutshell, 2nd Edition:
-
[..] this URI should point to a resource that indicates which relationship the arc describes (e.g., parent-child, employer-employee). For instance, we might add an
xlink:arcroleattribute to the purchase arc that pointed to the URLhttp://www.example.com/purchase_details.txt. The filepurchase_details.htmlmight then contain the text "will be bought from." This would indicate that the source of the link is bought from the target of the link; that is, "The Wonderful Wizard of Oz will be bought from Amazon", or "The Wonderful Wizard of Oz will be bought from Fatbrain", or "The Wonderful Wizard of Oz will be bought from Barnes & Noble". However, although this usage is suggested, XLink processors will not enforce it, and indeed there's really no way they could be asked to do this since that would require that they actually understand what they read. -
Although can't fathom how the example links, such as http://www.williammorrow.com, are useful as roles at all.
Some mentions from the spec:
-
the role attribute indicates a property that the entire link has
Section 5.5 Semantic Attributes (role, arcrole, and title) states that "The value of the
roleorarcroleattribute is a [Legacy extended IRIs]. The identifier must not be relative."Section 5.1.3 Traversal Rules for an Extended Link (arc-Type Element) brings a specific example that "a resource might generically represent a "person," but in the context of a particular arc it might have the role of "mother" and in the context of a different arc it might have the role of "daughter"." But how does these translate to an URI?
(It also doesn't help that the same section uses "roles" interchangeably with "labels"...)
Some other sites I've found:
Peter Egri: Overview on XLink
No examples, but it is good summary.http://www.brenkoweb.com/tutorials/xml/xml-xlink-xml-linking/xlink-attributes
https://www.brainbell.com/tutorials/XML/Linking_With_XLink.htm
Both of these provide examples torolewith simple strings (e.g., "employee") so they are not normative.
Found the answer in the 3rd edition of XML in a Nutshell, Link Semantics chapter: