Open Stack

Anne:

Once we have the customized schema file, it will be fairly trivial to
update the script to point to it (one line change in validate.py):

https://github.com/openstack/openstack-manuals/blob/master/tools/validate.py#L63

Lorin


On Mon, Aug 26, 2013 at 10:54 AM, Anne Gentle <anne at openstack.org> wrote:

>
>
>
> On Mon, Aug 26, 2013 at 9:50 AM, Lorin Hochstein <lorin at nimbisservices.com
> > wrote:
>
>>
>> On Mon, Aug 26, 2013 at 10:43 AM, Anne Gentle <anne at openstack.org> wrote:
>>
>>>
>>>
>>>
>>> On Mon, Aug 26, 2013 at 9:29 AM, Lorin Hochstein <
>>> lorin at nimbisservices.com> wrote:
>>>
>>>>
>>>> On Mon, Aug 26, 2013 at 9:37 AM, Anne Gentle <anne at openstack.org>wrote:
>>>>
>>>>>
>>>>>
>>>>> On Mon, Aug 26, 2013 at 6:21 AM, Andreas Jaeger <aj at suse.com> wrote:
>>>>>
>>>>>> On 08/26/2013 04:32 AM, Tom Fifield wrote:
>>>>>> > Hi,
>>>>>> >
>>>>>> > I've tried to fix this one https://review.openstack.org/#/c/43032
>>>>>> >
>>>>>> > for build for a bit, but it's hard without a line number for the
>>>>>> > validation error. I've isolated it to the file
>>>>>> > section_object-storage-features.xml.
>>>>>> >
>>>>>> > Any ideas?
>>>>>>
>>>>>>
>>>>>> I found the culprit:
>>>>>> Remove from line 748 this include:
>>>>>>
>>>>>>             <xi:include
>>>>>> href="../common/tables/swift-proxy-server-(filter:slo).xml"/>
>>>>>>
>>>>>> I guess you need to wrap that in a section but can't debug further
>>>>>> now,
>>>>>>
>>>>>>
>>>>> Yep,  the para table elements need to be wrapped in a section.
>>>>>
>>>>> I'm hesitant to stop validating individual files because many people
>>>>> need to use a non-validating editor. Can we find a way to validate
>>>>> individual files against a schema that we all agree to?
>>>>>
>>>>
>>>> Anne:
>>>>
>>>> Is the individual file validation useful for people using a
>>>> non-validating editor? Given that validate.py now runs maven on all changed
>>>> books and will fail if a book doesn't build, is there any value added by
>>>> running validation against individual files?
>>>>
>>>> The only advantage I could imagine is if the individual file validation
>>>> gave clearer error messages than maven, but I'm not even sure if that's the
>>>> case.
>>>>
>>>
>>> I'm thinking of the scenario where Tom got an error message from Maven
>>> but still couldn't find the error. When I use a validating editor it's easy
>>> to find. When I'm not, it's not. So my sense of the overall need is for
>>> more fine-grained indicators to locate and troubleshoot.
>>>
>>>
>>
>> Ah, gotcha.
>>
>> In that case, David, can you generate that customized schema you made
>> reference to earlier (less constrained in what's allowed in the root node)?
>> We can add it to the repository and use that for individual file checking.
>>
>>
> Do any Pythonistas know if it's possible to customize the lxml library to
> insert your own customized schema? That's a potential shortcut I think.
>
>
>> Lorin
>>
>> --
>> Lorin Hochstein
>> Lead Architect - Cloud Services
>> Nimbis Services, Inc.
>> www.nimbisservices.com
>>
>
>


-- 
Lorin Hochstein
Lead Architect - Cloud Services
Nimbis Services, Inc.
www.nimbisservices.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20130826/a37ad0aa/attachment.html>