Re: [regrep-cc-review] Moving Forward (RIM-based vs.XMLSerialization)

I'll go with that. Let's strive to get the entire job done with (a):

(a) Mapping to current RIM architecture as much as possible, and
covering "unmappable" items with Slots

- and if we cannot do this (off the top of my head I can't see why we
could not), then we can consider a limited XML serialization.

Joe

David RR Webber - XML ebusiness wrote:
> 
> Joe,
> 
> Combination of a) and b).
> 
> Obviously if you can get the entire job done with a) - great.
> 
> But b) remains and option for those items that the a)
> approach comes up short for.
> 
> The nice thing about this is that is leverages the RIM
> while minimizing the impact to it.
> 
> Thanks, DW.
> ========================================
> Message text written by "Chiusano Joseph"
> >
> Would that mean (sorry for the multiple choice here):
> 
> (a) Mapping to current RIM architecture as much as possible, and
> covering "unmappable" items with Slots, OR
> 
> (b) Mapping to current RIM architecture as much as possible and covering
> "unmappable" items with limited XML-serialization (and not Slots), OR
> 
> (c) Something else?
> 
> Joe
> <