[higgins-dev] Newbie question: Higgins Ontology (HOWL XML File) to Java

[<Berend.Boll@xxxxxxxxxxxxx>]

Dear Higgins Team,

we are currently looking into the Higgins project as a base implementation for an IdAS/Context Provider solution for our user profiles distributed over different application silos.

One key point we are still having problems with, is the question how to map the Higgins Ontology (as defined in an XML file) to the actual "Model" classes in the java code (EntityModel, AttributeModel) that can be accessed via the "getModel()" method.

For example, the Higgins 1.0 solution for the XMLFile Context Provider does not implement such a mapping. The "getModel" method is just not implemented here.

Also I can find no source code that may do such a "generic" scanning and conversion of the Higgins ontology XML file. From my partial understanding of Higgins so far, I would think that this mapping task is similar for each context, because the Higgins ontology is specified. So I do not have to implement such a mapping for each context provider, but can reuse some conversion method implemented in the Higgins framework. 

Is that so? And if yes, where is it done? What code can I reuse, when I write my own context provider?

Any help to get me on the right direction will be appreciated.


Kind regards, 
Berend Boll
T-Systems Enterprise Services GmbH
Systems Integration
Project Delivery Unit Telco 
IP Products Service & Network
Berend Boll
IT Systems Architect
Goslarer Ufer 35, 10589 Berlin
+49 30 3497-3246 (Tel.)
+49 30 3497-3247 (Fax)
+49 170 7641785 (Mobil)
E-Mail: berend.boll@xxxxxxxxxxxxx
Internet: http://www.t-systems.com

T-Systems Enterprise Services GmbH
Aufsichtsrat: René Obermann (Vorsitzender)
Geschäftsführung: Reinhard Clemens (Vorsitzender), Dr. Ferri Abolhassan, Olaf Heyden, Joachim Langmack, Dr. Matthias Schuster, Klaus Werner
Handelsregister: Amtsgericht Frankfurt am Main HRB 55933
Sitz der Gesellschaft: Frankfurt am Main
WEEE-Reg.-Nr. DE87523644


Notice: This transmittal and/or attachments may be privileged or confidential. If you are not the intended recipient, you are hereby notified that you have received this transmittal in error; any review, dissemination, or copying is strictly prohibited. If you received this transmittal in error, please notify us immediately by reply and immediately delete this message and all its attachments. Thank you.