On Mon, Apr 2, 2012 at 5:34 AM, Frank Bennett <[email protected]> wrote:
> In terms of user experience in the calling application, the provision
> level is definitely the right unit of reference for note-taking, etc.
> I can see several ways of setting that up. One is to adapt the
> processor to run, as illustrated in the test, with a static locator
> (in some form -- using the section field with parsed-out label strings
> may not be ideal). Another would be to make no adjustments in the
> processor, and put the burden on calling applications to find a way of
> dicing up statutes into manageable units.
>
> The problem I see with the latter approach is that programmers of a
> calling application will be tempted to "do the right thing" and treat
> the statute as an object with a hierarchical structure internally (an
> XML construct). Doing that unavoidably opens up a massive engineering
> task that John Sheridan and Jeni Tennison are working on in the UK:
> statutes change over time, and so the XML object needs to support
> versioned storage. It's not really necessary, since a reference
> manager is only used for handling individual scraps of a statute for
> writing purposes -- for research, it is sufficient that the user has a
> browser channel through which the user can access robust data stores
> (like legislation.gov.uk), through which to discover the scraps that
> they actually want to work on.
This reminds me of a suggestion I made earlier on attaching locators to
item notes:
http://forums.zotero.org/discussion/17270/page-numbers/?Focus=99600#Comment_99600
Would that be a possible way to keep track of provisions, without requiring
separate (and hierarchically structured) items?
Rintze
------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here
http://p.sf.net/sfu/sfd2d-msazure
_______________________________________________
xbiblio-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xbiblio-devel
