[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Issue Comment Edited: (OFFICE-702) PublicComment: 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=16278#action_16278 ]
Michael Brauer edited comment on OFFICE-702 at 10/13/09 10:11 AM:
------------------------------------------------------------------
Suggestions regarding #2:
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 Dublin Core namespace*.
----
Adapt 17.3.15 formula to:
---
A string containing a formula. Formulas do not have a predefined syntax, but should start with a namespace prefix. *The XML namespace name associated with the namespace prefix* specifies the syntax *and semantics of* the formula.
----
Adapt 17.3.19 namespacedToken to:
----
A namespaced token is a token id that makes use of the XML namespace mechanism for modularization purposes. *It consists of a namespace prefix and a local name. The local name is considered to be a name in the XML namespace associated with the namespace prefix.*
----
Adapt 18.31 config:name to:
---
For <config:config-item-set> elements that are children of <office:settings> elements, the name should be preceded by a namespace prefix. *The XML namespace associated with the namepsace prefix* identifies the implementation that has stored the setting.
---
Delete the 2nd sentence from 18.88.3 [db:type] <db:server-database>. 18.88.2 reads then:
----
The db:type attribute specifies the type of a server-database.
----
Delete the 2nd sentence from 18.149 draw:engine. 18.149 reads then:
----
The draw:engine attribute specifies the name of a specific rendering engine that can be used to render a custom shape.
----
Delete the 2nd sentence from 18.261 form:control-implementation. 18.261 reads then:
----
The form:control-implementation attribute specifies a specific concrete rendition or implementation of a control that should be instantiated.
----
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 be preceded by a namespace prefix. If a namespace prefix is present, the local name of the attribute value is considered to be a name in the XML namespace associated with the namespace prefix.*
----
was (Author: michael.brauer):
Suggestions regarding #2:
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 Dublin Core namespace*.
----
Adapt 17.3.15 formula to:
---
A string containing a formula. Formulas do not have a predefined syntax, but should start with a namespace prefix. *The XML namespace name associated with the namespace prefix* specifies the syntax *of* the formula.
----
Adapt 17.3.19 namespacedToken to:
----
A namespaced token is a token id that makes use of the XML namespace mechanism for modularization purposes. *It consists of a namespace prefix and a local name. The local name is considered to be a name in the XML namespace associated with the namespace prefix.*
----
Adapt 18.31 config:name to:
---
For <config:config-item-set> elements that are children of <office:settings> elements, the name should be preceded by a namespace prefix. *The XML namespace associated with the namepsace prefix* identifies the implementation that has stored the setting.
---
Delete the 2nd sentence from 18.88.3 [db:type] <db:server-database>. 18.88.2 reads then:
----
The db:type attribute specifies the type of a server-database.
----
Delete the 2nd sentence from 18.149 draw:engine. 18.149 reads then:
----
The draw:engine attribute specifies the name of a specific rendering engine that can be used to render a custom shape.
----
Delete the 2nd sentence from 18.261 form:control-implementation. 18.261 reads then:
----
The form:control-implementation attribute specifies a specific concrete rendition or implementation of a control that should be instantiated.
----
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 be preceded by a namespace prefix. If a namespace prefix is present, the local name of the attribute value is considered to be a name in the XML namespace associated with the namespace prefix.*
----
> 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
> 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 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]