On Thu, Jun 7, 2012 at 9:04 AM, Frank Bennett <[email protected]> wrote: > On Thu, Jun 7, 2012 at 8:57 PM, Bruce D'Arcus <[email protected]> wrote: >> 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 > How would this work in a user interface?
Is that really our concern? Seems to me we want a good, stable, spec that leaves room for different sorts of UI approaches. It might be, for example, that some apps (like Zotero) just have a simple field and parsers that field as a set of comma-separated values. It might be that other apps treat it more structured. I guess I just need think if we're going to go this way, we better define the model (is a point locator a single value, or is it a list of key-values) so that it's clear, and that we probably shouldn't be changing it later. 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
