This document has RDF linked via the xml:id tag. The entire third paragraph is linked, The first time the string "Barry" appears in the subsequent paragraph is linked using text:meta, The header after that is linked (text:h), the bookmark containing the second sentence after the header is linked, and the table cell which delcares itself linked is linked. There is text before and after linked elements so you can see that when the cursor moves out of them then the RDF is no longer linked. For example, after the "Barry" text:meta link you should no longer find the RDF for barry, this is to test that scoping is working as it should. This is the first paragraph. Have you no sense of decency sir at long last? Frankly my dear, I don’t give an xml element. This document contains xml:id references to text:p, text:h, bookmarks, text:meta, and a table cell. I should move the RDF menu entries to their own to level menu, but at the moment you move the cursor and select "Collaborate/Dump RDF for point." and the UT_debugmsgs should tell you what RDF is linked to the document elements around the current cursor position. This entire paragraph is linked to dan's foaf entry. And the fun puns continue in this second paragraph. Self describing documents are load of fun eh? Why does anyone read Tolstoy when this masterpiece is available? How long is a string, longer than a USB cable? This paragraph includes a text:meta tag which surrounds the following reference to Barry. If you have the point on that last "Barry" then you should be able to discover some RDF information too. This header is linked to RDF This is just some plain text in a text:p. You will find this sentence which is in a bookmark also has some RDF. This is after the bookmark, so you shouldn't find it in the RDF at point for anything here. What follows is a table which has some RDF linked to some cells. Header R1C1 Header R1C2 Header R1C3 Raw data This cell is linked! No link here Something after the table...