[ http://tools.oasis-open.org/issues/browse/OFFICE-3411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=21948#action_21948 ]
Dennis Hamilton commented on OFFICE-3411:
-----------------------------------------
So why don't you just use the XML Schema datatype "integer" and let it go at that, with anything else dealt with as part of the implementation-dependency?
> 19.32 config:type: dubious references to SQL specifcation
> ---------------------------------------------------------
>
> Key: OFFICE-3411
> URL: http://tools.oasis-open.org/issues/browse/OFFICE-3411
> Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
> Issue Type: Bug
> Components: Public Review
> Affects Versions: ODF 1.2 Part 1 CD 5, ODF 1.2 CD 05
> Environment: OpenDocument-v1.2-cd05-part1.odt
> Reporter: Michael Stahl
> Assignee: Andreas Guelzow
> Priority: Minor
> Fix For: ODF 1.2 CD 06
>
>
> <quote>
> The config:type attribute specifies a data type for a setting.
> The defined values for the config:type attribute are:
> base64Binary: 18.2
> boolean: 18.3.2
> datetime: 18.2
> double: 18.2
> int: 18.2
> long: defined by [SQL].
> short: defined by [SQL].
> string: 18.2
> </quote>
> most of the values here refer to types from the XMLSchema-2 specification, but surprisingly, 2 of then ("short", "long") refer to the SQL specification.
> i'm guessing this is probably wrong.
> XMLSchema-2 also specifies "short" and "long" types, so why not use those.
> furthermore, the type "int" refers to 18.2, but it is not actually listed in 18.2.
> (in ODF 1.1 the values were not described at all.)
--
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
