Katie Capps Parlante wrote:
In the architecture document, I used the term "domain model" instead
of "content model". This layer defines the domain specific schema:
calendar events, email messages, tasks, contacts, etc. The term
"content model" was OSAF specific. I strongly prefer "domain model"
because that is a more standard term.
http://chandler.osafoundation.org/docs/0.6/overview.html
Before I go do a bunch of wiki gardening and initiate any code
changes, I thought I'd do a sanity check. Do folks agree with this
terminology change? Please respond by Wednesday morning.
+1, or maybe +10 :)
I always though "content model" was confusing - especially since the DOM
in a web page is also often referred to as a content model. It took me a
few weeks at OSAF to realize that the "content model" didn't necessarily
include the block API :)
Alec
Cheers,
Katie
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/dev
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/dev
