[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Updated: (OFFICE-702) Public Comment:OpenDocument 1.2v7-02: 1.3 Namespaces
[ http://tools.oasis-open.org/issues/browse/OFFICE-702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Hamilton updated OFFICE-702: ----------------------------------- Resolution: Adapt section 1.4.2.4 clause (D4.4) to --- All table:formula attribute values shall be in the form that begins with a namespace prefix. The prefix shall be bound to the urn:oasis:names:tc:opendocument:xmlns:of:1.2 namespace. --- Adapt 17.3.15 formula to: --- A string containing a formula. Formulas do not have a predefined syntax, but should follow a namespace prefix after a ":" separator. The namespace bound to the prefix determines the syntax and semantics of the formula. --- Adapt 17.3.19 namespacedToken to --- Attribute values of namespacedToken type shall have Namespace PrefixedName syntax [xml-names]. The attribute value taken as a qualified name shall satisfy the "Namespace constraints [xml-names]" in the place where an attribute having a value of this type occurs. The namespacedToken value signifies the expanded name that is the resulting unique interpretation of the qualified name. --- Adapt 18.15.1 <chart:chart>, <chart:series>, first paragraph to --- The chart:class attribute specifies the chart type. The attribute value is a namespacedToken for a chart type. The values for the predefined chart types are: . chart:area [Existing text, but with the different types show as prefixed names} . chart:surface { ... } --- --- Adapt 18.31 config:name second paragraph to --- For <config:config-item-set> elements that are children of <office:settings> elements, the name should start with a namespace prefix followed by a ":". The XML namespace bound to the prefix identifies the implementation that defines the setting having that name. --- Adapt 18.88.3 <db:server-database> to simply say --- The db:type attribute specifies the type of a server-database. --- Adapt 18.149 draw:engine to omit the second sentence. It then reads -- The draw:engine attribue specifies the name of a specific rendering engine that can be used to render a custom shape. The drawing engine may get its data from the draw:data attribute or it may evaluate the <draw:enhanced-geometry> child element instead. --- Adapt 18.262 form:control-implementation to omit the second sentence. It then reads: --- The form:control-implementation attribute specifies a specific concrete rendition or implementation of a control that should be instantiated. --- Adapt 18.431 script:event-name to have the following first paragraph: --- The script:event-name attribute specifies the name of an event. Since the available events, their names and their meanings are application and script language dependent, the name should follow a namespace prefix and separating ":", so that the corresponding namespace together with the name can be used to identify the semantics of the event. --- Adapt 18.583 table:algorithm to --- The table:algorithm attribute names the algorithm used to compare sort keys. To avoid name clashes between different implementations, the algorithm name should follow a namespace prefix and separating ":". The namespace bound to the prefix establishes a unique context in which the name is understood to be local. --- Adapt 18.644 table:formula second paragraph to: --- Formulas specify calculations to be performed within table cells. The attribute value should begin with a namespace prefix followed by ":" followed by the text of the formula. The namespace bound to the prefix determines the syntax and semantics of the formula. --- Adapt 18.807 text:formula second paragraph to --- The attribute value should begin with a namespace prefix followed by ":" followed by the text of the formula. The namespace bound to the prefix determines the syntax and semantics of the formula. --- was: Adapt section 1.4.2.4 clause (D4.4) to --- All table:formula attribute values shall be in the form that begins with a namespace prefix. The prefix shall be bound to the urn:oasis:names:tc:opendocument:xmlns:of:1.2 namespace. --- Adapt 17.3.15 formula to: --- A string containing a formula. Formulas do not have a predefined syntax, but should follow a namespace prefix after a ":" separator. The namespace bound to the prefix determines the syntax and semantics of the formula. --- Adapt 17.3.19 namespacedToken to --- A namespacedToken consists of an XML Namespace QName [xml-names]. The PrefixedName form is interpreted in accordance with the namespace rules for qualified names. The UnprefixedName form is interpreted as a name in the default namespace, if any, defined for the particular use of a namespacedToken type. . --- Adapt 18.15.1 <chart:chart>, <chart:series>, first paragraph to --- The chart:class attribute specifies the chart type. The attribute value is a namespacedToken for a chart type. If there is no prefix in the token, the urn:oasis:names:tc:opendocument:xmlns:chart:1.0 is understood as the default. The names for types in the default namespace are: --- Adapt 18.31 config:name second paragraph to --- For <config:config-item-set> elements that are children of <office:settings> elements, the name should start with a namespace prefix followed by a ":". The XML namespace bound to the prefix identifies the implementation that defines the setting having that name. --- Adapt 18.88.3 <db:server-database> to simply say --- The db:type attribute specifies the type of a server-database. --- Adapt 18.149 draw:engine to omit the second sentence. It then reads -- The draw:engine attribue specifies the name of a specific rendering engine that can be used to render a custom shape. The drawing engine may get its data from the draw:data attribute or it may evaluate the <draw:enhanced-geometry> child element instead. --- Adapt 18.262 form:control-implementation to omit the second sentence. It then reads: --- The form:control-implementation attribute specifies a specific concrete rendition or implementation of a control that should be instantiated. --- Adapt 18.431 script:event-name to have the following first paragraph: --- The script:event-name attribute specifies the name of an event. Since the available events, their names and their meanings are application and script language dependent, the name should follow a namespace prefix and separating ":", so that the corresponding namespace together with the name can be used to identify the semantics of the event. --- Adapt 18.583 table:algorithm to --- The table:algorithm attribute names the algorithm used to compare sort keys. To avoid name clashes between different implementations, the algorithm name should follow a namespace prefix and separating ":". The namespace bound to the prefix establishes a unique context in which the name is understood to be local. --- Adapt 18.644 table:formula second paragraph to: --- Formulas specify calculations to be performed within table cells. The attribute value should begin with a namespace prefix followed by ":" followed by the text of the formula. The namespace bound to the prefix determines the syntax and semantics of the formula. --- Adapt 18.807 text:formula second paragraph to --- The attribute value should begin with a namespace prefix followed by ":" followed by the text of the formula. The namespace bound to the prefix determines the syntax and semantics of the formula. --- Corrected the treatment of namespacedToken to line up with earlier versions of ODF and the research that went into OFFICE-2157. > Public Comment: OpenDocument 1.2v7-02: 1.3 Namespaces > ----------------------------------------------------- > > Key: OFFICE-702 > URL: http://tools.oasis-open.org/issues/browse/OFFICE-702 > Project: OASIS Open Document Format for Office Applications (OpenDocument) TC > Issue Type: Bug > Components: Conformance > Affects Versions: ODF 1.2 > Environment: This proposal applies to ODF 1.2 Part 1. The resolution is stated in terms of the sections in ODF 1.2 Part 1 cd03. > Reporter: Robert Weir > Assignee: Dennis Hamilton > Priority: Blocker > Fix For: ODF 1.2 > > > Copied from office-comment list > Original author: "Dennis E. Hamilton" <dennis.hamilton@acm.org> > Original date: 18 May 2008 06:41:47 -0000 > Original URL: http://lists.oasis-open.org/archives/office-comment/200805/msg00029.html > This issue is taken as applying specifically to the situations where the prefix of a qualified name and an independently used prefix is spoken of as being the namespace name, rather than being bound to the namespace (name) by a namespace declaration. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]