Hi Florido, Comments interleaved below. Cheers, David
* grouping elements commented out. is it possible to have them? any issue with that? I'd also like to have a <Services> grouping. Balazs said it was taken out at a certain moment, but I'd like it back.
I am not really sure why you would need more grouping elements? The 'Entities' element is the document root element. This element wraps the other glue entity elements in an predefined order. Therefore, the different types of entity elements are always grouped together in established locations within 'Entities.' For example, on line 91 the 'AbstractService' element positions the different types of service element (Service, ComputingService, StorageService) after <Domain> elements (AdminDomain, UserDomain) but before <AbstractEndpoint> elements (Endpoint, ComputingEndpoint, StorageEndpoint).
* Naive question: in glue2_2SampleDoc1.xml, the <glue:...> prefix is added to every element. Is that mandatory? A consumer should search within the namespaces in the header, isn't it like that?
You just need to add the default namespace declaration for the glue2 namespace to the Entities element and you can drop all the '<glue:...>' prefixes. Sample below (note the addition of the default namespace declaration within Entities: 'xmlns='http://schemas.ogf.org/glue/2009/03/spec_2.0_r1'): <?xml version="1.0" encoding="UTF-8"?> <Entities xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xmlns='http://schemas.ogf.org/glue/2009/03/spec_2.0_r1' xmlns:glue='http://schemas.ogf.org/glue/2009/03/spec_2.0_r1' xsi:schemaLocation='http://schemas.ogf.org/glue/2009/03/spec_2.0_r1 glue2_2.xsd'> <Location> <ID>location1</ID> <Associations> <ServiceID>service1</ServiceID> </Associations> </Location> <Contact> <ID>contact1</ID> <Detail>http://some.uri/embedding/contact/info</Detail> <Type>general</Type> <Associations> <ServiceID>service1</ServiceID> </Associations> </Contact> </Entities>
I already know my XML document will not validate due to the absent groupings. I will comment those out and check if it works.
I doubt that your documents will validate as this updated schema is flat, not hierarchical and a number of other changes have been made too.
Cheers, -- Florido Paganelli Lund University - Particle Physics ARC Middleware EMI Project
On 2012-06-29 14:36, david.meredith@stfc.ac.uk wrote:
Hi all,
Following OGF 35 I have produced an updated draft of the XSD: http://tools.ngs.ac.uk/ngstools/glue2proposal/flat.zip
This rendering has a ‘flat’ style and includes the global <Entities> element bag with abstract elements/substitution groups. There are a few choices that still need to be addressed which are highlighted with TODO annotations (please do a search on ‘TODO’ in glue2_2.xsd). A sample instance document is also provided (glue2_2SampleDoc1.xml).
For the purposes of demonstration, there is also a sample XSD (sampleGlue2_2Extension.xsd) that imports the glue2_2.xsd to define new service and endpoint element types. This shows how future profiles could extend the glue XSD in order to define new sub-type specialisations (also see the sample instance doc, sampleGlue2_2ExtensionDoc.xml).
I guess the next step is to do another telephone conf to agree/disagree. If possible, i would prefer to do this before spending too much effort on updating the Word doc.
Cheers,
David
==========================
David Meredith Scientific Computing Technology eScience Daresbury Laboratory Tel: +44 (0) 1925 603762 Fax: +44 (0) 1925 603100 (Site) Email: david.meredith@stfc.ac.uk
Skype name: davidismeredith
-- Scanned by iCritical.
_______________________________________________ glue-wg mailing list glue-wg@ogf.org https://www.ogf.org/mailman/listinfo/glue-wg