I do not wish to argue over what is a non-issue, so please see the
following as an augment rather than a rhetorical opposition . . .
 
On Tue, 30 Nov 1999 Jean-Francois Gauvin wrote:
 
> I agree with Sebastian on this matter Guy,
 
> Here at the University of Montreal we use an Access database to manage
> the metadata to our theses. Then, with an export module we convert to
> the TEIHeader, DC in HTML, and other interchange formats. We haven't
> programed the RDF export template yet since we are waiting to see IF it
> is worthwhile to use this format.
 
Of course if there is no need in your current work to develop the RDF
template, then don't-- but at the same time, that perspective is not
likely to successfully generalize as policy outlook . . . cf. the close
interworking of the DC team _with_ the RDF team.  RDF _is_ on the future
itinerary of where metadata is headed.  Rather than debate an abstracted
"if", it would seem an engaging dialogue on this list regarding how to
integrate TEI-header and DC/RDF (frequently these latter two are _already_
namespaced together) would produce fruitful forward-compatibility.
 
On Mon, 29 Nov 1999, Guy Teasdale wrote:
 
> Thanks John Robert,
>
> We hope that the Teiheader will be produced by the students. To this ends,
> we are setting up a FileMaker Database on the web that will be used by the
> students to enter themselves their cataloguing information. Then, always
> As I don't want to make all these efforts if TEAHEADER is eventually
> going to an RDF schema, I asked this question.
 
in deference to Jean-Francois, I would say that it is certainly prudent to
wait before sweating the the set up you describe here . . . XSL/T will
certainly make a lickety-split-quick business of changing it down the
road.  That said . .. .
 
> Some of you already answered me privately that there is no indication that
> RDF will eventually be used on the Web. I personnaly think  that as there
> are already 800 millions of documents on the Web, a metadata framework is
> essential. If the TEI community is going to port TEILITE to XML, I am just
> asking, are there any reflexions being also made to port the TEIHEADER to
> RDF ? Is it an option ? why and why not ?
 
this is a relatively quiet list and some development dialogue towards
general TEI-header interfacing--using XSL/T since it is now a standard (as
of Nov. 16, a Rec. of W3C)--would provide all of us with tools for
"crosswalking" our meta-data materials for the different formats.
Debating whether or not one format or another will become ubiquitous (as
RDF likely will be at any rate) is best left to the developer's lists,
while working with tools we now have in order to address current _and_
future meta-data wrappers and headers is a viable and worthy exercise.
 
respectfully,
 
jr