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


Help: OASIS Mailing Lists Help | MarkMail Help

office message

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

Subject: Re: [office] Re: [office-metadata] Re: [office] Suggested ODF1.2 items

On Dec 12, 2006, at 7:57 AM, Patrick Durusau wrote:

> But, let's not confuse what the user is "marking" with what is 
> happening on the other side of the screen. Say that a user selects 
> half a table and the following paragraph to attach some arbitrary 
> semantic. On the markup side of the screen, what is to prevent me from 
> using well formed markup to mark the half-table and paragraph 
> separately but pointing to the same arbitrary semantic?

Right, my point in the last note.

When we're talking about adding metadata within content, it'll be 
important for GUIs to be able to identify for the user the subject of 
that metadata.

I would expect, for example, that a table might have a contextual menu 
that would allow a user to add a metadata statement.

Perhaps, too, tables cells could do the same, or paragraphs, or spans.

But if a user does want to tag "half-a-table" with some metadata (can't 
imagine what!), then what are the subjects of those statements? The 
rows? The cells?

In any case, I just wanted to separate out the claim that we need a 
generic field (or maybe more than one) that can hook into the metadata 
system, and the question of what exactly that field looks like. I don't 
think the proposal Florian offered will work for citations (or other 
similar sorts of OOXML fields he wants to convert to/from).


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