I have checked the Fedora code. There are 32 usages of the reference
Constants.MODEL.HAS_MODEL, to get the content models of a object. To me,
this feels like something that should be collected in a general method,
like getContentModels(pid) or the like.
If I remember correctly, that was the
Hi
First up, my initial proposal was just the factor out the way find the
content models for a object into a method, rather than directly querying
the relations. This should not in any way change the behaivour of
Fedora. This would make ANY approach much simpler to implement later.
After that,
Hi Asger,
On Wed, Jul 8, 2009 at 8:07 AM, Asger
Blekinge-Rasmussena...@statsbiblioteket.dk wrote:
I have checked the Fedora code. There are 32 usages of the reference
Constants.MODEL.HAS_MODEL, to get the content models of a object. To me,
this feels like something that should be collected in
Hi
We, with the Enhanced Content Models, want to support content model
inheritance. Due to the freedom for Fedora Content Models we can easily
define a inheritance relation between content models, and inheritance is
thus supported. No problem there.
But only applications that understand this
I must have mis-spoken in that I do believe the the mix-in / trait
model is the most practical for the Fedora pattern. By static, I only
meant the creation of the contents of a given model expression
datastream. In use by services, the mix-in (aggregation) and service
binding needs to be
