Re: [office-metadata] Re: Updated example

[Patrick Durusau <patrick@durusau.net>]

Bruce,

Bruce D'Arcus wrote:
>
> On Jun 21, 2007, at 10:20 AM, Svante Schubert wrote:
>
>> There are more restrictions aside of odf:idf-ref:
>>
>> First aside of idref the path of the odf:File is releveant.that is 
>> related by a odf:hasPart
>
> Sure.
>
>> Second odf:Citation is of type odf:Element as well. Remember it is 
>> just a rdf:Description with more rdf:types
>>    <rdf:type 
>> rdf:resource="http://docs.oasis-open.org/opendocument/meta/package#Citation"/>, 
>> but it has as well the
>>    <rdf:type 
>> rdf:resource="http://docs.oasis-open.org/opendocument/meta/package#Element"/> 
>>
>
> Svante: I know this! My point is the second type statement is not 
> necessary. We're not proposing to enforce that any reference to an ODF 
> content node include this type; are we?
>
Err, I didn't think we were enforcing (except where we say so, see 
below) any requirement on referencing. Such as type. I can see some 
advantages to it but I can also see why someone might not want to use it.
>> Third, odf: is meant to be a vocabulary that describes the 
>> OpenDocument format, as long citation is not specified we need some 
>> other namespace.
>
> Yes, I think we might as well standardize this part while we're at it. 
> I will suggest as much. The TC approved a citation field, so if I'm 
> going to suggest dropping it, I want something to take its place.
>
> What namespace it is in doesn't matter that much to me, but I do think 
> the "Reference" class ought to be fairly generic.
>
+1
> Finally, if the odf prefix is meant to relate on to the package, then 
> we should change the suggest prefix:
>
>     odfp?
>     package?
>
> ... I don't know.
>
I'm easy but I do think we need to keep a clean separation between odf 
for ODF stuff and other things. Just so that it is always clear which is 
which.

Hope everyone is having a great day!

Patrick
> Bruce
>
>
>

-- 
Patrick Durusau
patrick@durusau.net
Chair, V1 - US TAG to JTC 1/SC 34
Acting Convener, JTC 1/SC 34/WG 3 (Topic Maps)
Co-Editor, ISO/IEC 13250-1, 13250-5 (Topic Maps)
Co-Editor, OpenDocument Format (OASIS, ISO/IEC 26300)