Questions on the RDFa split solution..

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

Hi Bruce,

I need some clarifications on your example:

Bruce D'Arcus wrote:
>
> On Jan 10, 2007, at 9:06 AM, Michael Brauer wrote:
...
>
>> For the office application it is enough, because it knows that the 
>> spans belong together. But a RDF application that processes the 
>> document takes the two spans as different properties (correct me if 
>> I'm wrong, but that's what you said above). So it would interpret the 
>> metadata differently than intended.
>
> I would expect that an RDF application would process an ODF file like 
> this:
>
> 1) read the manifest and look for RDF/XML files; load them up directly
> 2) read the content file for the triples there, and load them in 
> (merging happens automatically via the URIs)
>
> On 2, if it comes across a property node with the attribute we've been 
> talking about, it knows it first has to merge the literal with the 
> other node(s) sharing the same attribute value.
>
> In either case, we basically have to define the processing mechanism. 
> But the solution I'm suggesting here has the virtue that it solves 
> these problems in a simple way that is friendly to both RDF and 
> regular XML tools.
Yes, your approach below seems to be a computable solution to avoid the 
problem of split object literal in conjunction with RDFa.

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< ---------------------

Let me see if I understand your example correctly.
I assume that you want to give three RDF statements in your example :

The first is easy as it is from standardized RDF XML:
"http://ex.net/foo"; has the predicate ex:status with the external 
resource "http://ex.net/Important"; as object.

The second is easy as well, as it was the problem:
A subject "http://ex.net/x"; has the predicate ex:title, which object is 
the literal "Some title"

The third is a little puzzling, I guess you want to say something like:
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?

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.

Regards,
Svante