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] fields proposal



OK.

On Mar 26, 2007, at 6:14 AM, Svante Schubert wrote:

> I assume there is only one rule:
> All ODF application that do not want to support metadata should be 
> able to display a document with metadata similar to any other ODF 
> application.

Agree.

> Due to this, whenever a string is similar to a RDF literal and being 
> edited in the viewed content, the string and the RDF statement have to 
> be in-content (the RDFa approach).
> For any other metadata there exist no rule nor a guideline. The choice 
> is completely up to the RDF application.
> For example, the content created from a RDF application based on 
> metadata - viewed in the document - is placed in a text:meta-field. 
> But how the RDF statements are attached to the field (in-content vs. 
> RDF/XML) is irrelevant.

This I don't agree with. We have to account for the in-content encoding 
in the RELAX NG schema and spec, or it won't be an option.

My use case requires that the citation fields be round-trippable 
between different ODF applications (and also, realistically, other 
formats). So I'd like us to keep that requirement in mind when deciding 
on this.

> Moreover if the field had been generated by some algorithm, the 
> description of this process does not have to be part of the document. 
> For example, when a plugin would offer the relation between "Last  
> Tuesday of the year" to a xsd:date.

Agree.

Bruce



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