[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [legalxml-econtracts] grammatical paras necessary for "linkingand retrieval mechanisms"?
John McClure wrote: > Jason, > I said for "linking and retrieval mechanisms" because if a link is to be made to > a trailing fragment of a grammatical paragraph, using a logical XP expression > that does not rely on id-lookup, then that fragment needs to exist physically as > a part of that grammatical paragraph. ?? In the simple para model, the xpath > expression to that fragment simply cannot be stated without using #id. Incorrect! Though without the example i've asked you for, i fail to see why you'd want to link to the "trailing fragment of a grammatical para" anyway. That's > the flaw of the simple para model: it does not encapsulate content as one might > normally expect, Not that there's any guarantee the content will be so encapsulated (with either the grammatical para models which have been proposed in the TC, nor with XHTML 2.0) and hence it's not possible to reference the data logically -- > you're left with #id references, which I find unacceptable for previosuly-stated > reasons. ?? > > As for retrieval mechanisms, if I want to retrieve the entire grammatical > paragraph, that's simply not possible with the simple paragraph model because > one can't know apriori the extent of SIBLING elements that are to be retrieved > as part of the grammatical paragraph that is to be retrieved. Very true, but please show me a compelling example with one of our benchmark contracts as to why you'd want to store/reuse a grammatical para, rather than an item. Examples please, so we have something we can poke at and talk about. thanks Jason > > Hope that helps. Anyway, attached is a start of a module definition for the four > elements that I've mentioned. > > <!-- LegalXML Element Structure > > <html> > <body> > <legal:instrument> > <section/> > <legal:layout/> > <legal:attachment/> > </legal:instrument> > </body> > </html> > > To do: > (a) insert instrument, attachment, and layout into %body.content; > (b) insert signature into %inline.content; > --> > >>-----Original Message----- >>From: Jason Harrop [mailto:jharrop@speedlegal.com] >>Sent: Saturday, November 22, 2003 1:25 PM >>To: Legalxml-Econtracts >>Subject: [legalxml-econtracts] grammatical paras necessary for "linking >>and retrieval mechanisms"? >> >> >> I think grammatical paragraps ARE a >> >>> key requirement for linking and retrieval mechanisms. ... it >> >>encapsulates >> >>> content that can be further analyzed by specialized software. >> >>Please provide examples which substantiate your claim. Examples from the >>Hanover Lease or any other contract would be fine. >> >>thanks >> >>Jason >> >> >>To unsubscribe from this mailing list (and be removed from the roster >>of the OASIS TC), go to >>http://www.oasis-open.org/apps/org/workgroup/legalxml-econtracts/member > > s/leave_workgroup.php. > > > ------------------------------------------------------------------------ > > To unsubscribe from this mailing list (and be removed from the roster of the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/legalxml-econtracts/members/leave_workgroup.php.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]