UBL-Ontology Project Conference Call - KIF Formalization workshop - Thu 2004-02-26 (195)
Conference Call Details (196)
- Subject: [UblOntology] project conference call - KIF Formalization workshop - Thu 2004-02-26 (197)
- Comments/Agenda: (198)
- Date: Thursday, Feb. 26, 2004 (19G)
- Start Time: 10:30 AM Pacific Standard Time (19H)
- End Time: 11:55 AM Pacific Standard Time (19I)
- Dial-in Number: 1-702-851-3330 (Las Vegas, Nevada) (19J)
- Participant Access Code: "040226#" (19K)
Agenda Ideas (19W)
- Get prepared for the KIF-Workshop session. (--AdamPease / 2004.02.19) (19X)
- setup a time for working on Core Component Type representation and recommendations (--ppy / 2004.02.26) (19Z)
- setup a time for PatCassidy to demo SMINK009min on Protege. (--ppy / 2004.02.26) (1A1)
- Folks, If I could suggest again, the best way to make sure the session next week is productive would be to try some formalization work. It may be tough, you may wind up with lots of questions, but that will be all to the good, and much better than arriving "cold" into the formalization session. I'd be eager to have email dialog with folks during the week leading up to the session. Here are the suggested "assignments" I sent out earlier. The methodology I suggest is http://ontolog.cim3.net/cgi-bin/wiki.pl?Methodology#nid091 --Adam (1A5)
- (1A6)
- Peter Yim: (1A7)
- StatusCode Invoice. Status. Code "Identifies the status of the document with regard to change from its original state; 'original', 'copy', 'revision' or 'cancellation'. Original is as first sent; a copy is typically sent on request if the original has been misplaced; a revision is a document that contains a change from the original, e.g. new, deleted or amended item lines; cancellation is cancellation of whole document (for normal order changes and cancellations the respective documents should be used)" (1A8)
- /PeterExercise (1A9)
- (1AQ)
- Mike Daconta: (1AR)
- Delivery Invoice. Delivery associates the overall invoice with the details of a delivery (or deliveries) (1AS)
- (1B0)
- Sue Probert (1B1)
- ExchangeRate Invoice. Exchange Rate "associates the invoice with an exchange rate. In any one invoice there is only one exchange rate needed, either between invoicing at tax currency, or between pricing and invoice totalling." (1B2)
Proceedings (1BB)
- We welcome NenadIvezic from NIST who is joining us at the call for the first time. (1BC)
- Issue: forking of SUMO at v1.566 (1BE)
- Needs to be addressed urgently so that there is one SUMO and one MILO, instead of having ours different from what Teknowledge is licensing differently (1BF)
- Action: (1BG)
- Adam will make revisions to "Invoice" (1BH)
- Peter to pick some other term and work on it (annouce which one) (1BI)
- call ended 11:45am PST (1BJ)