[RFC] profile editing within nALFS: how much do you really want it?

Hui Zhou zhouhui at wam.umd.edu
Mon Mar 15 11:45:35 PST 2004

On Mon, Mar 15, 2004 at 12:15:19PM -0700, Kevin P. Fleming wrote:
> >Here is a question that I would like to hear from you:
> >Now the parsing of profile is (or will be?) moved to the backend, is
> >it possible to make the parsing function a module, so one can extend
> >nALFS to use other profile if one really desire? As far as the actual
> >running concerned, nALFS only cares the instructions, the original
> >format is lost anyway, so it should be possible, isn't it? 
> I won't say it's impossible, but it would not be easy. The nALFS 
> handlers and the code that supports them are also built around the 
> existing XML profiles. The same goes for the future "frontend", it will 
> understand that the profile is a tree-structured entity and be able to 
> navigate it with help from the backend, produce log files, etc. If some 
> alternative profile could be represented in the same fashion then it's 
> possible that the nALFS frontend could be used to talk to a different 
> backend, but I don't know about splitting the backend into pieces.
> -- 
I meant other profile format that also provides a tree sturcture.
What I have in mind right now is OGDL, which is a tree structure also.


More information about the alfs-discuss mailing list