As per ODF TC minutes on 21-March-2016, the xml:id in context.xml is accepted for ODF 1.3

Outside of context.xml, a separate JIRA issue should be opened if the feature is to be pursued.

adding a proposal to implement 1.

some notes:

• 19.861 text:section-name and 19.910.37 <text:section-source> say that fragment identifiers may refer to sections by text:name.

• this is all formulated in terms of what URIs may do, not in terms of what Consumers should support.

• i think this should be either somewhere in section 3 Document Structure, or an appendix... i'm putting it at the end of section 3

• an obvious other candidate target for fragment-identifiers is bookmarks by name - should we mention that explicitly?

• LibreOffice supports an astonishing amount of other things as target of a fragment identifier, so i've added an implementation-dependent clause

to answer the question what kind of fragment identifiers LibreOffice supports:

• Writer:

• "abc|region" => section named "abc"
• "abc|outline" => heading with number "abc" , or with text that starts with "abc"
• "abc|frame" => text frame named "abc"
• "abc|graphic" => image named "abc"
• "abc|ole" => embedded object named "abc"
• "abc|table" => table named "abc"
• "abc|sequence!1" => 1st sequence field named "abc"
• "abc|text" => search for text content "abc"
• "abc" => bookmark named "abc" or hyperlink named "abc"

• Calc

• anything that can be parsed as a valid cell address or range

• Impress/Draw

• "action?jump=firstslide" => first page
• "action?jump=lastslide" => last page
• "action?jump=nextslide" => next page
• "abc" => page named "abc" or shape named "abc"

• Impress, while slideshow is running:

• "page1" => 1st page
• "abc" => shape named "abc"