You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by Nicola Ken Barozzi <ni...@apache.org> on 2005/02/23 16:43:25 UTC
Re: [RT] Per document skinconf (was Re: coloring table cells [from
the user list])
Ross Gardler wrote:
...
I agree to the intent, and in fact I had done a similar proposal,
although without considering the impact for the plugins.
Read this and tell me what you think, and how the two may fit.
[RT] Directory structure and configuration
http://marc.theaimsgroup.com/?l=forrest-dev&m=110172138119333&w=2
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
Re: Metadata in Forrest (was Re: [RT] Per document skinconf...)
Posted by Ross Gardler <rg...@apache.org>.
Nicola Ken Barozzi wrote:
> Nicola Ken Barozzi wrote:
>
>> Ross Gardler wrote:
>
> ...
>
>>> All that being said, Forrest could be made to support both a separate
>>> file or embedded data (there are use cases where the simplistic
>>> solution is the best one). The problem with this is that we will have
>>> two locations for storing the same data - could be confusing for users.
>>
>>
>> IMHO the least we have to worry about is to confuse users. I have seen
>> that if there is a simple and a more complete way, users would not get
>> confused.
>>
>> The only confusion would come out of using both methods at the same
>> time, with clashing metadata values. Ouch!
>>
>> I'll browse the web for 'rdf in html', 'xhtml metadata' etc to see how
>> this is defined elsewhere. I want to try to reinvent the wheel the
>> least possible.
>
>
> And I did :-)
>
> From what I read it seems that making it possible to embed in xhtml
> *and* be able to king to a metadata file is the solution to pursue.
OK, I'm working on meta-data in an extension to Burrokeet soon (using
Dublin Core). I'll follow up on these links and create a separate RT
(after 0.7 release).
Ross
Metadata in Forrest (was Re: [RT] Per document skinconf...)
Posted by Nicola Ken Barozzi <ni...@apache.org>.
Nicola Ken Barozzi wrote:
> Ross Gardler wrote:
...
>> All that being said, Forrest could be made to support both a separate
>> file or embedded data (there are use cases where the simplistic
>> solution is the best one). The problem with this is that we will have
>> two locations for storing the same data - could be confusing for users.
>
> IMHO the least we have to worry about is to confuse users. I have seen
> that if there is a simple and a more complete way, users would not get
> confused.
>
> The only confusion would come out of using both methods at the same
> time, with clashing metadata values. Ouch!
>
> I'll browse the web for 'rdf in html', 'xhtml metadata' etc to see how
> this is defined elsewhere. I want to try to reinvent the wheel the least
> possible.
And I did :-)
From what I read it seems that making it possible to embed in xhtml
*and* be able to king to a metadata file is the solution to pursue.
Informative Opinion
http://lists.oasis-open.org/archives/legalxml-econtracts/200401/msg00026.html
XHTML2 Metainformation Attributes Module
http://www.w3.org/TR/2004/WD-xhtml2-20040722/mod-metaAttributes.html
<link> to the Metadata
http://infomesh.net/2002/rdfinhtml/#link
FOAF Auto-Discovery: Publishing and Linking FOAF files
http://xmlns.com/foaf/0.1/#sec-foaffiles
Using Dublin Core
http://dublincore.org/documents/usageguide/
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
Re: [RT] Per document skinconf (was Re: coloring table cells [from
the user list])
Posted by Ross Gardler <rg...@apache.org>.
Nicola Ken Barozzi wrote:
> Ross Gardler wrote:
>
>> Nicola Ken Barozzi wrote:
>
...
>> Meta-data is often processed independently of actual data. For
>> example, a meta-data harvester is not interested in content. Of
>> course, this would still be possible if it were all in the same file,
>> but performance would suffer.
>
>
> So it's a technical and not a design issue. I tend to optimize later
> (and sometimes get bitten ;-)
That is also my method, and I am being bitten on the Learning Objects
projects - hence my concern here. The solution I have implemented is a
simple on in which the meta-data is embedded in the XHTML and it's a
real problem.
>> In some use cases this performance bottleneck will become an issue,
>> for example I have Learning Objects that consist of over 600 pages,
>> each with an average of around 4000 characters. Each page has an
>> additional 1000 characters of meta data (not including XML elements).
>> The nature of XML is that you need to process the whole file even if
>> you only want one element. This means we are processing 5000
>> characters of data instead of 1000, when harvesting 600 pages that is
>> 300,000 characters of data that we don't want (and we are still
>> ignoring the XML elements).
>
>
> Well, it's not true, as the stremaing parser can stop processing at any
> time. This is how we get the doctype.
OK, I concede that one :-))
>> Furthermore, meta-data tends to be highly structured and would
>> therefore benefit from being stored in a relational database rather
>> than an XML one.
>
>
> Hmmm, this is an interesting point.
I have an RDBMS Database plugin sitting on my hard drive that was built
exactly for this purpose. I've not had the time to package it nicely
yet, but it will be committed when time allows (or someone asks for it).
> My use case for metadata is title, author, etc. You have a much more
> complex use case. I now start to understand more of your POV.
I'm sure this will be the most common use case. Perhaps we now have the
first situation where we need two alternative plugins doing the same
basic job; A simple meta data plugin for handling the majority use case
of author, subject etc. and a complex one with an RDBMS and full dublin
core meta-data.
>> All that being said, Forrest could be made to support both a separate
>> file or embedded data (there are use cases where the simplistic
>> solution is the best one). The problem with this is that we will have
>> two locations for storing the same data - could be confusing for users.
>
>
> IMHO the least we have to worry about is to confuse users. I have seen
> that if there is a simple and a more complete way, users would not get
> confused.
OK
> The only confusion would come out of using both methods at the same
> time, with clashing metadata values. Ouch!
>
> I'll browse the web for 'rdf in html', 'xhtml metadata' etc to see how
> this is defined elsewhere. I want to try to reinvent the wheel the least
> possible.
I see from another mail you have found some solutions, so I'll return to
this elsewhere.
>
>>> Also, what is the relationship between skinconf.xml,
>>> pdf-output.conf.xml and metadata.xml?
>>
>>
>> The files in FORREST-INF are the defaults. So skinconf.xml contains
>> the site wide defaults for presentation elements that are core to
>> Forrest. pdf-output.conf.xml contains the defaults for PDF config
>> (button on or off, page size etc.) Metadata.xml contains site wide
>> meta data (generated-by, site title etc.)
>
>
> Why are skinconf.xml and pdf-output.conf.xml separate?
My thinking was only that the items in pdf-output.xml are irrelevant if
the pdf-output plugin is not present. Consequently, we do not want to
clutter skinconf.xml in fresh-site with config information not relevant
to the core.
An alternative would be to have the plugin add the elements into the
project skinconf-xml file the first time the site is built with the
plugin enabled.
> It seems we are in violent agreement on the concept, just need to iron
> out some smaller details.
Yes, and to see what Thorsten comes up with on the forrest:views front.
Ross
Re: [RT] Per document skinconf (was Re: coloring table cells [from
the user list])
Posted by Nicola Ken Barozzi <ni...@apache.org>.
Ross Gardler wrote:
> Nicola Ken Barozzi wrote:
...
>> Why not insert the metadata in the file itself like I proposed? I
>> prefer to keep faith to the 1 file -> one output rule.
>
> I guess our different views here are because of different use cases. You
> seem to be assuming that you only ever want the meta-data and the
> content together. That is not the case for me.
>
> Meta-data is often processed independently of actual data. For example,
> a meta-data harvester is not interested in content. Of course, this
> would still be possible if it were all in the same file, but performance
> would suffer.
So it's a technical and not a design issue. I tend to optimize later
(and sometimes get bitten ;-)
> In some use cases this performance bottleneck will become an issue, for
> example I have Learning Objects that consist of over 600 pages, each
> with an average of around 4000 characters. Each page has an additional
> 1000 characters of meta data (not including XML elements). The nature of
> XML is that you need to process the whole file even if you only want one
> element. This means we are processing 5000 characters of data instead of
> 1000, when harvesting 600 pages that is 300,000 characters of data that
> we don't want (and we are still ignoring the XML elements).
Well, it's not true, as the stremaing parser can stop processing at any
time. This is how we get the doctype.
> Furthermore, meta-data tends to be highly structured and would therefore
> benefit from being stored in a relational database rather than an XML
> one.
Hmmm, this is an interesting point.
My use case for metadata is title, author, etc. You have a much more
complex use case. I now start to understand more of your POV.
> Meta-data is often the subject of complex queries and the speed of
> a relational database is useful here. If the meta-data is stored inside
> the content file then this can only be done by duplicating the data
> across two locations. I don't want to do that, I only want to store it
> once. This wold force the meta-data to be separate from the content.
>
> Further still, it is also common, in some use cases (i.e. editing
> Learning Objects) for a meta-data editor to be working on the meta-data
> at the same time as the content author. Having the files separate is
> useful in the absence of Version Control that does not require technical
> knowledge (most of my users can barely use an email client).
I understand now.
> All that being said, Forrest could be made to support both a separate
> file or embedded data (there are use cases where the simplistic solution
> is the best one). The problem with this is that we will have two
> locations for storing the same data - could be confusing for users.
IMHO the least we have to worry about is to confuse users. I have seen
that if there is a simple and a more complete way, users would not get
confused.
The only confusion would come out of using both methods at the same
time, with clashing metadata values. Ouch!
I'll browse the web for 'rdf in html', 'xhtml metadata' etc to see how
this is defined elsewhere. I want to try to reinvent the wheel the least
possible.
>> Also, what is the relationship between skinconf.xml,
>> pdf-output.conf.xml and metadata.xml?
>
> The files in FORREST-INF are the defaults. So skinconf.xml contains the
> site wide defaults for presentation elements that are core to Forrest.
> pdf-output.conf.xml contains the defaults for PDF config (button on or
> off, page size etc.) Metadata.xml contains site wide meta data
> (generated-by, site title etc.)
Why are skinconf.xml and pdf-output.conf.xml separate?
> As with your RT you can then have versions of these files in subsites
> that will override these defaults within the scope of the subsite.
Yup.
It seems we are in violent agreement on the concept, just need to iron
out some smaller details.
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
Re: [RT] Per document skinconf (was Re: coloring table cells [from
the user list])
Posted by Ross Gardler <rg...@apache.org>.
Nicola Ken Barozzi wrote:
> Ross Gardler wrote:
>
>> Nicola Ken Barozzi wrote:
>>
>>> Ross Gardler wrote:
>>> ...
>>>
>
>> Handling Meta Data and Presentation Data
>> ----------------------------------------
>>
>> Meta-data is generated on a per file basis, with only a minority of
>> information coming from a central location. On the other hand,
>> presentation data has the majority of information coming from a
>> central location with only a minority being defined on a per file
>> granularity.
>
>
> Not necessarily. If a Forrest provider makes a site for multiple people,
> each would want it's own presentation metadata...
Exactly, if I reuse your content I will want your meta-data but not your
presentation data. Therefore we need to keep it separate.
>
>> This means that to be "able to define metadata nearer to the file that
>> needs it" we need to store the different types of data in different
>> locations. Meta-data needs to be closer to the file with an
>> opportunity to centrally define defaults (as per your RT) and
>> presentation data needs to be centralised with an opportunity to
>> override locally to the file (as per my RT).
>
>
> Again, since there are both local and central locations, where is the
> divide?
You are absolutely correct. I spotted this mistake after posting, but
thought I'd wait for your comments. Although we need two files (see
above) there need only be one access mechanism within Forrest.
>> Directory Structure
>> ===================
>>
>> How does this affect the proposed directory structure in your RT?
>>
>> You propose:
>>
>> my-project/
>> forrest.xml
>> documentation/
>> status.xml
>> ** all other content
>> FORREST-INF/
>> skinconf.xml
>> site.xml
>> tabs.xml
>>
>> This would become (arrows indicate changed/added lines):
>>
> (inserted correct version)
> ...
>
>> my-project/
>> forrest.xml
>> documentation/
>> status.xml
>> --> content.xml
>> --> content.meta.xml
>> ** all other content
>> FORREST-INF/
>> skinconf.xml
>> --> pdf-output.conf.xml
>> site.xml
>> tabs.xml
>> --> metadata.xml
>> Note that with the introduction of a meta-data plugin all the
>> meta-data files would be optional since the plugin would provide
>> defaults. Similarly the plugin conf.xml files are optional. So
>> although this looks like adding many new files, they are only present
>> if actually needed by a user.
>
>
> I don't understand what the files you add contain.
Sorry, I'll try and explain
> I suppose that content.xml is a normal xml file, and content.meta.xml
> it's metadata.
Yes
> Why not insert the metadata in the file itself like I
> proposed? I prefer to keep faith to the 1 file -> one output rule.
I guess our different views here are because of different use cases. You
seem to be assuming that you only ever want the meta-data and the
content together. That is not the case for me.
Meta-data is often processed independently of actual data. For example,
a meta-data harvester is not interested in content. Of course, this
would still be possible if it were all in the same file, but performance
would suffer.
In some use cases this performance bottleneck will become an issue, for
example I have Learning Objects that consist of over 600 pages, each
with an average of around 4000 characters. Each page has an additional
1000 characters of meta data (not including XML elements). The nature of
XML is that you need to process the whole file even if you only want one
element. This means we are processing 5000 characters of data instead of
1000, when harvesting 600 pages that is 300,000 characters of data that
we don't want (and we are still ignoring the XML elements).
Furthermore, meta-data tends to be highly structured and would therefore
benefit from being stored in a relational database rather than an XML
one. Meta-data is often the subject of complex queries and the speed of
a relational database is useful here. If the meta-data is stored inside
the content file then this can only be done by duplicating the data
across two locations. I don't want to do that, I only want to store it
once. This wold force the meta-data to be separate from the content.
Further still, it is also common, in some use cases (i.e. editing
Learning Objects) for a meta-data editor to be working on the meta-data
at the same time as the content author. Having the files separate is
useful in the absence of Version Control that does not require technical
knowledge (most of my users can barely use an email client).
All that being said, Forrest could be made to support both a separate
file or embedded data (there are use cases where the simplistic solution
is the best one). The problem with this is that we will have two
locations for storing the same data - could be confusing for users.
> Also, what is the relationship between skinconf.xml, pdf-output.conf.xml
> and metadata.xml?
The files in FORREST-INF are the defaults. So skinconf.xml contains the
site wide defaults for presentation elements that are core to Forrest.
pdf-output.conf.xml contains the defaults for PDF config (button on or
off, page size etc.) Metadata.xml contains site wide meta data
(generated-by, site title etc.)
As with your RT you can then have versions of these files in subsites
that will override these defaults within the scope of the subsite.
Ross
>
> TIA
>
Re: [RT] Per document skinconf (was Re: coloring table cells [from
the user list])
Posted by Nicola Ken Barozzi <ni...@apache.org>.
Ross Gardler wrote:
> Nicola Ken Barozzi wrote:
>
>> Ross Gardler wrote:
>> ...
>>
>> I agree to the intent, and in fact I had done a similar proposal,
>> although without considering the impact for the plugins.
>>
>> Read this and tell me what you think, and how the two may fit.
>>
>> [RT] Directory structure and configuration
>> http://marc.theaimsgroup.com/?l=forrest-dev&m=110172138119333&w=2
>
> I remember this RT now, it seems that my RT includes many of the meme's
> planted by you in your original - this is a good sign.
Indeed! :-)
> Lets discuss...
>
> What is Meta-Data? What is Presentation Data?
> =============================================
>
> In re-reading your RT I discovered why I am not completely at ease with
> the current skinconf.xml. We are confusing two types of data in the
> skinconf.xml file. On the one hand there is true meta-data (data about
> data), for example:
>
> <project-name>Forrest</project-name>
>
> and presentation data:
>
> <disable-pdf-link>false</disable-pdf-link>
>
> We have gotten away with this so far because we do not handle meta-data
> separately. However, your RT and a post by Glen Tulikin
> (http://marc.theaimsgroup.com/?l=forrest-dev&m=110324061019177&w=2)
> start to look at how we can better handle true meta-data.
>
> Unfortunately, your RT further blurs the distinction between true
> meta-data and presentation data, for example:
>
> <meta name="credits.title.name" content="Built with Forrest">
>
> is meta-data, but:
>
> <meta name="org.apache.forrest.disable-pdf-link"
> content="true"/>
>
> is presentation data.
>
> I think to further blur things in this way would be dangerous.
Hmmm, I don't understand why you think it's dangerous.... let's read on...
> I tried
> to avoid this in my RT by ignoring the meta-data aspect. I was hoping to
> sneak it through without the need to move meta-data nearer the data
> raising its head. However, your RT has the intention of being "able to
> define metadata nearer to the file that needs it".
>
> The problem is if we mix the two types of "meta" data "the file that
> needs it" cannot be identified. I'll try to explain...
Hmmm...
> Handling Meta Data and Presentation Data
> ----------------------------------------
>
> Meta-data is generated on a per file basis, with only a minority of
> information coming from a central location. On the other hand,
> presentation data has the majority of information coming from a central
> location with only a minority being defined on a per file granularity.
Not necessarily. If a Forrest provider makes a site for multiple people,
each would want it's own presentation metadata...
> This means that to be "able to define metadata nearer to the file that
> needs it" we need to store the different types of data in different
> locations. Meta-data needs to be closer to the file with an opportunity
> to centrally define defaults (as per your RT) and presentation data
> needs to be centralised with an opportunity to override locally to the
> file (as per my RT).
Again, since there are both local and central locations, where is the
divide?
> Directory Structure
> ===================
>
> How does this affect the proposed directory structure in your RT?
>
> You propose:
>
> my-project/
> forrest.xml
> documentation/
> status.xml
> ** all other content
> FORREST-INF/
> skinconf.xml
> site.xml
> tabs.xml
>
> This would become (arrows indicate changed/added lines):
>
(inserted correct version)
...
> my-project/
> forrest.xml
> documentation/
> status.xml
> --> content.xml
> --> content.meta.xml
> ** all other content
> FORREST-INF/
> skinconf.xml
> --> pdf-output.conf.xml
> site.xml
> tabs.xml
> --> metadata.xml
>
> Note that with the introduction of a meta-data plugin all the meta-data
> files would be optional since the plugin would provide defaults.
> Similarly the plugin conf.xml files are optional. So although this looks
> like adding many new files, they are only present if actually needed by
> a user.
I don't understand what the files you add contain.
I suppose that content.xml is a normal xml file, and content.meta.xml
it's metadata. Why not insert the metadata in the file itself like I
proposed? I prefer to keep faith to the 1 file -> one output rule.
Also, what is the relationship between skinconf.xml, pdf-output.conf.xml
and metadata.xml?
TIA
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
Re: 0.7 Plugin Documentation
Posted by David Crossley <cr...@apache.org>.
Jason End wrote:
> I was wondering if anyone would object to me rewriting
> the Plugin documentation. My understanding is that the
> 0.7 documentation isn't finished and hence I find some
> of the topics slightly confusing.
Please do. Documentation is never finished :-) and
there is always room for improvement. Do it in stages
if needed. Please send patches via the Jira Issue Tracker.
> I have some technical doubts that might require a
> couple answers from someone, but beyond that I'd have
> no problem doing the rewrite.
Please discuss any issues here on the dev list.
--David
Re: 0.7 Plugin Documentation
Posted by Ross Gardler <rg...@apache.org>.
[Please don't reply to a mail and change the subject completely it makes
the archives hard to search - start a completely new thread]
Jason End wrote:
> I was wondering if anyone would object to me rewriting
> the Plugin documentation. My understanding is that the
> 0.7 documentation isn't finished and hence I find some
> of the topics slightly confusing.
We welcome *any* contribution that you believe is an improvement to
*any* part of Forrest. Please go ahead.
> I have some technical doubts that might require a
> couple answers from someone, but beyond that I'd have
> no problem doing the rewrite.
At the moment there are only a few of us who have worked on plugins, so
the more questions that are asked about how and why it works the more
polished it will become. I'm ready to help where I can.
Ross
0.7 Plugin Documentation
Posted by Jason End <be...@yahoo.com>.
Hi,
I was wondering if anyone would object to me rewriting
the Plugin documentation. My understanding is that the
0.7 documentation isn't finished and hence I find some
of the topics slightly confusing.
I have some technical doubts that might require a
couple answers from someone, but beyond that I'd have
no problem doing the rewrite.
Jay
__________________________________
Do you Yahoo!?
Yahoo! Mail - You care about security. So do we.
http://promotions.yahoo.com/new_mail
Re: [RT] Per document skinconf (was Re: coloring table cells [from
the user list])
Posted by Ross Gardler <rg...@apache.org>.
Ross Gardler wrote:
> Nicola Ken Barozzi wrote:
>
>> Ross Gardler wrote:
...
> my-project/
> forrest.xml
> documentation/
> status.xml
> --> content.xml
> --> content.meta.xml
> ** all other content
> FORREST-INF/
> skinconf.xml
> --> pdf-output.conf.xml
> site.xml
> tabs.xml
> --> metadata.xml
Blasted email editor inserted tabs so the layout is wrong: this is what
I intended:
my-project/
forrest.xml
documentation/
status.xml
--> content.xml
--> content.meta.xml
** all other content
FORREST-INF/
skinconf.xml
--> pdf-output.conf.xml
site.xml
tabs.xml
--> metadata.xml
Ross
Re: [RT] Per document skinconf (was Re: coloring table cells [from
the user list])
Posted by Ross Gardler <rg...@apache.org>.
Nicola Ken Barozzi wrote:
> Ross Gardler wrote:
> ...
>
> I agree to the intent, and in fact I had done a similar proposal,
> although without considering the impact for the plugins.
>
> Read this and tell me what you think, and how the two may fit.
>
> [RT] Directory structure and configuration
> http://marc.theaimsgroup.com/?l=forrest-dev&m=110172138119333&w=2
>
I remember this RT now, it seems that my RT includes many of the meme's
planted by you in your original - this is a good sign. Lets discuss...
What is Meta-Data? What is Presentation Data?
=============================================
In re-reading your RT I discovered why I am not completely at ease with
the current skinconf.xml. We are confusing two types of data in the
skinconf.xml file. On the one hand there is true meta-data (data about
data), for example:
<project-name>Forrest</project-name>
and presentation data:
<disable-pdf-link>false</disable-pdf-link>
We have gotten away with this so far because we do not handle meta-data
separately. However, your RT and a post by Glen Tulikin
(http://marc.theaimsgroup.com/?l=forrest-dev&m=110324061019177&w=2)
start to look at how we can better handle true meta-data.
Unfortunately, your RT further blurs the distinction between true
meta-data and presentation data, for example:
<meta name="credits.title.name" content="Built with Forrest">
is meta-data, but:
<meta name="org.apache.forrest.disable-pdf-link"
content="true"/>
is presentation data.
I think to further blur things in this way would be dangerous. I tried
to avoid this in my RT by ignoring the meta-data aspect. I was hoping to
sneak it through without the need to move meta-data nearer the data
raising its head. However, your RT has the intention of being "able to
define metadata nearer to the file that needs it".
The problem is if we mix the two types of "meta" data "the file that
needs it" cannot be identified. I'll try to explain...
Handling Meta Data and Presentation Data
----------------------------------------
Meta-data is generated on a per file basis, with only a minority of
information coming from a central location. On the other hand,
presentation data has the majority of information coming from a central
location with only a minority being defined on a per file granularity.
This means that to be "able to define metadata nearer to the file that
needs it" we need to store the different types of data in different
locations. Meta-data needs to be closer to the file with an opportunity
to centrally define defaults (as per your RT) and presentation data
needs to be centralised with an opportunity to override locally to the
file (as per my RT).
Directory Structure
===================
How does this affect the proposed directory structure in your RT?
You propose:
my-project/
forrest.xml
documentation/
status.xml
** all other content
FORREST-INF/
skinconf.xml
site.xml
tabs.xml
This would become (arrows indicate changed/added lines):
my-project/
forrest.xml
documentation/
status.xml
--> content.xml
--> content.meta.xml
** all other content
FORREST-INF/
skinconf.xml
--> pdf-output.conf.xml
site.xml
tabs.xml
--> metadata.xml
Note that with the introduction of a meta-data plugin all the meta-data
files would be optional since the plugin would provide defaults.
Similarly the plugin conf.xml files are optional. So although this looks
like adding many new files, they are only present if actually needed by
a user.
(At Burrokeet I am doing some extensive work on Meta-Data at present, I
hope to be moving much of this into Forrest in 2-3 months, fortunately
Nicola's RT memes seem to be infecting my work there too :-)).
Ross