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

 


Help: OASIS Mailing Lists Help | MarkMail Help

office-metadata message

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


Subject: Re: [office-metadata] Multiple content nodes representing on RDFsubject




Bruce D'Arcus wrote:
>
> On Dec 22, 2006, at 11:03 AM, Svante Schubert wrote:
>
>> Just imagine there is a certain text with semantic in the content:
>>
>> <text:p xml:id="_foo1">This is an important and divvikult text!</text:p>
>>
>> which is part of a N3 statement:
>>
>> <#_foo1> <#isImportant> "This is an important and divvikult text!"
>
> Note that there's no way to derive this statement from what you 
> presented above. All you are doing above in the XML is identifying the 
> node (as a *possible* subject).
>
> To do that, you'd need some additional RDF/XML (or use the meta 
> attributes we've been promoting):
>
> <rdf:Description rdf:about="content.xml#_foo1">
>   <ex:isImportant>This is an important and divvikult 
> text!</ex:isImportant>
> </rdf:Description>
>
> This would generate your triple.
>
> Of course, that's a little strange, and makes more sense to do:
>
> <rdf:Description rdf:about="content.xml#_foo1">
>   <ex:status rdf:resource="http://ex.net/Important";>
> </rdf:Description>
Exactly. The metadata RDF XML was presumed. Thank you for clarifying this.
>
>> Now a user recognizes an error in the text and marks a subset with a 
>> different vocabulary.
>>
>> <text:p xml:id="_foo1">This is an important and </text:p>
>> <text:p xml:id="_foo2">divvikult</text:p>
>> <text:p xml:id="_foo3"> text!</text:p>
>>
>> By this a new RDF statement has been added into the existing text
>>
>> <#_foo2> <#typingError> "divvikult"
>>
>> Furthermore the earlier N3 statement has changed as well, as the sum 
>> of (<#_foo1> + <#_foo2> + <#_foo3>) representing now the earlier 
>> important text.
>
> ...
>
> Maybe I'm just missing something, but am not understanding the problem 
> here. Moreover, I still think you're not understanding the data 
> modeling issues (the RDF). Perhaps we can see if there's a way to 
> clarify?

Hmm.. I will try to reach you by phone, we might avoid long mailing 
threads before x-mas ;-)

Bests,
Svante



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