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


Help: OASIS Mailing Lists Help | MarkMail Help

office message

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

Subject: Metadata Fields


A new issue that I had not previously noted.

6.5.1 – 6.5.19, inclusive. All the text in these sections refer to a 
“document.” However, note that all these elements are children of 
|<text:a>| 5.1.4, |<text:h>| 4.1.1, |<text:meta>| 5.1.5, 
|<text:meta-field>| 6.5.19, |<text:p>| 4.1.2, |<text:ruby-base>| 5.4.1 
and |<text:span>| 5.1.3 elements. None of which represent documents.

Could mean the document being edited, but then we would have to say that 
all <text:initial-creator> elements, for instance, must have the same 
value. Since that element may occur as a child of every <text:p> element.

Could mean that the metadata in question applies to the elements specified.

This problem also occurs with 6.3.6 – 6.3.11, and 6.3.2 – 6.3.5, inclusive.


1. Say that the metadata fields apply to their parent elements. (Would 
we need to say something about displaying those fields?)

2. Could change the schema to attach these fields to elements that 
represent "documents." And to remove them from elements that don't. 
(Note that this would not be backwards compatible.)

I don't have a default position to suggest. I can't count the number of 
times I have read this section and simply missed this issue.


Hope everyone is at the start of a great week!


Patrick Durusau
Chair, V1 - US TAG to JTC 1/SC 34
Convener, JTC 1/SC 34/WG 3 (Topic Maps)
Editor, OpenDocument Format TC (OASIS), Project Editor ISO/IEC 26300
Co-Editor, ISO/IEC 13250-1, 13250-5 (Topic Maps)

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