[Data-modeling] structure2: using the Project schema

[Ed Laurent]

Good point about "Participation" being too general. I guess we both need to
rethink that one, and maybe the generic naming conventions are what's
confusing me here overall. How about prefacing "Project" with "Engineering
or "Construction"?

I'll agree with you too on the company projects, but many "routine"
government projects are funded through competitive grants, contracts, bonds,
etc. that sometimes (not often enough) have identifiers that could be used
for summaries. Maybe that's not of interest to you, so just consider this
point like all my notes as merely a suggestion. Again, however, more precise
names for your types and properties might help provide focus and reduce
confusion (mine for example) in Freebase search.

The parent/child phylogeny is good for nesting projects (I also used that
approach) but I referred to "Project focus" in my fourth point, not the
project parent/child relationship. You used "Project focus" and I used
"Coordinated program" to describe the purpose of projects. My interpretation
was that these types were similar and I was just providing an example of the
properties that I had found useful for describing them.

Good luck with your base!
-Ed
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freebase.com/pipermail/data-modeling/attachments/20090226/fb0e07cd/attachment.htm