Sergio,
At the XDI TC telecon meeting tonight I
announced the proposed Friday morning telecon with MEDSI and four other TC members
volunteered to attend the call along with myself:
Ajay
Madhok, AmSoft (Vice Chair)
Marc Le Maitre, Cordance (Secretary)
Steve
Churchill, ooTao & XDI.ORG
Owen
Davis,
We propose to use the following bridge,
which is available internationally although it is a toll call:
Dial-in number:
Access Code: 2647893
In addition, Steve Churchill is preparing
a short writeup of how relational-to-XDI-graph mapping works, which we will try
to send to you in advance of the call.
Any slides you can provide us will be very
helpful; you can just send them to myself and I will distribute them to the TC
members. Also, there was interest in understanding which EU directives MEDSI
was operating under so we know the types of data controls that will be
required.
RE OASIS membership, I understand the IPR
issues. It would be ideal if MEDSI itself could become an OASIS associate
member. Again, let myself or XDI TC Secretary Marc Le Maitre or our OASIS TC administrator
Mary McRae know if we can help at all.
Lastly, RE the open source licensing of
ooTao's implementation, that's not an XDI TC matter but rather ooTao and Identity
Commons policy. I believe the Apache 2.0 license will be used but only Andy or
Steve or Owen can provide you with an authoritative answer, so I'll defer to
them.
I look forward very much to speaking on
Friday morning.
Best,
=Drummond
From: sergg@tid.es [mailto:sergg@tid.es]
Sent: Wednesday,
To: Drummond Reed
Cc: geoffrey.strongin@amd.com;
marc.lemaitre@cordance.net; mev@tid.es; owen@idcommons.net; ad@ootao.com;
mary.mcrae@oasis-open.org; steven.churchill@ootao.com;
Subject: Re: MEDSI riding again
Dear Drummond,
Thank you for your answers.
As to the audioconf,
Regarding the OASIS membership, I'm sorry to tell you that I've been a bit
naive. I'm not likely to be allowed to make an individual subscription (IPR
policies) and we are studying if an associate membership is possible. Anyway,
we keep on lobbying the company to become an OASIS contributor.
And finally, maybe this is a question for Andy. Under which kind of license
will be released the XDI software? We have to take it into account in order to
define the licensing of MEDSI.
Best regards,
Sergio
Drummond Reed escribió:
I was at a conference last week and
offline all weekend, so I'm just getting caught up. It is great news that MEDSI
is going forward and we all look forward very much to working with you.
Please see my replies inline marked ###
below.
Best,
=Drummond
From: sergg@tid.es [mailto:sergg@tid.es]
Sent: Friday,
To: drummond.reed@cordance.net
Cc: geoffrey.strongin@amd.com; marc.lemaitre@cordance.net; mev@tid.es; owen@idcommons.net;
ad@ootao.com; mary.mcrae@oasis-open.org
Subject: MEDSI riding again
Dear Drummond,
Finally, we got the green light from the European Commission, so the project is
again running. Next 6th and 7th of June we are having a project meeting in
###
Unfortunately
this week Andy Dale is at a family reunion, so he will not be available. But I
could be available starting as early as
Just let
me know if either Thursday or Friday will work.
###
Regarding OASIS membership, as the company is putting off the decision of
becoming an OASIS contributor, we have decided to subscribe meanwhile as
individuals. We will start the submission asap.
###
Wonderful. It is a very easly process, though there is a little bit more
paperwork under the new OASIS membership rules. Let myself or Marc Le Maitre,
TC Secretary, know if you need any help.
###
During these weeks we have been trying the ooTao software, to understand the
most important concepts of XDI. We have some doubts about which functionalities
are implemented and which are not and the plans to do it. This way, we can
decide which functionalities of MEDSI could rely on XDI and which not.
Specifically, we are interested in the caching and synchronization mechanisms
of link contracts.
###
On the
specifics of ooTao's implementation, Steve (or Andy if he's on email) will have
to weigh in on that. I believe that caching and sync of link contracts is next
on their agenda, but again, they will have to speak to that.
###
>From a more conceptual point of view, one of the most important questions
is to know whether it is possible to represent any kind of information with the
XDI schema. We work with relational datamodels and we have to understand how to
map such a model to the XDI schema and back.
###
The
answer is yes – we have been discussing that quite a bit since the
###
I will try to show it with an example and, by the way, I will try to show the
kinds of problems we face in MEDSI:
We have a hospital working as information provider with XDI and we want to
import their updated information through XDI mechanisms.
We have a couple of tables to store the information about hospitals. One for
hospitals, another one, related 1 to n, for their departments. In a very
simplified way
HOSPITALS (#hospital_id, name, address)
DEPARTMENTS (#department_id, hospital_id, number_of beds, number_of_free_beds)
And we want to represent that information in an XDI way (authority, type,
instance, data...) to request the information and store it into the relational
database. Our doubts are how tables, fields, and data (registers) match logical
authorities, types, instances and data.
If you have any clue about this issue, it would be welcome. I'm sure we will
have many chances to analyze this issue during next weeks/months.
###
Indeed,
to be able to map and represent this data so that it can be moved between any
two XDI-enabled systems regardless of the underlying native data format
(relational, object, flat-file, etc.) is a key objective of XDI. I don't have
time for a longer answer tonight (and, ironically, it is a question that I'm
sure Andy with his relational database background would love to bite into.) But
since Andy isn't here this week, I will try to work with other TC members to
assemble an more detailed answer tomorrow and make sure you get it in advance
of our call Thursday or Friday.
Again,
let me know what time would work best for you.
###
Best regards,
Sergio.
--
|
Sergio
García Gómez |
--
|
Sergio
García Gómez |
