[wpkg-users] Updated XML Schema for Packages

[Rainer Meier]

Hi,

mscdex wrote:
> I'm not sure if I'm jumping on this too early, but I thought I'd ask.

I just did some updates in SVN without testing them yet - probably you would
like to have a look:

<http://wpkg.svn.sourceforge.net/viewvc/wpkg/wpkg/current-development/xsd/packages.xsd?r1=20&view=log>

Well, I did some re-structuring but did not finish them as it looks like.


> I noticed that with the new version of WPKG, the schema for the packages
> was updated (packages.xsd). This new packages schema seems to break
> quite a bit with existing packages.xml files. One difference I found was
> the change in the "depends" element. It seems it now contains a string
> for its content and no attributes (package-id attribute is gone). Should
> the string content be the package id? Also, somewhat related, I noticed
> a packageReference type that was defined and contains a "package-id"
> attribute like the old "depends", but it isn't used anywhere in any
> elements.

As I wrote before. It was not my intention to break anything. Since I am working
on the WPKG project I never broke down compatibility to previous versions. So
upgrading to the latest version was always as easy as replacing wpkg.js. At
least this was my intention.

In this case I've created a new type called "packageReference" because I
intended to use it for dependencies, chained packages and includes. However I
forgot to assign them to the elements. Should be fixed now.


> Something else too, I noticed that with the previous (rev 20) and
> possibly with this new revision, both require the "type" attribute name
> of "check" elements to be all uppercase, which contradicts what the WPKG
> documentation shows, which has all lowercase. Changing it to uppercase
> solved the libxml errors I was getting before when validating against
> the previous schema, but it didn't seem to when validating against the
> new schema?

Well, it was always uppercase as far as I can see here. However I don't know why
(probably I had problems with lowercase because of reserved words or something
similar...). Anyway, I changed it to lowercase 'type' now.


> I'm also getting other libxml errors that the path, value, and condition
> attributes of "check" elements are "not allowed."

Hmm, might still be an issue. However I checked that I defined these attributes
as optional which does not mean they are not allowed.
Might require further investigation.


> I can post the simple packages.xml I'm using if necessary, but it _does_
> validate against the previous schema (after changing the case on the
> type attribute names from "type" to "TYPE" of course). I'm using the
> latest xmllint and libxml for validation testing.

You could try the latest version I just checked in. Suggestions are welcome of
course.

Please remember that wpkg.js does not yet make use of the XSD files. I've
"hacked" them quickly in order to get some documentation. This is the reason it
contains quite a lot of element documentation. I preferred to write a documented
XSD instead of somehow not directly linked wiki pages.
I agree that they probably need some major improvements. So please do not
consider these XSD files as a part of the officially released WPKG toolset.

br,
Rainer