[glue-wg] XSD aligned to draft 27

[JP Navarro]

Paul,

I'm less familiar with the XML terminology you use, but I would  
second your
suggestion using commoner terminology: we should be able to  
independently
publish subsets of the GLUE schema hierarchy.  The ability to develop  
and
run independent info-providers for subsets of information is a very  
useful
design. Did I understand your proposal correctly?

One question this raises is how one binds or links these separately  
published
subset documents to each other?  Would we need to introduce  
attributes in each
subset that binds it to other related subsets?

JP Navarro

On Mar 13, 2008, at 8:51 AM, Paul Millar wrote:

> Hi Sergio,
>
> On Wednesday 12 March 2008 19:48:31 Sergio Andreozzi wrote:
>> XSD for GLUE 2.0 - draft 27
>> http://forge.cnaf.infn.it/plugins/scmsvn/viewcvs.php/glue/xml/ 
>> schema/GLUE2.
>> xsd?rev=1344&root=omii-europe&view=log
>
>> From a quick look, I spotted that the XSD defines a namespace:
> 	xmlns:glue="http://GLUE2"
>
> To my mind, this is broken: it should be a URI with FQDN + path.   
> The path
> should include the year and/or a version number, allowing some version
> control.
>
> On a related note, we were going to discuss the XML binding with  
> regard to
> primary documents; but, I don't believe this discussion took place.
> Discussing GLUE-2.0 "abstract" (independent of any binding) has taken
> priority.
>
> My concern was that, with the current binding, all valid documents are
> required to express the complete GLUE hierarchy.  The current XSD  
> expresses
> this by requiring documents have a "Grid" top-level element to be  
> valid.
>
> This requirement does not come from XML and XSD.  Moreover, I  
> believe that, by
> GLUE-2.0/XML introducing this requirement,  an unnecessary burden  
> will be
> placed on the info-providers.  This will make implementing them  
> harder,
> require explicit configuration and so make the process needlessly more
> fragile.
>
> It would also prevents the information being published into more  
> than one
> GLUE-based information system.
>
> As a specific proposal, I suggest that other elements be allowed as  
> top-level
> elements; for example, that a StorageService be a valid top-level  
> element.
> The primary document from a StorageService info-provider should have a
> StorageService as its top-level element.
>
> i.e., just added:
>
>         <element name="StorageService" type="glue:StorageService_t"/>
>
> after the Grid one, near the beginning of the XSD.
>
> Cheers,
>
> Paul.
>
> _______________________________________________
> glue-wg mailing list
> glue-wg at ogf.org
> http://www.ogf.org/mailman/listinfo/glue-wg
>