- From: Dan Brickley <danbri@w3.org>
- Date: Sat, 18 Jan 2003 18:33:15 -0500
- To: "Henry S. Thompson" <ht@cogsci.ed.ac.uk>
- Cc: www-archive@w3.org, mf@w3.org
* Henry S. Thompson <ht@cogsci.ed.ac.uk> [2003-01-18 23:21+0000]
> > xsltproc logicOut.xsl po-mapped.xml > po-fopl.xml
> > po-mapped.xml:2: error: Empty namespace name for prefix ns2
> > urs="" map:maxOccurs="" map:type-to="individual" map:type-name="{}PurchaseOrder
> > ^
> > warning: failed to load external entity "standardBuiltins.xml"
> >
> > This is referenced in logicOut.xsl:
> > <xsl:variable name="standardBuiltins" select="document('standardBuiltins.xml')/map:pings"/>
>
> attached.
Lost in transit! Could you try re-sending? I didn't see any attachments...
> > Anyhow we get some output, fopl and java files.
> >
> > Trying the fopl htmlizer, however, I only get message in the html
> > complaining required parameter missing: group [yes|no]; presumably
> > something which went wrong earlier has screwed things up?
>
> Oops, bug in 00README, should include group=yes on command line (I
> don't know how xsltproc takes command line param settings).
xsltproc --stringparam group no fopl.html.xsl po-fopl.xml > po.fopl.html
...works beautifully :)
> > On the brightside, po-fopl.xml is very nice. I can see how this maps to RDF quite easily.
> > The only change I'd seek, at first glance, is for the relation name to be
> > URI-based.
> >
> > Where you have:
> >
> > <fopl:relation name="street">
> > <fopl:pointer ref="id2589284"/>
> > <fopl:atom type="string">123 Maple Street</fopl:atom>
> > </fopl:relation>
> >
> > we need something like
> >
> > <fopl:relation name="http://example.com/some-ns/#street">
> > <fopl:pointer ref="id2589284"/>
> > <fopl:atom type="string">123 Maple Street</fopl:atom>
> > </fopl:relation>
> >
> >
> > Presuambly the mapping vocab could carry such info?
>
> Or, better I think, just change logicOut.xsl to output what you want,
> since it's systematic.
I did that for now, for the ntriple generator I just sent (rdfOut.xsl).
However it does seem like knowing a URI for each edge-type / property in the
graph is something that will be common across many of the output formats. Is the
required information already in po-mapped.xml?
Dan
Received on Saturday, 18 January 2003 18:33:20 UTC