Re: Document pch and linkerflag elements.

[Martin Fuchs]

Hello,

the main XML build file "ReactOS.xml" is referencing a DTD file
"tools/rbuild/project.dtd". But it's not included in the SVN
repository. Is there already such a file? And in that case - could you
please check it in?

Thanks,

Martin

[Casper Hornstrup]

I don't know of such a file. Maybe Royce has one.

Casper
> -----Original Message-----
> From: [e-mail] [mailto:[e-mail]] On Behalf Of Martin Fuchs
> Sent: 31. juli 2005 10:21
> To: ReactOS Development List
> Subject: [ros-dev] Re: Document pch and linkerflag elements.
>
> Hello,
>
> the main XML build file "ReactOS.xml" is referencing a DTD file
> "tools/rbuild/project.dtd". But it's not included in the SVN
> repository. Is there already such a file? And in that case - could you
> please check it in?
>
> Thanks,
> Martin
>
> Ros-dev mailing list
> [e-mail]
> http://reactos.com:8080/mailman/listinfo/ros-dev

[Royce Mitchell III]

I had at one time, but...

1) I don't any more

2) The structure changed a lot since I had written it anyway.

Sorry :(

Casper Hornstrup wrote:
> I don't know of such a file. Maybe Royce has one.
>
> Casper
> > -----Original Message-----
> > From: [e-mail] [mailto:[e-mail]] On Behalf Of Martin Fuchs
> > Sent: 31. juli 2005 10:21
> > To: ReactOS Development List
> > Subject: [ros-dev] Re: Document pch and linkerflag elements.
> >
> > Hello,
> >
> > the main XML build file "ReactOS.xml" is referencing a DTD file
> > "tools/rbuild/project.dtd". But it's not included in the SVN
> > repository. Is there already such a file? And in that case - could you
> > please check it in?
> >
> > Thanks,
> >
> > Martin
> >
> > Ros-dev mailing list
> > [e-mail]
> > http://reactos.com:8080/mailman/listinfo/ros-dev
>
> Ros-dev mailing list
> [e-mail]
> http://reactos.com:8080/mailman/listinfo/ros-dev
>
> .

[Royce Mitchell III]

Royce Mitchell III wrote:
> I had at one time, but...
>
> I don't any more
>
> The structure changed a lot since I had written it anyway.
>
> Sorry :(

Also, I could never get it to work with validators because I couldn't 
find a way to get them to recognize the "xi" namespace

[Emanuele Aliberti]

There is a problem with our XML. XInclude requires that included XML 
files contain a single node. We violate that rule almost everywhere.

For instance. In ReactOS.xml there is

<xi:include href="baseaddress.xml" />

but baseaddress.xml contains only a set of <property ... /> nodes, not a 
containing node. I tried wrapping them with a <group>...</group> node

<group>
  <property ... />
  ...
</group>

and it works fine. More difficult is the <directory ...> case.

Royce Mitchell III wrote:
> > I had at one time, but...
> >
> > I don't any more
> >
> > The structure changed a lot since I had written it anyway.
> >
> > Sorry :(
>
> Also, I could never get it to work with validators because I couldn't 
> find a way to get them to recognize the "xi" namespace
-- 
:Emanuele Aliberti

[Royce Mitchell III]

Emanuele Aliberti wrote:
> There is a problem with our XML. XInclude requires that included XML 
> files contain a single node. We violate that rule almost everywhere.
>
> For instance. In ReactOS.xml there is
>
> <xi:include href="baseaddress.xml" />
>
> but baseaddress.xml contains only a set of <property ... /> nodes, not 
> a containing node. I tried wrapping them with a <group>...</group> node
>
> <group>
>  <property ... />
>  ...
> </group>
>
> and it works fine. More difficult is the <directory ...> case.

IMHO, A special "do-nothing" xml tag should be created for this purpose.

[Emanuele Aliberti]

Royce Mitchell III wrote:
> Emanuele Aliberti wrote:
> > There is a problem with our XML. XInclude requires that included XML 
> > files contain a single node. We violate that rule almost everywhere.
> >
> > For instance. In ReactOS.xml there is
> >
> > <xi:include href="baseaddress.xml" />
> >
> > but baseaddress.xml contains only a set of <property ... /> nodes, 
> > not a containing node. I tried wrapping them with a 
> > <group>...</group> node
> >
> > <group>
> >  <property ... />
> >  ...
> > </group>
> >
> > and it works fine. More difficult is the <directory ...> case.
>
> IMHO, A special "do-nothing" xml tag should be created for this purpose.

<group> looks like harmless, but i could not find what it is for.

I put the HTML rendering of the rbuild reference on line here 
http://users.libero.it/ea/ros/rbuild/ for wider audience and peer review.

After some <group>'ing, loading ReactOS.xml in XXE 2.10 emits this error 
now:

/project/xi:include:
cannot load file "E:\src\ros\trunk\reactos\config.xml": 
E:\src\ros\trunk\reactos\config.xml (file not found)

I don't know if it is wrong how we specify xi:fallback or if XXE is wrong.
-- 
:Emanuele Aliberti

[Royce Mitchell III]

Emanuele Aliberti wrote:
> <group> looks like harmless, but i could not find what it is for.

It was (mostly) created for specifying common options for a collection 
of entities. However, a tag specifically documented as a top-level tag 
for xi:included files would be better to use for "readability" purposes.
> I put the HTML rendering of the rbuild reference on line here 
> http://users.libero.it/ea/ros/rbuild/ for wider audience and peer review.

Cool, thank you.
> After some <group>'ing, loading ReactOS.xml in XXE 2.10 emits this 
> error now:
>
> /project/xi:include:
> cannot load file "E:\src\ros\trunk\reactos\config.xml": 
> E:\src\ros\trunk\reactos\config.xml (file not found)
>
> I don't know if it is wrong how we specify xi:fallback or if XXE is 
> wrong.

http://www.stylusstudio.com/w3c/xinclude/include_element.htm
http://www.stylusstudio.com/w3c/xinclude/fallback_element.htm#fallback_eleme...

It looks like our use of xi:fallback is correct. Perhaps, though, the 
problem is that we're not including a DTD for xi:include. I tried 
doing that once, but the tools I had at hand couldn't get past first 
base with external namespaces.

[Emanuele Aliberti]

Royce Mitchell III wrote:
> It looks like our use of xi:fallback is correct. Perhaps, though, the 
> problem is that we're not including a DTD for xi:include. I tried 
> doing that once, but the tools I had at hand couldn't get past first 
> base with external namespaces.

I just commited a rough DTD for the 'project' document. XXE 2.10 says 
ReactOS.xml is valid (it may be boggy, just like XInclude support though).
-- 
:Emanuele Aliberti

[Emanuele Aliberti]

Emanuele Aliberti wrote:
> After some <group>'ing, loading ReactOS.xml in XXE 2.10 emits this 
> error now:
>
> /project/xi:include:
> cannot load file "E:\src\ros\trunk\reactos\config.xml": 
> E:\src\ros\trunk\reactos\config.xml (file not found)
>
> I don't know if it is wrong how we specify xi:fallback or if XXE is 
> wrong.

XML Inclusions (http://www.w3.org/TR/2004/REC-xinclude-20041220/) 
specify exactly what we do (§ 3.2):

<xi:include ...>
  xi:fallback
    <xi:include ... />
  </xi:fallback>
</xi:include>

and says (§ 4.4) that "XInclude processors must perform fallback 
behavior in the event of a resource error, [omissis]".

It seems XXE 2.10 has a bug.
-- 
:Emanuele Aliberti