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


Hi Patrick,

Patrick Durusau wrote:
> Svante,
>
> Ok, so the problem is multiple segments of text (contained in 
> different ODF elements) to which I want to attach RDF metadata.
>
> Hmmm, well, using your table example, I am making the simplifying 
> assumption that the cells are contained in the same row.
The only reason I introduced the table was to split the content. The 
table itself has no meaning, the significant content was split into two 
paragraphs before and after the table.
>
> As I understand Elias's presentation last week, if my subject was 
> Bruce D'Arcus I would have an rdf:about="someURI" attribute on the 
> container element and then on the multiple segments would have the 
> attributes that complete two separate RDF triples, one for "Bruce" and 
> one for "D'Arcus", but both of those "roll up to" the subject, which 
> is shown by the rdf:about attribute.
>
The problem is that not each substring is the name for themselves, but 
the concatenated substrings in the right order is the name.
> It will probably make real RDF experts cringe but last night I was 
> thinking that the container with rdf:about="someURI" is similar to 
> inheritance of attributes.
>
> That is that we are accustomed to saying that an element inherits 
> attributes from a parent element. Makes it easier to be consistent and 
> saves typing on the elements that inherit the attribute.
>
> While it certainly could be the case that an entire RDF triple could 
> be written on every segment in the example it is easier to simply 
> specify the subject only once and allow that to be "inherited" by 
> subsequent other parts of an RDF triple within a container.
>
> Noting that the "inheritance" in this case is interrupted by a 
> container element with an rdf:about attribute as opposed to the 
> occurrence of another attribute and that it goes the opposite way from 
> what we usually describe as inheritance.
The three ODF containers are siblings no parent-child hierarchy. First a 
paragraph with first part of name, table splitting it with arbitrary 
content, than second paragraph with last part of name.
Two parts of the name are used as one.
Sure nobody would split a name with a table, but is it always such obvious?
>
> NOTE: I have *not* seen the notion of inheritance used in any RDF 
> literature so please don't repeat it unless some RDF expert thinks it 
> bears repetition.
>
> Hope you are having a great day!
>
> Patrick
>
> Svante Schubert wrote:
>
>> Hi Patrick,
>>
>> Patrick Durusau wrote:
>>
>>> Svante,
>>>
>>> Just an understanding check:
>>>
>>> So you are saying that there are discontinous (in the sense of being 
>>> contained in separate ODF elements) segments of text that I want to 
>>> treat as a single subject.
>>>
>>> Yes?
>>
>> Correct.
>>
>>>
>>> So I need a mechanism to gather them up so that set of segments can 
>>> be treated as a single entity for purposes of attaching RDF 
>>> metadata. Yes?
>>>
>>> Just want to make sure I understand the example.
>>
>> This is exactly the scenario.
>>
>>>
>>> Hope you are having a great evening!
>>
>> Till later,
>> Svante
>>
>>
>>
>>
>
Best regards,
Svante


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