RE: Section 5 Comments

["Carlson, Tom" <tcarlson@ncsc.dni.us>]

The problems you mentioned about color coding is why I think there also
needs to be the code. The code is usually something simple like 1=maps
exactly to the GJXDM, 2=GJXDM element in a different context,
3=extenstion, 4=some kludge.

(Sorry to be short. It's 5pm Tommy time and I'm heading out the door.)

-----Original Message-----
From: Perry, Ellen M. [mailto:EPerry@mtgmc.com] 
Sent: Tuesday, October 25, 2005 4:55 PM
To: Carlson, Tom; legalxml-intj-exmndr@lists.oasis-open.org
Subject: RE: Section 5 Comments


Thanks for the feedback, Tom.  I've also copied the subcommittee here in
case anyone else wants to weigh in.


- The suggested section name change seems reasonable to me.

- Scott, do you have any further explanation about why it might not be
necessary to include the full path?

- I'm not sure about the utility of a column that captures how well an
element maps to the GJXDM. While that would be helpful during the
development process, I thought that the final IEPD would extend if there
was no GJXDM match.  Could you explain how you've seen this used in
final documents? 

- I disagree about color coding, as I think it's very labor intensive
and difficult to automate, depends on color printers, etc.  That said,
we could certainly include guidelines if an entity wanted to use colors.
I don't have any idea about "colors currently used by the community"
though - can you offer any guidance here?


--- Ellen 

The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged
material.  If you received this in error, please contact the sender and
delete the material from any computer.


-----Original Message-----
From: Carlson, Tom [mailto:tcarlson@ncsc.dni.us] 
Sent: Tuesday, October 25, 2005 1:00 PM
To: Perry, Ellen M.
Subject: Section 5 Comments

Here are my comments on Section 5:

I don't like the general layout a whole lot. I'd rather see simpler
matrix of column names, simple definitions, and require/optional status.
Then foloow the matrix with a section containing the long definitions
and notes/examples for each. Then the definitions could be expanded a
little. Right now they're not as clear as they could be, mainly, I
think, to fit them into the matrix.

This is picky, but I think we should rename the section. Every time I
read "Domain Model and GJXDM Mapping" I read it grouped like this
"(Domain Model) and (GJXDM Mapping)". This is technically correct, I
guess, but I'd rather it be something like "Mapping the Domain Model to
the GJXDM.

Regarding the full path to the GJXDM element column, Scott Came has some
justifications for not always including the full path. I confess that I
don't fully understand the argument. But I know it exists. And, knowing
Scott, it's probably valid.

I'd like to add a column that contains a code for how well an element
maps. This information is usually presented by coloring rows in the
spreadsheet. I think you need both. (Having a column with a code
preserves the info in a printout or CSV dump, and allows you to sort and
filter the spreadsheet based on the type of mapping.)

I'm also not seeing a section about the color coding. We need that,
along with the colors currently used by the community.

I'm not sure what's supposed to go in the "B.Business to GJXDM Map -
Sections Overview". Maybe this is the what I asked for above, to follow
the matrix?

And, I suppose it ought to include a section on advice in doing the
mapping. Or is that somewhere else?

-----Original Message-----
From: Perry, Ellen M. [mailto:EPerry@mtgmc.com]
Sent: Tuesday, October 25, 2005 11:19 AM
To: Carlson, Tom
Subject: RE: [legalxml-intjustice] Groups - LegalXML IJTC Monthly
Conference Call modified


Ok, thanks for the update! 


--- Ellen 

The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged
material.  If you received this in error, please contact the sender and
delete the material from any computer.


-----Original Message-----
From: Carlson, Tom [mailto:tcarlson@ncsc.dni.us] 
Sent: Tuesday, October 25, 2005 8:19 AM
To: Perry, Ellen M.
Subject: RE: [legalxml-intjustice] Groups - LegalXML IJTC Monthly
Conference Call modified

I'm probably going to miss the conference call. So here's my status:

- I should have comments on Section 5 by the end of the day. (I still
need to actually write them up.)
- I expect to have a new comments-incorporated draft of Section 2 by
Friday, as we agreed to on the last MNDR Conf Call



-----Original Message-----
From: eperry@mtgmc.com [mailto:eperry@mtgmc.com]
Sent: Monday, October 24, 2005 3:21 PM
To: legalxml-intjustice@lists.oasis-open.org
Subject: [legalxml-intjustice] Groups - LegalXML IJTC Monthly Conference
Call modified


As a reminder, our monthly IJTC conference call is scheduled for
tomorrow,
Tuesday 10/25 from 10-11am Pacific.

The agenda and call in information is attached below; 



 -- Ms Ellen Perry


LegalXML IJTC Monthly Conference Call has been modified by Ms Ellen
Perry

Date:  Tuesday, 25 October 2005
Time:  10:00am - 11:00am PT

Event Description:
1-641-297-5400 (St. Marys, IA) 
Participant Access Code 251005

Agenda:
1. 	MNDR Status Report and Document Feedback 
2. 	Legal XML - Steering Committee Report 
3. 	Legal XML - Update on Court Document Deliverable  
4.	Other Business 


Minutes:


View event details:
http://www.oasis-open.org/apps/org/workgroup/legalxml-intjustice/event.p
hp?event_id=8797

PLEASE NOTE:  If the above link does not work for you, your email
application may be breaking the link into two pieces.  You may be able
to
copy and paste the entire link address into the address field of your
web
browser.