]>
XLink Demo - Extended Links

Camera ABC

Photo: Camera Model ABC

Example of extended XLinks

The XLink code behind the links from the left side (colored in blue) is detailed in the right side.

The root element must have declared the xlink namespace:

<DOC xmlns:xlink="http://www.w3.org/1999/xlink"> ..... </DOC>
Resolution 2,240 x 1,680 pixels (interpolated) 1,856 x 1,392 pixels 1,856 x 1,232 pixels 1,280 x 960 pixels 640 x 480pixels Goes from one locator (point/element) to another. The starting point of the link will be #resolution. The extended link is declared somewhere in this document and looks like this: <link xlink:type="extended"> <a-loc xlink:type="locator" xlink:label="resolution-spec" xlink:href="specs.xml#resolution"/> <a-loc xlink:type="locator" xlink:label="resolution" xlink:href="#resolution"/> <an-arc xlink:type="arc" xlink:from="resolution" xlink:to="resolution-spec" xlink:title="What is resolution all about?"/> </link> Now there is need only for an element to match the xlink:from locator. And we have here: <text id="resolution">Resolution</text>
Standard connection Yes. See Other connectors A link from one element(a resource) to another(a locator) and viceversa, declared with two arcs. The locator's target is an element with id="other-connectors" being at the end of this document. <extlink xlink:type="extended"> <res xlink:type="resource" xlink:label="point1">Other connectors</res> <loc xlink:type="locator" xlink:label="point2" xlink:href="#other-connectors"/> <arc xlink:type="arc" xlink:show="replace" xlink:from="point2" xlink:to="point1" xlink:title="Back to Standard connection"/> <arc xlink:type="arc" xlink:show="replace" xlink:from="point1" xlink:to="point2" xlink:title="Go to Other connections"/> </extlink>
Image sensor 1/1.8" CCD chip with 3,340,000 pixels See also Device C specification There can be created links in other docs then this one without touching them, because the links are declared here. Now, in deviceC.xml there is a link to be found at this location -> deviceC.xml#xpointer(/1/2/3/1). The target of this link is a local resource from here (extended.xml) pointing to "Image sensor" subtitle from the left. <extlink xlink:type="extended"> <loc xlink:type="locator" xlink:label="extern_start" xlink:href="deviceC.xml#xpointer(/1/2/3/1)"/> <loc xlink:type="resource" xlink:label="localresource">Image sensor</loc> <arc xlink:type="arc" xlink:from="extern_start" xlink:to="localresource" xlink:title="Go to Camera Image sensor specification"/> </extlink>
Image format JPEG (.jpg), TIFF (.tif) or MPEG video (.mpg) The link from the left side opens the video.xml document which will popup a new window with a document containing the history of the video electronics. This is similar to simple XLinks with actuate="onLoad" and show="new". The difference is that in video.xml we have an extended XLink. The code in video.xml file looks like this: <extlink xlink:type="extended"> <loc xlink:type="locator" xlink:label="targetdocument" xlink:href="video-history.xml"/> See also the new window just opened with <res xlink:type="resource" xlink:label="locallink">the history of the video electronics</res>. <arc xlink:type="arc" xlink:from="locallink" xlink:to="targetdocument" xlink:actuate="onLoad" xlink:title="See also the history document"/> </extlink>
Internal flash memory no We want to create 2 links when Flash Memory Documentation file is oppened. Both links will have 2 target choises. For example, when clicked on "Compact Flash" type of memory from flashmem.xml file we want to have the option of choosing a camera, that uses that type of memory, to be redirected to. The 2 multiple links will be created by this code being in flashmem.xml: <ext xlink:type="extended"> <loc xlink:type="locator" xlink:label="end" xlink:href="deviceA.xml" xlink:title="Device A"/> <loc xlink:type="locator" xlink:label="end" xlink:href="deviceB.xml" xlink:title="Device B"/> <loc xlink:type="locator" xlink:label="start" xlink:href="flashmem.xml#cf" xlink:title="Compact Flash Memory"/> <loc xlink:type="locator" xlink:label="start" xlink:href="resolution.xml#1mp" xlink:title="1 Megapixel Resolution"/> <arc xlink:type="arc" xlink:from="start" xlink:to="end" xlink:show="replace" xlink:actuate="onRequest" xlink:title="Choose from multiple camera specifications"/> </ext>
Removable memory Memory Stick . 8 Mbyte removable memory media included. Inserted in the left side of the camera. The link from the left will popup 3 windows with types of memory sticks that wanted to be shown (recomended/in stock/available). The code behind: <ext xlink:type="extended"> <loc xlink:type="resource" xlink:label="here">Memory Stick</loc> <loc xlink:type="locator" xlink:label="memstick_doc" xlink:href="stickA.xml" xlink:title="Memory stick type A"/> <loc xlink:type="locator" xlink:label="memstick_doc" xlink:href="stickB.xml" xlink:title="Memory stick type B"/> <loc xlink:type="locator" xlink:label="memstick_doc" xlink:href="stickC.xml" xlink:title="Memory stick type C"/> <arc xlink:type="arc" xlink:from="here" xlink:to="memstick_doc" xlink:show="new" xlink:actuate="onRequest" xlink:title="Open all type of memory sticks"/> </ext>
Storage in DCF standard yes This link opens the dcf.xml document which will popup a new window with a document representing a recomandation/solution for this specific problem. The owner of dcf.xml page wants that all its visitors to see this recomandation/solution in a new popup window. The XLink code that popups the window is to be found in this document (extended.xml) and looks like this: <extlink xlink:type="extended"> <loc xlink:type="locator" xlink:label="trigger-doc" xlink:href="dcf.xml" xlink:title="DCF Documentation"/> <loc xlink:type="locator" xlink:label="popup-doc" xlink:href="dcf-solution.xml" xlink:title="DCF Recomandation/Solution"/> <arc xlink:type="arc" xlink:from="trigger-doc" xlink:to="popup-doc" xlink:show="new" xlink:actuate="onLoad" xlink:title="Open a solution"/> </extlink>
Image deletion at the camera single pictures / all pictures. (Improved more on Device A Camera) Supposing one wants document redirections from Device A to Device B and then to Device C. Clinking on the link on the left you will be redirected 3 times until deviceC.xml file reached. Multiple redirections code looks like this: <ext-link xlink:type="extended"> <loc xlink:type="locator" xlink:label="file1" xlink:href="deviceA.xml" xlink:title="Filename is deviceA.xml"/> <loc xlink:type="locator" xlink:label="file2" xlink:href="deviceB.xml" xlink:title="Filename is deviceB.xml"/> <loc xlink:type="locator" xlink:label="file3" xlink:href="deviceC.xml" xlink:title="Filename is deviceC.xml"/> <arc xlink:type="arc" xlink:from="file1" xlink:to="file2" xlink:actuate="onLoad" xlink:title="Jump from Device A to Device B"/> <arc xlink:type="arc" xlink:from="file2" xlink:to="file3" xlink:actuate="onLoad" xlink:title="Jump from Device B to Device C"/> </ext-link>
Other connectors AC adaptor input, PAL/NTSC video output (switchable), audio output. Different from Device D. Click here if you want to activate the links in linkbase.xml. XLink Linkbase. In linkbase files you can declare as many extended links as you want. Linkbase files are XML files separated from the browsed documents and containing only extended XLinks. The links declared in these files can be activated with a code like this: Click <linkbaselink xlink:type="extended"> <loc xlink:type="locator" xlink:label="linkbasedoc" xlink:href="linkbase.xml" xlink:title="A linkbase file containing extended XLinks"/> <res xlink:type="resource" xlink:label="locallink">here</res> <arc xlink:type="arc" xlink:from="locallink" xlink:to="linkbasedoc" xlink:actuate="onRequest" xlink:title="Loads linkbase links" xlink:arcrole="http://www.w3.org/1999/xlink/properties/linkbase"/> </linkbaselink> if you want to activate the links in linkbase.xml. If you click on here link from the left the browser will load all the extended links from linkbase.xml file and activate them. The -|| xlink:arcrole="http://www.w3.org/1999/xlink/properties/linkbase" ||- attribute makes the browser to treat this link like a special link, a link that loads a linkbase file. Open Device D document first without clicking on here and you will see the difference after you click on it. NB: The linkbase file can also be loaded automaticaly by an extended XLink with actuate="onLoad" placed in deviceD.xml.