Anthony Perritano wrote: > I think this is great. maybe we can talk about this @ the sail > meeting. but what does this mean for timeline for authoring and trying > to create a concrete editor that can author correct curnits.right > now, we are trying to create testing/implentation interations to get > authoring working. how does this impact this? If anything this will slow down that process in the beginning. It is probably best to try to fix the existing system to get authoring working. But I know that has been a pain and has required a lot of work of Turadg and you. If it is simply not practical way to move forward with the existing Authoring tool and the existing Pod system, then perhaps the suggestion below is feasible.
Here is a suggestion which looks good to me, but perhaps it is not practical given the TELS or the researcher pack deadlines: - put authoring on hold until next weeks meeting - I'll make the skeleton of Pas in OTrunk - we discuss this at next weeks meeting -- if we decide to go ahead with OTrunk, then authoring will stay on hold until October (see below) -- if we decide not go ahead, then authoring will start up again using the existing system. - if we go ahead with OTrunk then in October Tony and possibly Turadg comes out to CC for a week and we create the first version of Pas in OTrunk complete with basic authoring. I chose October for a few reasons: - Turadg said he might be available in October - CC should have another programmer hired at that point, so this will be a chance to bring them up-to-speed at the same time as Turadg and Tony. - CC others project will be well under way at that point so we shouldn't be crunching for some other projects deadline. - The longer we hold off switching to OTrunk the easier it will be. Scott > > -Tony > > On 7/25/07, *Scott Cytacki* <[EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>> wrote: > > > Turadg Aleahmad wrote: > > Here at CSCL, Stephen and I have been talking about OTrunk is > used in > > SAIL, how Scott's planning to move it onto EMF, and how maybe > the same > > tech could be used as the object persistence format in pods. > > > > I've put some notes together on our current design and how we got > > here. I'd really like to get rid of XMLEncoder, or at least this > > assemblyCalls mechanism. Please take a look at this proposal and > > leave any comments, additions or clarifications. > > > > > > > > http://www.telscenter.org/confluence/display/SAIL/Proposal+for+pod+model+v2 > > <http://www.telscenter.org/confluence/display/SAIL/Proposal+for+pod+model+v2> > > > > Scott, what do you think? > I agree getting rid of the assembly mechanism is a must. > > If we are considering moving to OTrunk/EMF, then I don't think it > makes > sense to do some intermediate replacement of XMLEncoder. A change > like > this in any form will affect many parts of Sail/Pas, so doing it > twice > will really slow everyone down. > > The move to OTrunk/EMF will be more fundamental than just redesigning > the Pod system. In OTrunk/EMF there might not be a need to have > something called a Pod. Most of the functionality would be there, it > would just be accomplished by multiple parts of the system working > together. > > My suggestion would be to have a CC developer or a developer who can > spend some time at CC make a prototype version of Pas that runs on > OTrunk. In this case an otml file would be used to configure the > project. I think a mostly functional version of this could be put > together in a few days time. Then we'd have something concrete to > compare with the existing Pas system. > > I think I should focus on finishing the current annotation changes > before moving on to this though. And Aaron needs to focus on another > project for the next month. > I think I or Aaron could do this prototype in late August or early > September. > > If we really need to address this now, I can spend a couple of hours > before the SAIL meeting next week and make a skeleton of the > prototype. Then we can discuss that skeleton. > > Scott > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "SAIL-Dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/SAIL-Dev?hl=en -~----------~----~----~----~------~----~------~--~---
