RE: [regrep-cc-review] Kickoff!

[David RR Webber - XML ebusiness <Gnosis_@compuserve.com>]

Diego,

This posting of yours is a gem!  Thanks for your insights.

The crux of the problem is 
'how do the two worlds work together?'

We have spent a deal of time in the OASIS CAM TC work
on seeing how to make it so that the model and the
realization can work in synergy.  When you look at
real world work - like the OASIS CIQ teams - on name
and address - you see the challenges and also the
opportunities. 

The 'Big Three' that I see we've not yet addressed are:

Context, Codelists and Construction.

While your teams approach covers the model - when
you relate say the notion of 'Person' to the OASIS CIQ
model - you see that, based on context, there are in
fact many ways of representing what Person is, in
both the linguist ways of naming said, and also their
role and function - and it requires Context to resolve
the details, and then the construction linkage for the 
physical payloads must also be addressed.

So - back to the requirements again - how much
of this are we looking to do, Phase 1, Phase 2, Phase 3,
etc.   I'm happy so long as we have a clear set of
goals (what problem(s) are we addressing?), 
requirements, and then the roadmap.

Critically - when we go out to "the world" with this - 
we need to be able to show them what they
can do 'out the box' with our deliverables, and
how it relates to their systems today.

Thanks, DW.
==============================================
Message text written by Diego Ballvé
>but I guess we're talking about the same things, just in
different levels of abstraction. As I've mentioned in a
previous 'ps', I also have assembly info, but in a
diferent XML, which I do not store as metadata. Btw, that
might be the way to handle codelists: adding to metadata
just a pointer to another registry document. Just crossed
my mind now..

Anyway, the most important thing is that one level does not
invalidate the other.
<