Overall, looks good. I definitely like the added benefits for inline translation.
Couple of thoughts: 1) Should "type" be required for <container> or can we default to fieldset? 2) Can we make the "attribute" sections optional for controls, allowing them to be attached to the main item as well? The attribute sections are only needed for translation. 3) You are aware that there will be many different, optional controls which different formcontrols require. Does the accommodate that? Does it matter? 4) I don't see anything in there for <option> children. Should those be included? 5) Can we make storage optional? The whole point is to make it easier for themers to create configuration, and forcing them to think about storage makes that harder. If not supplied, we'd provide an intelligent default based upon the form location. Otherwise, looks good. On Jun 3, 2009, at 12:12 AM, Owen Winkler wrote: > > XSD: > http://schemas.habariproject.org/Pluggable-1.0.xsd > > Validated XSD: > http://pastoid.com/azc+/ > > Sample XML: > http://pastoid.com/aya+0/ > > I can't find an online tool to validate the XML using the XSD, but the > XML should validate if you have a desktop tool that supports XSDs. > > Owen > > > > --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/habari-dev -~----------~----~----~----~------~----~------~--~---
