The Xpath for accessing a particular part’s title would be /law/part/title so the PRESTO URLs would need some kind of convention.
Now, I am not sure I understand the issues well enough to say which system for indexing is absolutely best. But I think the advantage of
http://www.eg.com/law/part2/titleis that it is probably a more common case that your system is interested in
/law/part/titlerather than all titles of parts
/law/part/title. But it is a matter of the particular use case and the consequent virtual schema.
This has particular interest to me because I’ve recently been involved in putting some of the UK’s legislation online. We don’t expose the parts/sections and so on as individual documents at the moment (although this is something that you get with the Statute Law Database, albeit with an awful URL scheme).
Anyway, we do have anchors for parts/sections within the main legislation which follow a similar scheme to the one that Rick suggests here. But they have a drawback: at least for consolidated legislation (which reflects the “current state” of legislation that has been amended by later legislation), the anchors don’t reflect the semantics of the numbering scheme used by the document. For example, see Section 5A of the Rent Act 1977, whose URL is:
As you can see, the URL ends in a 6 rather than 5A because it’s the 6th Section that appears in the document.
The thing is that generic, position-based XPaths into content are seldom the ones that make most sense semantically. A friendly XPath to Section 5A would look like:
and even if you just counted sections it would be:
when what you really want is the equivalent of:
//section[number = '5A']
Given this, I wonder if a “striped” URL scheme would be better, by which I mean something that follows the general pattern
/name/identifier/name/identifier. For example:
There are several advantages to this. The resulting URLs are more semantically meaningful than those based on positions. They are more robust to changes in the document (which naturally happen with consolidated legislation). They also provide a neat method of returning all the sections in a particular part, such as:
(though you could get this advantage with a position-based scheme as well, depending on how you map from XPath to URL).
The main disadvantage is that you have to provide a custom mapping from XPath to URL, because it’s not immediately obvious what identifier to use for a given element: it might be a
<number> element child for one kind of element, but an
id attribute for another element, and the position of the child for some other element. Of course you could add annotations to your schema to indicate what acts as the identifier for that particular element type, but it does raise the implementation barrier.