generic structured fields, citations

On 10/23/06, Jakob Lechner <jakob.lechnerfabalabs.org> wrote:
> On Thu, 2006-10-19 at 12:49 -0400, Bruce D'Arcus wrote:
> > I'm not so sure I agree about the "should be
an xpath expression" or
> > how you've precisely framed this (accessing the
property directly).
> >
> > > The field could stored in the content.xml
file like this:
> > > <textml-fi
eld text:name="field1"
xlink:href="customXml/item1.xml"
> > > xpath="/contacts[0]/surname" />
> >
> > See some brainstorming ideas I've posted:
> >
> > <http://wiki.oasis-open.org/office/Metadata_Fie
ld_Brainstorming>
>
> I thought about your suggestions on the site you posted
your ideas.
> Basically I agree with you that it would be a good idea
to associate
> metadata using an IRI, but this presumes that the
corresponding xml
> element actually has such an IRI for identification.

Yes, but the IRI could be a local ID. Is there any reason
why you
would not add an ID to any given item?

> The idea behind my xpath suggestion was to be able to
associate
> arbitrary xml tags.

Yes, I understand. The trick is how best to do this.

> Beside that: What if I wanted to change the association
currently
> pointing on the first contact, so it points on the
second or third
> contact. With an xpath you could just try to locate the
element
> using "/contacts[1]/surname" instead of
"/contacts[0]/surname".

Why do you need to use a positional xpath here? Why not just
identify
the item you want directly  (maybe
"Contacts#doej") and use some other
mechanism to say you want the surname property displayed?

Bruce

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribesw.openoffice.org
For additional commands, e-mail: dev-helpsw.openoffice.org