XMP uses a subset of RDF/XML, with a few limitations thrown in to make
reification and provenance tracking impossible, but hey who needs metadata.
I'm not sure if XSLT is particularly well suited to anything, but it ought
to be possible to cruft something up. I would still recommend following
Owen's suggestion of using an RDF toolkit of some kind to take hide the
details of any sequences etc. I can point you at a few people at NIST who
might be able to give some advice.
What does ContentMFDM expect in it's tab separated files?
Simon
On Mon, Jan 14, 2013 at 2:56 PM, Owen Stephens <[log in to unmask]> wrote:
> I'm not familiar with what XMP RDF/XML looks like but it might be worth
> using an RDF parser rather than using XSLT?
>
> Graphite (http://graphite.ecs.soton.ac.uk/) is pretty easy to use if you
> are comfortable with PHP
>
> Owen
>
> On 14 Jan 2013, at 19:09, Kyle Banerjee <[log in to unmask]> wrote:
>
> > On Sat, Jan 12, 2013 at 1:36 PM, Michael Hopwood <[log in to unmask]
> >wrote:
> >
> >> I got as far as producing XMP RDF/XML files but the problem then
> remains;
> >> how to usefully manage these via XSLT transforms?
> >>
> >> The problem is that XMP uses an RDF syntax that comes in many flavours
> and
> >> doesn't result in a predictable set of xpaths to apply the XSLT to.
> >
> > XSLT is not a good tool for many kinds of XML processing. In your
> > situation, string processing or scanning for what tags are present and
> then
> > outputting in delimited text so you know what is where is probably a
> better
> > way to go.
> >
> > kyle
>
|
