Ticket #820 (new enhancement)

Opened 9 months ago

Last modified 8 months ago

Use ontologies to store content model info and have references to them from ClassMetadata etc.

Reported by: pradeep Assigned to: pradeep
Priority: high Milestone:
Component: topaz Version: 0.8.3-SNAPSHOT
Keywords: Cc:
Blocking: Blocked By:

Description (Last modified by pradeep)

Amit, as you mentioned, the key to using ontology is to recognize that there are multiple ontologies. So in one ontology a property can be an object-property and in another it can be a data-property without any conflict.

1. @Entity annotation should add the following two attributes:

uses=<ontology> or defines=<ontology>. If neither of them are present, it defaults to a 'defines=<ontology>' where ontology id/name is constructed from the entity-name

2. Embedding and Java sub-classing are considered ontology mergers during definition.

3. super-class and embedded-class properties arc expected to conform to the ontology defined as 'uses' on any java class.

Dependency Graph

Change History

03/04/08 16:41:26 changed by pradeep

  • description changed.

03/19/08 15:54:50 changed by amit

I would recommend to keep this simple for now and use internal structures. We will map this out post 0.9. Makes sense?

03/25/08 11:51:03 changed by pradeep

(In [5148]) Remove the rdf:type of the association from the RdfMapper?. It is more accurate to look this up based on the associated entity. Also the RdfMapper? look-up by URI is accurate only if the complete rdf:type look-ahead values are available. So removed the version that looked up mappers by partial rdf:type look-ahead info. Therefore made the Criterion persistence pre-insert/post-load store/retrieve the complete rdf:type information of the associated entity.

@Predicate should also be providing an explicit associated entity configuration option for referring to entities loaded via other mechanisms (eg. from an OWL content model definition). This requires the de-coupling of binding and meta-definition as required by (see #820).

See #840 also.

03/28/08 11:56:29 changed by pradeep

(In [5178]) Seperate out the definitions part of Mappers. Now Mappers are built from Definitions and Binders. This makes it possible to seperate out the content model definitions from the entity-mode specific bindings.

Definitions now are registered with the SessionFactory? and can be used by "usage-classes" by referring to them. No annotations support exist at the moment - so the only way to use this now is programatically.

Addresses #820.

03/31/08 16:20:15 changed by amit

  • milestone changed from 0.8.3 to 0.9.0.

04/03/08 14:45:04 changed by amit

  • milestone deleted.