Minor issue:
> { "label": "none", "locator": "Act I, scene i, lines 12-23" }.
First point is this is easier as just:
{ "locator": "Act I, scene i, lines 12-23" }.
E.g. just make the label key optional.
The second point is more about the substance of the proposal. If I
understand right, we have two, completely orthogonal, issues here.
1) custom locators (what to do about point locator labels we haven't itemized?)
2) multiple locators
This proposal (as represented in the example above; it's doesn't seem
to be formalized as such) attempts to solve both problems at once, so
that the upshot is that the second problem requires a free text value.
For sake of argument, why not split these issues, so that you have a
point locator defined as a list of key values; something like?
[
{ "act": "1"},
{ "scene": "3"},
{ "value": "foo 5"}
]
Bruce
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
xbiblio-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xbiblio-devel
