Re: [office] text:meta-field

[Patrick Durusau <patrick@durusau.net>]

Bruce,

Bruce D'Arcus wrote:
> On 10/30/07, Patrick Durusau <patrick@durusau.net> wrote:
>   
>> Bruce,
>>
>> Bruce D'Arcus wrote:
>> <snip>
>>     
>>>> But the first question I would ask is for an example of a
>>>> "multi-paragraph spanning" input field.
>>>>         
>>> Patrick, Florian's already posted an example. See top-of-thread.
>>>
>>>       
>> Is Oliver's restating of it:
>>
>>     
>>> <p>XXX</p>
>>> <new-input-field|new-meta-field>
>>>     <field-prefix>AAA</field-prefix>
>>>     <p>BBB</p>
>>>     <p>CCC</p>
>>>     <field-suffix>DDD</field-suffix>
>>> </new-input-field|new-meta-field>
>>> <p>ZZZ</p>
>>>       
>> Equivalent to Florian's example?
>>
>> I looked at Florian's example:
>>
>>     
>>> Sample:
>>> <p>Comments: <text:meta-field-start/>This is a </p>
>>> <p>two line comment<text:meta-field-end/></p>
>>>       
>> And it looks like an unnecessarily complicated markup model. Can say
>> exactly what Florian wants to say but it isn't necessary to have
>> overlapping paragraph (or other) elements to do it.
>>
>> Noting that with Oliver's solution, we preserve the ability of an
>> application to simply render the text content of a paragraph.
>>     
>
> Yeah, the more I think about it, the more this looks like the
> territory for inline metadata. E.g. this is a case where you want to
> tag the literal document content with some semantics. I always assumed
> a field to be different.
>
>   
Well, I don't know this makes a case for "inline" metadata but simply 
that you need to apply metadata to the content. I am not sure that 
"inline" really has any meaning in a UI based environment. It could be 
"inline" or it could be by reference, really hard to say from the user's 
perspective. Granted that for processing reasons you could choose inline 
to simply lessen the load on the application but shouldn't the end 
result, the application of the metadata be the same?

Hope you are having a great day!

Patrick

-- 
Patrick Durusau
patrick@durusau.net
Chair, V1 - US TAG to JTC 1/SC 34
Acting Convener, JTC 1/SC 34/WG 3 (Topic Maps)
Co-Editor, ISO/IEC 13250-1, 13250-5 (Topic Maps)
Co-Editor, OpenDocument Format (OASIS, ISO/IEC 26300)