- From: Dan Connolly <connolly@w3.org>
- Date: 16 Jun 2003 09:04:05 -0500
- To: "Henry S. Thompson" <ht@cogsci.ed.ac.uk>
- Cc: Dominique Hazaël-Massieux <dom@w3.org>, Joseph Reagle <reagle@w3.org>, spec-prod@w3.org
On Mon, 2003-06-16 at 04:26, Henry S. Thompson wrote:
> Dominique Hazaël-Massieux <dom@w3.org> writes:
>
> > The real data are at:
> > http://www.w3.org/2002/01/tr-automation/tr.rdf
>
> Any chance of getting a stable ID on each of the entries in that
> document? Then I'll put together a two - stage XML Pipeline (XInclude
> plus XSLT) which will give everybody exactly what they want.
>
> Something of the form
> . . . id="http:__www.w3.org_TR_2001_REC-SVG-20010904"
> would do the job.
Er... but RDF IDs have to be XML names.
Each entry already has an about attribute...
<NOTE rdf:about="http://www.w3.org/1999/04/Editing/01">
what could you do with id that you can't do with about?
> The following template will add this to the existing doc't:
>
> <xsl:template match="/rdf:RDF/*[@rdf:about]">
> <xsl:copy>
> <xsl:attribute name="id">
> <xsl:value-of select="translate(@rdf:about,'/','_')"/>
> </xsl:attribute>
> <xsl:apply-templates select="@*|node()"/>
> </xsl:copy>
> </xsl:template>
>
> but it would be better to include this functionality somewhere in the
> production process -- I couldn't quite figure out where that should be.
>
> [Note that the nice overview at [1] is not quite as useful as it might
> be, because lots of the links therein are broken :-(]
>
> ht
>
>
> ______________________________________________________________________
> [1] http://www.w3.org/2002/01/tr-automation/
--
Dan Connolly, W3C http://www.w3.org/People/Connolly/
Received on Monday, 16 June 2003 10:03:57 UTC