OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

office-metadata message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [office-metadata] meta-field and more...


Svante.Schubert@Sun.COM wrote on 05/10/2007 03:06:59 PM:

>
>
> Elias Torres wrote:
> > "Bruce D'Arcus" <bruce.darcus@OpenDocument.us> wrote on 05/10/2007
02:40:37
> > PM:
> >
> All applications need to establish the relation between a
> text:meta-field and the owning application, which can be a plug-in.
> As written earlier this would sufficient to solve this problem.
>
> <odf:Element odf:idref="id" rdf:about="uri:elementURI">
>       <odf:belongsTo rdf:resource="http://someNamedGraph"/>
> </odf:Element>
>
> Does anyone see a problem by doing so? As it is in the current draft ;-)
> Svante

I do. I think we are slipping in application specific stuff that's
underdefined and makes for bad specs.

what does belongTo mean? can an element belongTo to only one plugin? is it
a plugin or a someNamedGraph? why a graph? I thought we were trying to
attach the element to a plugin not the named graph that has its
authoritative content.

Before we put this into the spec, I want to know what is the problem we are
trying to solve, defined (hopefully already in our requirements document).

I don't want to make a big stink if many are in support of this, especially
if someone like Florian backs it up, but I would like more convincing that
this is our responsibility and it's not Svante thinking from an ODF
application perspective as opposed from a metadata extraction one.

At least, I'm going down in the record as this is over-specification.

-Elias



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]