help-gift
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [help-GIFT] MRML stuff


From: Stephane Marchand-Maillet
Subject: Re: [help-GIFT] MRML stuff
Date: Wed, 24 Jul 2002 09:06:25 +0200

Dear Pruet, all,

> I'm in Thailand now, already complete my master degree (thanks for David). 
> I'll continue working on
> region query stuff as promised, anyway, the I18N issue interests me as well, 
> because I'm not English
> native speaking.
 So are most of us :-)

> An outline or mini-howto will be great, both in MRML side, and how to add new 
> handling code for the
> extension in GIFT too.
 I see this as an extendable library. We discussed this with Wolfgang
sometimes ago and I'll sketch something...

> I quite agree with him. GIFT is a test-bed for MRML, hence, MRML should have 
> its own space, or
> even community.
 Thanks :-) 

> I didn't look at xml:lang yet, but the recent proposal by Wolfgang is looked 
> very good for me.
 I agree that whatever is simpler is better. However, people get used to
some "style". I was saying that some people have had some thoughts on
that and rather that reinventing something that may eventually converge
to their solutions, we should not divert for them too much.....

> 
> >
> > >    - should we create a schema (XSD) for MRML, thus documenting it more
> > > precisely...
> > >    - MRML version 2.0: it is cited in the site. What is meant is to
> > > gather a set of proposal to better further MRML so that people can start
> > > doing collaborative thinking (standard procedure in collaborative
> > > efforts)...
> > >    - some inconsistencies in MRML have been reported on the mailing list
> > > (eg type attribute). I will take the messages and make some
> > > corrections...

 I forgot to add the proposal of an Issuzilla list (or Bugzilla?)

> > I guess all this depends quite a lot on what our user base wants (speak up,
> >
> > folks!). In some ways we surely can argue that free libraries for use with
> > XML have become more widely used, so that we can start using more complex 
> > XML
> >
> > features. In particular, there is a great XSL-T processor by the GNOMEs 
> > which
> >
> > might make it simple to translate more sophisticated versions of MRML into
> > more simple ones and vice versa. This might make large direction changes 
> > much
> >
> > more simple.
> 
> I think about MRML<->SOAP translation for sometime. It should not be hard 
> because both of them
> are based on MRML. If we can make MRML<->SOAP gateway or proxy, it will be 
> very easy for
           ^---- (you mean XML :-)
> developers to develop front-ends using Java or .NET .
 I suppose we should at least work inb the sense of having MRML included
as an XML-protocol here:
http://www.w3.org/2000/03/29-XML-protocol-matrix
 The proposal of having a number of consistencies with the W3C's other
specs go towards that aims (use of a namespace - mrml: -, extension
protocol, ...)
 Cheers,
 <steph/> :-)

> > > Note:  I do not intend to restrain the site for my own self. The way it
> > > works is that each HTML page is associated with an XML page (same name).
> > > I maintain the pages in CVS. If you wish to make an update, download the
> > > XML file, modify it and send it to me, I'll commit the modifs. You'll
> > > understand that I cannot open the modif procedure more...
> >
> > How do we get access to the XML? It might be good to open read-only access 
> > to
> >
> > CVS. Like that we can provide you up-to-date patches using cvs diff.
> >
> > Cheers,
> > Wolfgang
> >
> 
> Cheers,
> pruet
> 
> -------------------------------------------------
> This mail sent through IMP: http://horde.org/imp/

-- 
Stephane Marchand-Maillet, PhD
Computer Vision and Multimedia Laboratory, University of Geneva
24 Rue du General-Dufour - 1211 Geneva 4 - Switzerland
Tel: +41 (0)22 705 7631 / +41 (0)22 705 7660
Fax: +41 (0)22 705 7780 
Email: address@hidden
URL: http://viper.unige.ch/~marchand
     http://viper.unige.ch/
     http://www.benchathlon.net/
     http://www.mrml.net/



reply via email to

[Prev in Thread] Current Thread [Next in Thread]