OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

regrep message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [regrep] Core Components - Revisited

Thanks Farrukh. Would you be willing to elaborate on one point:

Experience with many pilots suggests that the best approach is to have
an XML format for CCTS content with ebRIM format for CCTS metdata. So I
would reccomend both XML serialization format (outside of binding) and
binding to ebRIM metadata.

It would be very helpful.

(NB: I might misinterpret some CC related facts):

I'd like to enumerate some steps that might help with defining the scope.
One can assume that this is possible:

[1] CCTS abstract model -> RIM

This is what I think Joe is referring to as "RIM binding". I'd say this
could be sufficient. Subteam certainly shouldn't attempt this:

[2] CCTS abstract model -> CCTS instantiation models

Here I assume that something like UBL would be a member of "CCTS
instantiation models".

And, subteam doesn't need to address this:

[3] CCTS instantiation models  -> RIM

I thought that subteam might need to address [3], but I see that this is not
necessary, because implementations of [3] would (should) be constrained by


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]