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: Splitting View and Model



On Dec 19, 2006, at 11:09 AM, Michael Brauer - Sun Germany - ham02 - 
Hamburg wrote:

> It's maybe a stupid question, but why can't you use the date field 
> described in section 6.2.1, which inserts a date into a document, 
> instead of modeling this with metadata?

We're designing a generic metadata system. And as Elias explained, 
dates are just one example of this sort.

> Independent of that, what are the benefits of knowing that the string 
> ###localized data### string is date 2005-08-01 if that date is not 
> related to any other information?

Right now fields in ODF distinguish between the normalized string and 
the localized presentation, so I'm not really sure why you guys are 
picking on Elias on this point.

> I would understand that example if the date would be a metadata of 
> some other subject (let's say a camera purchase). But in this case, 
> wouldn't it be more appropriate to keep all the data about the camera 
> purchase in one place, and to reference them from the content?

This is the "going in circles" issue that Elias is frustrated with.

Elias and I are proposing a way that you can have the same model in 
content and in the package, so that in effect which you use ought to be 
a decision of a user and/or implementor.

I think we need to settle this issue once and for all tomorrow. I hope 
Elias' demo will help clarify.

Bruce



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