I see the problem. Unless the diagram linked to has the ability to highlight the ellipse then the exercise is in vain. However, I was thinking more of a semantic link, such that the effect of clicking the link is not so important as the information contained in the link, i.e. the relation between the linking page and the linked “ellipse object.”
The most common way to reference an XML element is using:
an identifier
a CSS selector
an XPath selector
So you could write:
The place is located as shown by the ellipse [[here>>Path.To.Diagram||anchor="put ellipse selector here"]]
But it won’t have any effect ATM when the link is clicked and there’s no guarantee that the selector you use is the selector we’re going to support when we’re going to implement this feature in the Diagram Application.
That answers my question. Thanks very much for your help. I guess the ideal situation would be to be able to construct a SPARQL query to insert a link dynamically, referencing the ellipse using whatever semantic property information is already available in the XWiki.
My initial thought was to add RDFa attributes to the diagram
Then link to this from the “My Place” page by querying for the property “Shows location of” with the specific value “My Place.”
I find Wiki semantics restrictive. In RDFa, you can use the “about” attribute to specify a relation between two external resources. In wiki software, you are usually restricted to specifying a link between the current page and an external resource.
I have come across subobjects in Semantic Mediawiki. It would be great if I could specify the direct link between that ellipse and the “My Place” page but I have no idea how to do that, even in Mediawiki with its subobjects.
I guess the problem is that once you introduce markup that is not wiki markup, you have to give it the same ability to be marked up semantically as ordinary wiki text.