Greetings! Notes from the ODF TC teleconference on 15 August 2022 follow below. Hope everyone is at the start of a great week! Patrick ********************** *Patrick:* quorum - yes *Patrick:* agenda - approved by consent *Patrick:* minutes from 8 August 2022 - approved by consent *Patrick:*
https://issues.oasis-open.org/browse/OFFICE-4024 *Patrick:*
https://www.oasis-open.org/apps/org/workgroup/office/email/archives/202208/msg00008.html *anonymous morphed into Svante* *Patrick:*
https://www.oasis-open.org/apps/org/workgroup/office/email/archives/202208/msg00009.html *Patrick:* Andreas - but we are talking about documents, not software - a strict conforming consumer cannot anticipate foreign namespaces *Patrick:* Andreas - do it for the extended document all the time, that's ok because can write for strict only *Patrick:* Andreas - problem is changing values to be included in strict conforming documents *Patrick:* Michael - was clear as to the original intent - but can say we don't agree with that and change it *Patrick:* Michael - we have to recognize this actually is a change - *Patrick:* Regina - prefix is in the value of an attribute - just a string - defined as a string - interpreted - something different not described in conformance clause - strings should be defined in the attributes *Patrick:* Regina - what should an application do for a namespace it doesn't know *Patrick:* Regina - D.3 should only say attributes only use ODF namespace - conform to part 4 - possible to omit prefix need not be here, change in the individual attributes *Patrick:* Regina - omit prefix/no prefix - say conformance refers to the namespace used by an attribute value - under attributes - says which namespaces it allows *Regina Henschel:* The specification of style:condition (19.472), table:condition (19.600), table:expression (19.639), table:formula (19.646) and text:formula (19.811) determines a namespace to be used for the attribute value. This namespace determines the syntax and semantics of formulas or expressions in the attribute value. If the namespace to be used is the "urn:oasis:names:tc:opendocument:xmlns:of:1.2" namespace, then the formulas and expressions shall conform to Part 4 of this specification. *Patrick:* Thanks! *Patrick:* The namespaces used for attribute values by style:condition (19.472), table:condition (19.600), table:expression (19.639), table:formula (19.646) and text:formula (19.811) are defined by those attributes. *Patrick:* The namespace used for an attribute value by style:condition (19.472), table:condition (19.600), table:expression (19.639), table:formula (19.646) and text:formula (19.811) are defined by those attributes. *Patrick:* The namespace used for the attribute value by style:condition (19.472), table:condition (19.600), table:expression (19.639), table:formula (19.646) and text:formula (19.811) is defined by those attributes. *Patrick:* + If the namespace used is the "urn:oasis:names:tc:opendocument:xmlns:of:1.2" namespace, then the formulas and expressions shall conform to Part 4 of this specification. *Regina Henschel:* + If this namespace is the "urn:oasis:names:tc:opendocument:xmlns:of:1.2" namespace, then the formulas and expressions shall conform to Part 4 of this specification. *Patrick:* Proposed D.3) The namespace used for the attribute value by style:condition (19.472), table:condition (19.600), table:expression (19.639), table:formula (19.646) and text:formula (19.811) is defined by those attributes. If this namespace is the "urn:oasis:names:tc:opendocument:xmlns:of:1.2" namespace, then the formulas and expressions shall conform to Part 4 of this specification. *Patrick:* Another D.3) The namespace used for the formulas and expressions in attribute value by style:condition (19.472), table:condition (19.600), table:expression (19.639), table:formula (19.646) and text:formula (19.811) is defined by those attributes. If this namespace is the "urn:oasis:names:tc:opendocument:xmlns:of:1.2" namespace, then the formulas and expressions shall conform to Part 4 of this specification. *Patrick:* added an: The namespace used for the formulas and expressions in an attribute value by style:condition (19.472), table:condition (19.600), table:expression (19.639), table:formula (19.646) and text:formula (19.811) is defined by those attributes. If this namespace is the "urn:oasis:names:tc:opendocument:xmlns:of:1.2" namespace, then the formulas and expressions shall conform to Part 4 of this specification. *Regina Henschel:* The namespace used for the attribute value by style:condition (19.472), table:condition (19.600), table:expression (19.639), table:formula (19.646) and text:formula (19.811) is defined by those attributes. If this namespace is the "urn:oasis:names:tc:opendocument:xmlns:of:1.2" namespace, then the formulas and expressions in the attribute value shall conform to Part 4 of this specification. *Francis Cave:* The namespace used for the value of any of the attributes style:condition (19.472), ... *Patrick:* The attributes style:condition (19.472), table:condition (19.600), table:expression (19.639), table:formula (19.646) and text:formula (19.811) define namespaces for their values. *Patrick:* Francis agrees with Andreas this will be a change and an significant change at that *Patrick:* If the namespace is "urn:oasis:names:tc:opendocument:xmlns:of:1.2" namespace, then the formulas and expressions in the attribute value shall conform to Part 4 of this specification. *Patrick:* Latest suggestion in full: The attributes style:condition (19.472), table:condition (19.600), table:expression (19.639), table:formula (19.646) and text:formula (19.811) define namespaces for their values. If the namespace is "urn:oasis:names:tc:opendocument:xmlns:of:1.2" namespace, then the formulas and expressions shall conform to Part 4 of this specification. *Regina Henschel:* The attributes style:condition (19.472), table:condition (19.600), table:expression (19.639), table:formula (19.646) and text:formula (19.811) define namespaces for their values. If the namespace is "urn:oasis:names:tc:opendocument:xmlns:of:1.2" namespace, then the formulas and expressions in the attribute value shall conform to Part 4 of this specification. *Patrick:* The attributes style:condition (19.472), table:condition (19.600), table:expression (19.639), table:formula (19.646) and text:formula (19.811) define namespaces for formulas and expressions in their values. If the namespace is "urn:oasis:names:tc:opendocument:xmlns:of:1.2" namespace, then the formulas and expressions in the attribute value shall conform to Part 4 of this specification. *Patrick:* Regina - in their values - can be several expressions with a different namespaces - one namespace for all the values in an attribute *Patrick:* Reginas proposal: The attributes style:condition (19.472), table:condition (19.600), table:expression (19.639), table:formula (19.646) and text:formula (19.811) define namespaces for their values. If the namespace is "urn:oasis:names:tc:opendocument:xmlns:of:1.2" namespace, then the formulas and expressions in the attribute value shall conform to Part 4 of this specification. *Patrick:* Andreas - are there restrictions on what other namespaces can do? *Patrick:* Regina - we can say what consumers should do if they don't understand? *Patrick:* Andreas - can we require a different namespace to publish what it means? *Patrick:* Andreas - dependent vs. defined - does different namespace need to be defined? *Patrick:* Andreas - if a different namespace, can I secretly do whatever I want? *Patrick:* Good point Andreas *Patrick:* Svante - want request - other namespaces will be defined? *Patrick:* Andreas - thinking about required *Patrick:* Andreas - namespace has to have some meaning attached to it *Patrick:* Andreas - simply pointing to definitions would be enough *Patrick:* Regina- something a producer has to do - not the file *Patrick:* Regina - would be a sentence for other namespaces in attributes - must define the syntax and semantics - in the individual attributes *Patrick:* Andreas - could put here to point to where attributes are defined *Patrick:* Adjourned -- Patrick Durusau
patrick@durusau.net Technical Advisory Board, OASIS (TAB) Editor, OpenDocument Format TC (OASIS), Project Editor ISO/IEC 26300 Co-Editor, ISO/IEC 13250-1, 13250-5 (Topic Maps) Another Word For It (blog):
http://tm.durusau.net Homepage:
http://www.durusau.net Twitter: patrickDurusau Attachment: OpenPGP_signature Description: OpenPGP digital signature