[jsdl-wg] Issues for the teleconference tomorrow

[Ali Anjomshoaa]

Hi Andreas, Michel,


> > where
> >     "http://www.ggf.org/"  - is the shared domain of all GGF standards
> >     "jsdl/"                - is the JSDL common domain
> >     "2005/03/"             - is the version of the specification
> >     "jsdl/" (or sth. else) - is the sub-specification (if we want to 
> > think of any)
> 
> I'm ok with the current definition. (And, no, I wasn't the one to come 
> up with it.) And I'd object putting this on the teleconf agenda; it 
> doesn't feel like a useful discussion to have.

I agree with Andreas on both points, current definition is usable and we
shouldn't spend time on this today.


> 
> My proposal would be for some brave soul (Michel?) to do a short note on 
> how all GGF schema namespaces should look like and send it to the GGF 
> Editor. (It doesn't have to be an formal document or anything, maybe an 
> email would be ok.) I've seen this kind of discussion in more than one 
> group and it would be nice to have some simple guideline.

I think that this is an excellent suggestion. It would be an excellent
recommendation to have for all GGF groups.


> > 
> > 4) Reservations
> > What about the concept of resource reservations? Some initial thoughts:
> > - Use reservation tokens in JSDL to refer to previously made 
> > reservations (with means out of scope of JSDL)
> > - Incorporate/emend the job description with means to make reservations, 
> > so the reply to such a JSDL document would give the reservation token to 
> > put into another JSDL document to actually use the reserved resources
> 
> We've discussed this sort of thing in the past and put it out of scope 
> of version 1.0. (And I think that's where it should stay for now. I 
> don't want to go down the path of adding just-one-more new feature at 
> this moment.)

As Andreas and Donal have pointed out, and has been discussed at length at
various stages of JSDL development, this is out of scope for JSDL1 - and
will remain so if I could get my way :)


> 
> > 
> > 5) JSDL 2.0 issues list
> > I would like to get some topics to be put as research/development 
> > candidate for JSDL2.
> > 5.1) more structure for Java applications
> > Quote from Karl's mail:
> > 
> >>>      -- more structure for java
> >>>          -- jar versus bytecode class
> >>>          -- native compiled java?
> >>>              -- like executable but java-style
> >>>                            parameterization
> >>>          -- class w/ Main() to invoke
> >>>          -- language version
> >>>          -- external class dependencies?
> >>>          -- supported JVMs (java portability 50% myth)
> > 
> 
> I think we should have a post-v1 tracker and put these things there.  (I 
> can create a post-v1 tracker if the chairs agree.)

While I'm delighted that we are already thinking about starting on JSDL2,
can we please get JSDL1 finished first (boy we've come a long way since
2.5 years ago!) :)) . Go ahead Andreas, why not create a post-v1 tracker
now for a wish list.

Cheers and take care,

Ali


> 
> 
> -- 
> Andreas Savva
> Fujitsu Laboratories Ltd
> 
> 

--

        ---------------------------------------------------- |epcc| -
        Ali Anjomshoaa
        EPCC, University of Edinburgh
        James Clerk Maxwell Building
        Mayfield Road                   E-mail: ali at epcc.ed.ac.uk
        Edinburgh EH9 3JZ               Phone:  + 44 (0) 131 651 3388
        United Kingdom                  Fax:    + 44 (0) 131 650 6555
        -------------------------------------------------------------