OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

chairs message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Subject: Re: [chairs] Oasis document identifiers - conclusion?

I agree about not overloading file names. It would seem to me
a better solution to let the file name be most anything a given TC
wants it to be, and instead to let users rely on a set of tagged
elements of a structure that could adequately describe the attributes
of a document.

Such a structure could be managed and maintained by OASIS and
searched through a web page. A user then might retrieve all of the
standards, all the CSs, etc. This approach would not need to rely
on the good behavior of so many people across all of the TCs,
which may tend to be problematic.


jkeane wrote:
The second suggested format [TC-Phase-StandardName-Version]makes sense
because it goes from the general to the specific.

You can solve the classic database sorting problem by have multiple tags or
fields in  a catalog database. I had circulated a schematic and a list of
suggested fields prior to the Kavi meeting, but was unable to attend. Does
Kavi have any pre-existing workable solution to offer?  Are they on this
list? Are there some folks with Information Science or Wired Librarian skill
who should be involved with this discussion?.

A file name, however elegantly framed, has not been not enough to satisfy
the queries we have gotten in LegalXML. This is particularly true of queries
by outsider who have trouble figuring out what we are doing. We also have a
lot of resources beside formal documents we should share with each other.

Having a catalog database that can dynamically generate look-up table and
other user aids on various OASIS and committee web pages will allow reports
that can be specific to a sub-committee, to multiple sub-committees or cut
across committees, such as all drafts and final documents affecting
eCommerce or security. Without a database, we need to post multiple items to
various parts of the site, and then keep them synchronized as new drafts
appear and become final.

My 2 cents - based on 30 years of building document retrieval database for
litigation support.

Jim Keane
Vice Chair, LegalXML Member Section Steering Committee
Co-Chair, OdrXML

cc: Ad hoc group from LegalXML considering normalization of our document
    	Professor Lawrence Leff (who has offered to assist with document
    	Robin Gibson, Legal XML CourtFiling
    	Rogers Winters, Legal XML CourtFiling

James I. Keane
20 Esworthy Terrace
North Potomac MD 20878
301-948-4062 F: 301-947-1176 (N.B.: NEW FAX NUMBER)
www.jkeane.com <http://www.jkeane.com>

Co-Author and Annual Update Editor of Treatise: Litigation Support Systems,
An Attorney Guide 2nd
=wgstore>   Ed. (WestGroup, 1992, updated through 2002)

-----Original Message-----
From: Daniel Greenwood [mailto:dang@mit.edu]
Sent: Monday, January 06, 2003 12:33 PM
To: Eve L. Maler; chairs@lists.oasis-open.org
Subject: RE: [chairs] Oasis document identifiers - conclusion?

Eve and fellow Chairs,

I like and support the second suggestion
[TC-Phase-StandardName-Version], and I agree that it is worth
designating a Committee Specification [cs] differently from a draft or
an Oasis Standard [os] because under OASIS rules, a Committee
Specification is a special and recognized official plateau and in many
cases constitutes the final phase of formalization.

 - Daniel Greenwood, Chair of the eContracts TC and member of the
OASIS/LegalXML Member Section Steering Committee

|  Daniel J. Greenwood, Esq.
|  Director, E-Commerce Architecture Program
|  MIT School of Architecture and Planning
|  77 Massachusetts Avenue, Room 7-231
|  Cambridge, MA 02139
|     http://ecitizen.mit.edu
|     or http://www.civics.com
|     Mobile: 617-851-0412
|     Desk: 617-868-1746
|     dang@mit.edu

-----Original Message-----
From: Eve L. Maler [mailto:eve.maler@sun.com]
Sent: Monday, January 06, 2003 11:39 AM
To: chairs@lists.oasis-open.org
Subject: Re: [chairs] Oasis document identifiers - conclusion?

As far as I know these files will never be in the same area, but
general-to-specific is pretty much my reasoning for preferring the
latter...  Does anyone *disagree* with the second style shown below?


Drummond Reed wrote:
 > Is this preferable?

Or is this?


Drummond replies:

Classic database sorting decision. The latter makes the most sense.
searching long lists of TC docs from many TCs. To have them grouped
by TC
seems a lot more intuitive than by status.
Eve Maler                                        +1 781 442 3190
Sun Microsystems                            cell +1 781 354 9441
Web Technologies and Standards               eve.maler @ sun.com

To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>

To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>

To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Powered by eList eXpress LLC