You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by Reinhard Poetz <re...@apache.org> on 2003/12/17 09:13:06 UTC
Custom document types
After reading
http://xml.apache.org/forrest/your-project.html#integrating_rss I've got
the impression that I have to "patch" my the Forrest distribution if I
want to add my custom document types. Isn't there any better way to add
support for my doc types based on my custom DTD? (I'm thinking of the
mount-table matcher written by Sylvain)
WDYT?
--
Reinhard
Re: repositories
Posted by David Crossley <cr...@indexgeo.com.au>.
Nicola Ken Barozzi wrote:
> Replying a bit late...
>
> David Crossley wrote:
> > Nicola Ken Barozzi wrote:
> >>Dave Brondsema wrote:
> >>...
> >>
> >>>In
> >>>http://nagoya.apache.org/eyebrowse/ReadMsg?listName=forrest-dev@xml.apache.org&msgNo=8929
> >>>you suggested a property called 'forrest.extensions.descriptors'. Do we want
> >>>these descriptors to apply to more than just skins? In light of the recent
> >>>discussion of skins, I am inclined to keep skins descriptors seperate from dtd
> >>>descriptors and any other descriptors we might have.
> >>
> >>Are we talking about the same thing here? As "descriptor" I mean the XML
> >>file that tells Forrest where to download extensions.
> >>
> >
> > <snip/>
> >
> >>I was thinking of changing it to:
> >>
> >><forrest-extensions>
> >> <extension type="skin"
> >> name="testskin"
> >> author="Nicola Ken Barozzi"
> >> website="http://www.nicolaken.com"
> >> url="http://www.apache.org/~nicolaken/whiteboard/forrestskins/">
> >> <description>
> >> Based on the standard forrest-site skin.
> >> (Note: This is only a test skin, with trivial changes to
> >> demonstrate the concept.)
> >> </description>
> >> </extension >
> >> <extension type="dtd"
> >> name="testdtd"
> >> author="Nicola Ken Barozzi"
> >> website="http://www.nicolaken.com"
> >> url="http://www.apache.org/~nicolaken/whiteboard/forrestdtds/">
> >> <description>
> >> Blah
> >> </description>
> >> </extension >
> >>
> >>...etc
> >>
> >>Why should we have two different files?
> >
> > I think that DTD descriptors would need more information.
> > There is no guarantee that all the bit-and-pieces are packed
> > together in one nice compressed archive. This is especially
> > the case for DTDs that we do not manage and cannot re-distribute.
>
> Hmmm. If we cannot distribute them, then we should not even link to
> them, as autodownload is basically equivalent to redistribution in most
> cases. We should not mix things: or we distribute, or we link to their
> whole package if they ask us for it.
>
> > I can see DTDs that have the main DTD at one URL and DTD modules
> > at another relative URL. Maybe they do not provide a catalog,
> > so it would need to come from a third-party site.
>
> I'd say that we stick to redistributable ones for now.
> Non-redistributable ones will still need to be installed by hand.
>
> > Perhaps we need to define the individual pieces separately in the
> > descriptor with a "from" and "to" and "type" etc. so that the
> > descriptor can tell Ant where to get and put the individual pieces.
>
> This is redistribution, I'd rather stay away from half-distros.
>
> In any case this system is thought for custom DTD extensions, so the
> system will anyway get the whole package from a place that distributes
> them and that agrees that we link to them.
I agree with the gist of what you are saying.
However, i wanted to provide the ability for a project to
make a local descriptor to pull together the scattered bits.
The use-case that i was trying to describe is where a government
organisation has published a DTD (and supporting bits) but did not
also package it up in a nice tar.gz that Forrest can use. Now that
the funding has gone, there might not even be a way for us to zip
it for them to add to their website.
Okay, this is way more complicated, so we should stick with
the pre-packaged method for now.
--David
Re: repositories
Posted by Nicola Ken Barozzi <ni...@apache.org>.
Replying a bit late...
David Crossley wrote:
> Nicola Ken Barozzi wrote:
>
>>Dave Brondsema wrote:
>>...
>>
>>>In
>>>http://nagoya.apache.org/eyebrowse/ReadMsg?listName=forrest-dev@xml.apache.org&msgNo=8929
>>>you suggested a property called 'forrest.extensions.descriptors'. Do we want
>>>these descriptors to apply to more than just skins? In light of the recent
>>>discussion of skins, I am inclined to keep skins descriptors seperate from dtd
>>>descriptors and any other descriptors we might have.
>>
>>Are we talking about the same thing here? As "descriptor" I mean the XML
>>file that tells Forrest where to download extensions.
>>
>
> <snip/>
>
>>I was thinking of changing it to:
>>
>><forrest-extensions>
>> <extension type="skin"
>> name="testskin"
>> author="Nicola Ken Barozzi"
>> website="http://www.nicolaken.com"
>> url="http://www.apache.org/~nicolaken/whiteboard/forrestskins/">
>> <description>
>> Based on the standard forrest-site skin.
>> (Note: This is only a test skin, with trivial changes to
>> demonstrate the concept.)
>> </description>
>> </extension >
>> <extension type="dtd"
>> name="testdtd"
>> author="Nicola Ken Barozzi"
>> website="http://www.nicolaken.com"
>> url="http://www.apache.org/~nicolaken/whiteboard/forrestdtds/">
>> <description>
>> Blah
>> </description>
>> </extension >
>>
>>...etc
>>
>>Why should we have two different files?
>
> I think that DTD descriptors would need more information.
> There is no guarantee that all the bit-and-pieces are packed
> together in one nice compressed archive. This is especially
> the case for DTDs that we do not manage and cannot re-distribute.
Hmmm. If we cannot distribute them, then we should not even link to
them, as autodownload is basically equivalent to redistribution in most
cases. We should not mix things: or we distribute, or we link to their
whole package if they ask us for it.
> I can see DTDs that have the main DTD at one URL and DTD modules
> at another relative URL. Maybe they do not provide a catalog,
> so it would need to come from a third-party site.
I'd say that we stick to redistributable ones for now.
Non-redistributable ones will still need to be installed by hand.
> Perhaps we need to define the individual pieces separately in the
> descriptor with a "from" and "to" and "type" etc. so that the
> descriptor can tell Ant where to get and put the individual pieces.
This is redistribution, I'd rather stay away from half-distros.
In any case this system is thought for custom DTD extensions, so the
system will anyway get the whole package from a place that distributes
them and that agrees that we link to them.
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
Re: repositories
Posted by David Crossley <cr...@indexgeo.com.au>.
Nicola Ken Barozzi wrote:
> Dave Brondsema wrote:
> ...
> > In
> > http://nagoya.apache.org/eyebrowse/ReadMsg?listName=forrest-dev@xml.apache.org&msgNo=8929
> > you suggested a property called 'forrest.extensions.descriptors'. Do we want
> > these descriptors to apply to more than just skins? In light of the recent
> > discussion of skins, I am inclined to keep skins descriptors seperate from dtd
> > descriptors and any other descriptors we might have.
>
> Are we talking about the same thing here? As "descriptor" I mean the XML
> file that tells Forrest where to download extensions.
>
<snip/>
> I was thinking of changing it to:
>
> <forrest-extensions>
> <extension type="skin"
> name="testskin"
> author="Nicola Ken Barozzi"
> website="http://www.nicolaken.com"
> url="http://www.apache.org/~nicolaken/whiteboard/forrestskins/">
> <description>
> Based on the standard forrest-site skin.
> (Note: This is only a test skin, with trivial changes to
> demonstrate the concept.)
> </description>
> </extension >
> <extension type="dtd"
> name="testdtd"
> author="Nicola Ken Barozzi"
> website="http://www.nicolaken.com"
> url="http://www.apache.org/~nicolaken/whiteboard/forrestdtds/">
> <description>
> Blah
> </description>
> </extension >
>
> ...etc
>
> Why should we have two different files?
I think that DTD descriptors would need more information.
There is no guarantee that all the bit-and-pieces are packed
together in one nice compressed archive. This is especially
the case for DTDs that we do not manage and cannot re-distribute.
I can see DTDs that have the main DTD at one URL and DTD modules
at another relative URL. Maybe they do not provide a catalog,
so it would need to come from a third-party site.
Perhaps we need to define the individual pieces separately in the
descriptor with a "from" and "to" and "type" etc. so that the
descriptor can tell Ant where to get and put the individual pieces.
--David
Re: repositories
Posted by Nicola Ken Barozzi <ni...@apache.org>.
Dave Brondsema wrote:
...
> In
> http://nagoya.apache.org/eyebrowse/ReadMsg?listName=forrest-dev@xml.apache.org&msgNo=8929
> you suggested a property called 'forrest.extensions.descriptors'. Do we want
> these descriptors to apply to more than just skins? In light of the recent
> discussion of skins, I am inclined to keep skins descriptors seperate from dtd
> descriptors and any other descriptors we might have.
Are we talking about the same thing here? As "descriptor" I mean the XML
file that tells Forrest where to download extensions.
Currently it's like this:
<?xml version="1.0"?>
<skins>
<skin name="testskin"
author="Nicola Ken Barozzi"
website="http://www.nicolaken.com"
url="http://www.apache.org/~nicolaken/whiteboard/forrestskins/">
<description>
Based on the standard forrest-site skin.
(Note: This is only a test skin, with trivial changes to
demonstrate the concept.)
</description>
</skin>
<skin name="testskin2"
author="Nicola Ken Barozzi"
website="http://www.nicolaken.com"
url="http://www.apache.org/~nicolaken/whiteboard/forrestskins/">
<description>
Based on the standard forrest-site skin.
(Note: This is only a test skin, with trivial changes to demonstrate
the concept.)
</description>
</skin>
</skins>
I was thinking of changing it to:
<forrest-extensions>
<extension type="skin"
name="testskin"
author="Nicola Ken Barozzi"
website="http://www.nicolaken.com"
url="http://www.apache.org/~nicolaken/whiteboard/forrestskins/">
<description>
Based on the standard forrest-site skin.
(Note: This is only a test skin, with trivial changes to
demonstrate the concept.)
</description>
</extension >
<extension type="dtd"
name="testdtd"
author="Nicola Ken Barozzi"
website="http://www.nicolaken.com"
url="http://www.apache.org/~nicolaken/whiteboard/forrestdtds/">
<description>
Blah
</description>
</extension >
...etc
Why should we have two different files?
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
Re: repositories (was: Custom document types)
Posted by Dave Brondsema <da...@brondsema.net>.
Quoting Nicola Ken Barozzi <ni...@apache.org>:
> > Btw, what do you mean with fetch-dtd tool? How does it work?
>
> If you look in Forrest now, in particular in the forrest build file in
> the distro (the one that drives forrest), you will find that the system
> downloads skins from a repository if they are not on disk.
>
> The idea is to do the same with DTDs, with the extra chore of having to
> register them for the resolver. It should not be hard, and David called
> this "fetch-dtd tool".
>
> In the near future we'll maybe switch to using Ruper for this, but for
> the moment the current system is good enough (adding of course Dave's
> suggestion of a repository override mechanism for local repositories).
>
In
http://nagoya.apache.org/eyebrowse/ReadMsg?listName=forrest-dev@xml.apache.org&msgNo=8929
you suggested a property called 'forrest.extensions.descriptors'. Do we want
these descriptors to apply to more than just skins? In light of the recent
discussion of skins, I am inclined to keep skins descriptors seperate from dtd
descriptors and any other descriptors we might have.
--
Dave Brondsema
dave@brondsema.net
http://www.brondsema.net - personal
http://www.splike.com - programming
http://csx.calvin.edu - student org
Re: Custom document types
Posted by Nicola Ken Barozzi <ni...@apache.org>.
Reinhard Poetz wrote:
...
> David, Nicola, thanks for your answers. Because of some (paid) work I've
> had to change the some priorities in my todo-list. But as soon as I've
> some time I'll look into Forrest deeper and try to come up with a
> solution.
I would really like to work on it in these winter vacations, I really I
hope I can.
> Btw, what do you mean with fetch-dtd tool? How does it work?
If you look in Forrest now, in particular in the forrest build file in
the distro (the one that drives forrest), you will find that the system
downloads skins from a repository if they are not on disk.
The idea is to do the same with DTDs, with the extra chore of having to
register them for the resolver. It should not be hard, and David called
this "fetch-dtd tool".
In the near future we'll maybe switch to using Ruper for this, but for
the moment the current system is good enough (adding of course Dave's
suggestion of a repository override mechanism for local repositories).
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
RE: Custom document types
Posted by Reinhard Poetz <re...@apache.org>.
> -----Original Message-----
> From: David Crossley [mailto:crossley@indexgeo.com.au]
> Sent: Thursday, December 18, 2003 2:58 PM
> To: forrest-dev@xml.apache.org
> Subject: Re: Custom document types
>
>
> Reinhard Poetz wrote:
> > After reading
> >
> http://xml.apache.org/forrest/your-> project.html#integrating_rss I've
> > got the impression that I have to "patch" my the Forrest
> distribution
> > if I want to add my custom document types. Isn't there any
> better way
> > to add support for my doc types based on my custom DTD?
> (I'm thinking
> > of the mount-table matcher written by Sylvain)
>
> This is a nice new thing for Cocoon and yes its use sounds
> relevant to Forrest. Please lead the way. We would still need
> the things that Nicola Ken is talking about, like the
> fetch-dtd tool to automatically "patch" in the new DTDs (add
> an additional configured xml catalog).
David, Nicola, thanks for your answers. Because of some (paid) work I've
had to change the some priorities in my todo-list. But as soon as I've
some time I'll look into Forrest deeper and try to come up with a
solution.
Btw, what do you mean with fetch-dtd tool? How does it work?
--
Reinhard
Re: Custom document types
Posted by David Crossley <cr...@indexgeo.com.au>.
Reinhard Poetz wrote:
> After reading
> http://xml.apache.org/forrest/your-project.html#integrating_rss I've got
> the impression that I have to "patch" my the Forrest distribution if I
> want to add my custom document types. Isn't there any better way to add
> support for my doc types based on my custom DTD? (I'm thinking of the
> mount-table matcher written by Sylvain)
This is a nice new thing for Cocoon and yes its use sounds relevant
to Forrest. Please lead the way. We would still need the things
that Nicola Ken is talking about, like the fetch-dtd tool to
automatically "patch" in the new DTDs (add an additional configured
xml catalog).
--David
Re: Custom document types
Posted by Nicola Ken Barozzi <ni...@apache.org>.
Reinhard Poetz wrote:
> After reading
> http://xml.apache.org/forrest/your-project.html#integrating_rss I've got
> the impression that I have to "patch" my the Forrest distribution if I
> want to add my custom document types. Isn't there any better way to add
> support for my doc types based on my custom DTD? (I'm thinking of the
> mount-table matcher written by Sylvain)
Yes, there are things in the works.
One is to make it possible to have DTD packages to install
automatically. The idea is that for a new document format we need a DTD
and a stylesheet to transform to XDOC.
The other is to have a sourcemap that specifies where to find the sources.
Finally, if the above two are not sufficient, we will see to add
sitemaps like that matcher does.
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------