[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [eclipse-dev] Schema doc validation
|
Is there some move afoot to turn these into actual XML Schema documents? A
random sampling shows these problems...
- Improper namespace use
- No value for point attributes of extension elements (not even in
documentation)
- Only generic documentation for extensions
I would like to process these "schemas" and turn them into a RELAX NG schema
that can actually be used for validation, user assist, etc.
Bob
----- Original Message -----
From: "Dejan Glozic" <dejan@xxxxxxxxxx>
To: <eclipse-dev@xxxxxxxxxxx>
Sent: Wednesday, June 25, 2003 2:12 PM
Subject: [eclipse-dev] Schema doc validation
> Now that we fixed the regression (in today's I build), you may notice some
> new warnings if you have projects with schema files in your workspace.
> These warnings come from PDE schema validation step that checks
> documentation sections of your schema and hunts for the following:
>
> - Unmatched tags (e.g. <p .....)
> - Closing tags that does not match the opening one (e.g. <p> </b>)
> - No closing tag (e.g. <p>).
>
> Note that although browsers generally tolerate tags that are not closed,
it
> is a recommended practice that modern HTML documents are also well formed
> XML documents, hence the warning. To fix it, just add the closing tag (we
> suspect that 80% of the warnings will be for new paragraph tags using the
> old style).
>
> And just to illustrate how we are not only making you do more work, we had
> to fix our own schemas (all Update Core schemas had problems listed above
:
> -).
>
> Regards,
>
> Dejan Glozic, Ph.D.
> Manager, Eclipse Platform Components
> D2/MY7/8200/MKM
> IBM Canada Ltd.
> Tel. 905 413-2745 T/L 969-2745
> Fax. 905 413-4854
>
> _______________________________________________
> eclipse-dev mailing list
> eclipse-dev@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/eclipse-dev
>
>
