|
From: Jason H. <ja...@cs...> - 2002-11-21 02:21:07
|
One extra comment. Something to consider is, is this schema something that only has to be defined once for all time (which I'm thinking it is)? If so, then whatever eventual option might not be too bad. I think the worst choice is to have something that app developers would have to muck around with. A stopgap measure would be something like: - I want to sort on attribute "dateformat" - It goes to a lookup table and sees that "dateformat" is of type "date" - It pulls the "date" sorter and then does the right thing If we use this abstraction, then we can hide the details of whatever schema definition we use in the lookup table. Does this sound feasible for what we want and reasonable? ----- Original Message ----- From: "Jeffrey Heer" <jh...@cs...> Date: Wednesday, November 20, 2002 6:09 pm Subject: [Confab-developers] RE: XML Schemas and Confab types > This approach is fine with me for now, but I need to think some > more on > what consequences it may have down the road. But then by the time > we'redown the road a better solution may have presented itself. > |