On Wed, May 29, 2002 at 11:35:31AM +0100, Chris Croome wrote:
> On Wed 29-May-2002 at 10:26:44AM +0200, Thomas Baker wrote:
> > And now, after working with these flat text files for awhile and
> > finding them _very_ easy to maintain (once set up) -- you edit them
> > with a plain text editor, everyone can read them, I can paste them
> > into email messages, etc -- I am now wondering whether the flat text
> > files could be the upstream origin of the entire work-flow.
>
> If the text files had a little bit more information added using XHTML
> (class and id attributes or whatever works) would it be possible to use
> XSLT to transform them into RDF and the other versions that are needed?
This is exactly the sort of suggestion I am looking for.
I already add some XHTML to the flat text files in the form
of Web-page anchors such as "<a name=title-003>".
> Something along the lines of the XSLT used to generate RSS RDF from
> http://www.w3.org/ -- see here:
>
> http://www.w3.org/2000/08/w3c-synd/#
Hmm, Opera and IE 5.0 didn't understand the hash at the end, but
http://www.w3.org/2000/08/w3c-synd/ looks interesting.
> For example you noted that the HTML version is missing lang:
>
> -- Only the RDFS specifies lang="en" for the label and definition.
>
> Could these be added something like this?
>
> <a name=title-003>
> VMS-ID: title-003
> Name: title
> URI: <a HREF="http://purl.org/dc/elements/1.1/title">http://purl.org/dc/elements/1.1/title</a>
> Label: <span xml:lang="en">Title</span>
> Definition: <span xml:lang="en">A name given to the resource.</span>
>
> I realise that this would be a fairly evil hack... but if it works and makes
> maintenance easy...
This would indeed be easy, though in this case -- since I am
only maintaining the English version -- I should think that
a Perl script for converting this data could be written to
add lang="en" to every "Label:" and "Definition:", the only
fields that need such treatment.
I'm curious about the "<a HREF" in the example above
-- did you add it? -- because the "urlified" page at
http://www.gmd.de/People/Thomas.Baker/usage/terms/dc already
surrounds the title URI with an "<A HREF" (using an uppercase
A) -- generated by a Perl script.
Anyway, this is exactly the type of suggestion I am looking
for -- minimal markup that will make it easier to transform
my text file into whatever it needs to be transformed into,
whether Web pages or RDF.
Thanks,
Tom
--
Dr. Thomas Baker [log in to unmask]
Institutszentrum Schloss Birlinghoven mobile +49-171-408-5784
Fraunhofer-Gesellschaft work +49-30-8109-9027
53754 Sankt Augustin, Germany fax +49-2241-14-2619
|