This is a static archive of the previous Open Grid Forum GridForge content management system saved from host forge.ogf.org file /sf/wiki/do/viewPage/projects.glue-wg/wiki/PhoneMeeting20080410 at Fri, 04 Nov 2022 18:36:04 GMT SourceForge : View Wiki Page: PhoneMeeting20080410

Project Home

Tracker

Documents

Tasks

Source Code

Discussions

File Releases

Wiki

Project Admin
Search Wiki Pages Project: GLUE     Wiki > PhoneMeeting20080410 > View Wiki Page
wiki1998: PhoneMeeting20080410

Agenda

  • OGF 23 Booking sessions
  • XML
    • hierarchy (artf6177)
      • need Paul for finalizing discussion
      • to ask for his availability
    • usage of wildcards in association (artf6175)
    • representing inheritance (artf6178)
    • grouping element (artf6179)

Participants

  • Sergio Andreozzi
  • Balazs Konya
  • Shiraz Memon
  • Paul Millar

Summary Open Issues

  • OGF23: where to discuss GLUE-BES/HPC-JSDL profiling
    • sent email to Chris Smith to ask if he is planning to allocate slot in HPC WG session

Summary Actions

  • Sergio: to make requests for sessions by tomorrow 11 April
  • Paul to send his opinion to the list artf6175
  • Paul to send email on AOB about XML rendering

Minutes

OGF 23

  • we book 3 sessions
    • 1 session for explaining the spec in public comment
    • 1 session for discussion/update
    • 1 session for renderings
  • interact with OGF-Europe to evaluate GLUE tutorial on OGF-Europe track
    • objective: to explain the GLUE specification and provider a number of use cases
to teach how it can be used to model Grid services
    • target audience: Grid developers,
Advanced end-users (e.g. those writing utilities to submit jobs to the Grid)
    • request for 1 slot of 90'

artf6179

Q. should we enforce to publish the full hieararchy? e.g.:

    • /glue:Domains/AdminDomain/Service
<glue:Domains>
  <AdminDomain>
     <ID>UNKNOWN</ID>
	 <Services>
	     <Service>
		    <ID> ... </ID>

Sol. A

  • constraints on the server:
    • always use full hiearchy
    • if querying the Service directly,
      • expect the Service info to be complete
      • do not expect the upper entities to be complete, but they could
      • if they are not complete, then the mandatoryu attributes are published
using unknown placeholders; i.e., AdminDomain.ID can be equal to UNKNOWN

Sol. B

  • constraints on the client
    • never use full path when querying the service directly
    • use //Service/

we agree to go for Sol. A, we prefer to not put constraints in the client side

artf6175 - Paul to send his opinion to the list artf6178 - we use attribute basetype artf6179 - <List class="..."> advantage: clear decoupling from what is in GLUE spec and what is not in GLUE spec

 



Versions Associations Attachments Back Links  
Version Version Comment Created By
Version 5 Sergio Andreozzi - 04/10/2008
Version 4 Sergio Andreozzi - 04/10/2008
Version 3 Sergio Andreozzi - 04/10/2008
Version 2 Sergio Andreozzi - 04/08/2008
Version 1 Sergio Andreozzi - 04/08/2008



The Open Grid Forum Contact Webmaster | Report a problem | GridForge Help
This is a static archive of the previous Open Grid Forum GridForge content management system saved from host forge.ogf.org file /sf/wiki/do/viewPage/projects.glue-wg/wiki/PhoneMeeting20080410 at Fri, 04 Nov 2022 18:36:16 GMT