Re: [office-metadata] RDF/A and ODF

[Elias Torres <eliast@us.ibm.com>]

Thanks Bernd for your endorsement and I totally agree that @content is
one of those attributes we need to look at and possibly do away with it
given our circumstances. Remember that (as Bruce said) in RDFa we are
supposed to only rely on that one document, but in ODF we have the
meta.xml for any other information. However, internal/external doesn't
solve the problem that some data is for a human to read and not for a
machine to parse. Maybe that's some food for thought.

[To all] I think I'm finally in this thing for real if you are reading
this note.

-Elias

Bruce D'Arcus wrote:
> 
> On Nov 27, 2006, at 10:39 AM, Bernd Schuster wrote:
> 
>>  I followed the discussion of the last meeting with great interest and
>> I aggree, that using RDF/A is a good approach to seamlessly integrate
>> meta data into ODF documents.
>>  What I'm concerned about is the "content" attribute in Ben's example
>> concerning the cal:dstart, because it leads to a situation where the
>> information which is human readable might be different from the
>> information which is processed by a machine.
> 
> I think we should pay close attention to where the design priorities of
> RDFa (namely integration with HTML and the importance of hand-authoring
> within a single-file context there) might diverge from those of ODF
> (GUI-based productivity applications, multi-file package structure,
> etc.), and adjust as necessary.
> 
> Bruce
> 
>