Re: [office-metadata] Questions on the RDFa split solution..

[Svante Schubert <Svante.Schubert@Sun.COM>]

Hi Bruce,

thanks for the answers so far, something is left..

Bruce D'Arcus wrote:
>> Your example:
>> --------------------- 8< ---------------------
>>
>> <text:p meta:class="http://ex.net/foo";>
>>  <text:span object:id="xyz" meta:about="http://ex.net/x"; 
>> meta:property="ex:title">Some </text:span>
>> </text:p>
>> <text:p meta:class="http://ex.net/foo";>
>>  <text:span object:id="xyz" meta:about="http://ex.net/x"; 
>> meta:property="ex:title">Title</text:span>
>> </text:p>
>>
>> ... and in the package:
>>
>> <rdf:Description rdf:about="http://ex.net/foo";>
>>  <ex:status rdf:resource="http://ex.net/Important"/>
>> </rdf:Description>
>>
>> There are three subjects here:
>>
>> 1) two blank node paragraphs
>> 2) an external resource (another document) represent by the URI 
>> "http://ex.net/x";
>>
>> --------------------- 8< ---------------------

>> The parent paragraph is of type "http://ex.net/foo";, therefore the 
>> literal "Some Title" is as well important?
>> Does your example even tell that  "http://ex.net/foo"; as the the 
>> property "ex:title" with the Object "Some Title" as well?
What about the statement above? Is this valid by coincidence? The 
Paragraph is using the content of a child, why not the properties? How 
is this defined?

>> It would help me, if you show it in RDF XML. How would all statements 
>> look like, if the user had exported them to RDF XML?
>> It is obvious, that import and export of all RDF information as RDF 
>> XML will be an important scenario for us, which we should keep in mind.

> I assume you already know the first two. The third one is an example 
> of a blank node: a resource without a URI. In RDF/XML it would be:
>
> <rdf:Description>
>   <rdf:type rdf:resource="http://ex.net/foo"/>
> </rdf:Description>
>
> I am just using the RDF type there to hang different propeties off of 
> it (without having to use a URI).
Could you write them for me all together in a single RDF XML file? As I 
think this is what would be exported to the user in the end.
Some piece is missing for me, maybe you can help me out. (We might reuse 
this as one of the scenarios solutions to be compared on).

>
> Note: I'm really not sure how Elias or other RDF experts would feel 
> about how I've done that, but it seems to be one mechanism.
You are now our RDFa representive, I think you make a good work on this. 
Although I am not sure, if I a should favor RDFa or a RDF XML only 
approach, which references only to the ODF parts.
Saying, I dislike something or believe the other is better is of course 
not sufficient. I really hope we can make the current approaches 
comparable on some low level RDF use cases, like those on
http://wiki.oasis-open.org/office/Metadata_RDF_use_case


Looking forward to solve the Gordian knot ;-)
Svante