[Data-modeling] Processes

[Iain Sproat]

I've drafted up a (fairly abstract and ambitious) schema for modelling
Processes at http://process.freebase.com/ and I'd like some comments on it.
 Narphorium <http://www.freebase.com/view/user/narphorium> has something
similar in his project
management<http://www.freebase.com/view/user/narphorium/project_management>base.
I was initially trying to scheme up industrial and manufacturing processes
and came up with a basic scheme for that, but I have made some alterations
to broaden the scope and it might now also be suitable for other processes -
I've added the nitrogen
cycle<http://process.freebase.com/view/en/nitrogen_cycle> topic
and also Software waterfall
Model<http://process.freebase.com/view/en/waterfall_model> topic
as examples.

As a description of what is going on in the schema:
Firstly, there is a
Process<http://process.freebase.com/type/schema/base/process/process>type,
e.g. Nitrogen
fixation <http://process.freebase.com/view/en/nitrogen_fixation> , which has
some Input and Output properties (these would be typically expect a type of
material, but to allow for flexibility I'm only going to expect a type of
Topic)
A process can be composed of other component processes (for the Nitrogen
Cycle <http://process.freebase.com/view/en/nitrogen_cycle> these would
be Nitrogen
fixation <http://process.freebase.com/view/en/nitrogen_fixation> ,
decomposition <http://process.freebase.com/view/en/decomposition> ,
Nitrification <http://process.freebase.com/view/en/nitrification> etc.).
 Parent and component processes are linked with a Process stage
CVT<http://process.freebase.com/type/schema/base/process/process_stage>
 .

I was trying to model the order in which stages of a process occur (e.g.
decomposition, followed by Nitrification, followed by assimilation) by using
"previous stage" and "subsequent stage" properties - but that led to a CVT
within a CVT which the client doesn't agree with.  I've worked around this
to make Process stage have an Input and Output property, but this means that
input and outputs both need to be entered twice - once into the Process
topic and another time into the Process stage CVT - not ideal but it works.

In the Process type there is an "Tool" property which allows for tools,
machinery, catalysts etc. and the entity which carries out the process to be
noted.  e.g. Nitrifying bacteria carry out Nitrification, or that Factory Y
used Tool Z to carry out Process X.

Finally, there is a parent-child relationship in Process which allows
general and specific types of processes to be linked.  e.g. The Haber
Process and Biological Nitrogen Fixation are both more specific processes of
the general Nitrogen Fixation process.

I'd welcome constructive feedback that anyone has on this.

Iain
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freebase.com/pipermail/data-modeling/attachments/20090511/3a2bad4a/attachment-0001.htm