[jsdl-wg] Issues for the teleconference tomorrow

[Andreas Savva]

Hi Michel

I hope to make the call but just in case (still recovering from a cold) 
here are some comments:

Michel Drescher wrote:
> Co-wranglers,
> 
> I (again me...) have a list of questions (extracted from the mail of 
> Karl Czajkowski mentioned last week):
> 
> 1) Argument list handling in jsdl:Application	
	:
> 
> 2) Versioning
> This topic might be slipped, so I would like to raise it again. Call me 
> a nag bag, but is this superfluous information to contain 
> "jsdl-1..1.xsd" in the namespace definitions?
> As an alternative, I propose the following namespace that also serves as 
> a version identifier:
>     "http://www.ggf.org/jsdl/2005/03/jsdl/"
> or
>     "http://www.ggf.org/jsdl/2005/03/"
> 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.

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.

> 
> 3) Storage/bandwidth units
	:
> 
> 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.)

> 
> 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.)


-- 
Andreas Savva
Fujitsu Laboratories Ltd