[ontolog-forum] Invoice ontology and SUMO

[MDaconta@xxxxxxx]

Hi All,

I am working on a first draft of an invoice ontology in 
protege as an extension of (or connecting to) SUMO.

This quickly gets us into the nature of an "invoice" and 
the questions we want our ontology to answer about
invoices.

My current high-level definition would be:
"An invoice is a document which is part of a financial transaction
between two or more parties and is a response to an order."

Comments/refinements on the definition welcome.  It is not meant
to be exhaustive ... just accurate enough to correctly position the 
initial "bootstrap classes".

In regards to SUMO, I have downloaded the protege version and 
included it in my protege project.  While clearly an invoice follows
the "physical" branch of the class hierarchy.  I did not see anything
in SUMO equal to or close to a Document.  I probably missed it.
Adam, is the concept of "Document" represented in SUMO?  

- Mike
---------------------------------------------------
Michael C. Daconta
Chief Scientist, APG, McDonald Bradley, Inc.
www.daconta.net