[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (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:comment-tabpanel&focusedCommentId=16458#action_16458 ]
Michael Brauer commented on OFFICE-702:
---------------------------------------
ere is what I suggest, based on the resolutions in the resolution field. The changes are minor, and I have added notes what I did change. I have also added proposals for the attributes that were covered by comments, but were not included in the proposal.
Adapt section 1.4.2.4 clause (D4.4) to
---
All *namespace prefixes used in the values of* table:formula *attributes* shall be bound to the urn:oasis:names:tc:opendocument:xmlns:of:1.2 namespace.
---
Note: In CD03-Rev03 the default namespace is OpenFormula. Therefore, it is not reasonable to request that a namespace prefix is present.
In 2.2.1 [Non-RDF Metadata] General, adapt the 3rd paragraph to:
----
The pre-defined metadata elements borrow heavily upon the metadata standards developed by the Dublin Core Metadata Initiative (http://www.dublincore.org). Metadata elements drawn directly from the Dublin Core *are in the http://purl.org/dc/elements/1.1/ namespace*.
----
Note: If "Dublin Core namespace" is ambiguous, we still can mention the namespace we are using here.
Adapt 17.3.15 formula to:
---
A string containing a formula. Formulas do not have a predefined syntax, but *the string* should *begin with* a namespace prefix, *followed by* a ":" (COLON, U+003A) separator, *followed by the text of the formula*. The namespace bound to the prefix determines the syntax and semantics of the formula.
---
Note: I've only change the wording slightly to match similar definition we have, and added Unicode conventions.
Note: 17.3.19 will be covered by OFFICE-2157 now.
Adapt 18.15.1 <chart:chart>, <chart:series>, first paragraph to
---
The chart:class attribute specifies the chart type. The attribute value is a *namespaced token* 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
{ ... }
---
Note: Same text as proposed, except that I have replaced "namespacedToken" with "namespaced token", since "namespacedToken" is not a valid English word.
Adapt 18.31 config:name second paragraph to
---
For <config:config-item-set> elements that are children of <office:settings> elements, the name should *begin* with a namespace prefix followed by a ":" *(COLON, U+003A)*. The XML namespace bound to the prefix identifies the implementation that defines the setting having that name.
---
Note: I've one added the Unicode code point, and replaced "start" with" begin", since this is what we use elsewhere.
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 of the first paragraph. It then reads
--
The draw:engine attribue specifies the name of a specific rendering engine that can be used to render a custom shape.
---
Note: In CD03 Rev03, the 2nd sentence of the proposal have been removed. No other change
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 *begin with* a namespace prefix* followed by a ":" (COLON, U+003A) separator*, so that the corresponding namespace together with the name can be used to identify the semantics of the event.
---
Note: adapted the language to that of 17.3.15.
Adapt 18.433 script:language to
----
The attribute script:language specifies the name of a script. Script language names are implementation specific. *The names identifying script languages should begin with by a namespace prefix, followed by a ":" (COLON, U+003A) separator*. If a namespace prefix is present, the local name of the attribute value is considered to be a name in the XML namespace bound to the namespace prefix.*
----
Note: This attribute was missing in the proposal.
Add to the last but one paragraph of 18.471 style:condition:
---
The XML namespace name associated with the namespace prefix specifies the syntax and semantics of the formulas and values occurring within the condition.
---
Note: This attribute was missing in the proposal.
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 *begin with* a namespace prefix, followed by a ":" (COLON, U+003A) separator.*. The namespace bound to the prefix establishes a unique context in which the name is understood to be local.
---
Note: Same minor adaptations to the language as for other attributes.
Adapt 18.599 table:condition to
----
The table:condition attribute specifies the condition that determines whether a cell content is valid in regard to a validation rule or not. A cell content is valid if the condition evaluates to "true". The value of this attribute should be a namespace prefix*, followed by a ":" (COLON, U+003A),* followed by Boolean expression. If the namespace prefix is missing it defaults to the "urn:oasis:names:tc:opendocument:xmlns:of:1.2" namespace. *The XML namespace name bound to the namespace prefix specifies the syntax and semantics of the formulas and values occurring within the condition.*
----
Note: This attribute was missing in the proposal.
Adapt last paragraph of 18.638 to:
---
The value of this attribute may have a namespace prefix, *followed by a ":" (COLON, U+003A), *followed by the expression. If the namespace prefix is missing it defaults to the "urn:oasis:names:tc:opendocument:xmlns:of:1.2" namespace. If a namespace prefix is present, the expression shall start with an '=' equal sign. If no namespace prefix is present, the '=' equal sign may be omitted. *The XML namespace name bound to the namespace prefix specifies the syntax and semantics of the formulas and values occurring within the condition.*
---
Note: This attribute was missing in the proposal.
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 ":" *(COLON, U+003A)*, followed by the text of the formula. The namespace bound to the prefix determines the syntax and semantics of the formula.
---
Note: Added Unicode character code.
Adapt 18.807 text:formula second paragraph to
---
The attribute value should begin with a namespace prefix followed by ":"*(COLON, U+003A)* followed by the text of the formula. The namespace bound to the prefix determines the syntax and semantics of the formula.
---
Note: Added Unicode character code.
> 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]