OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

office message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [OASIS Issue Tracker] Commented: (OFFICE-1739) Editor Note: Section17.489 style:leader-text



    [ http://tools.oasis-open.org/issues/browse/OFFICE-1739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13186#action_13186 ] 

Michael Brauer commented on OFFICE-1739:
----------------------------------------

First of all, I noticed that we have a "character" datatype already since ODF 1.0. It therefore doesn't have to be added.

Regarding the character datatype/COMPATIBILITY WARNING:

Relax-NG is usually used with the XSD datatype library, and so does ODF. The datatypes that are then available are those defined by XSD, or specializations of them. The XML specification may provide a definition called "Char" as well, but that's not an XSD datatype, and therefore not usable in the context of an XML attribute value definition in Relax-NG.

Regarding the "INTEROPERABILITY CONCERN": 

We may add a list of characters that an application should support, but we haven't had this in previous version, and no one had requested this so far. I therefore would defer that to ODF-Next (or a discussion whether we should add a list, to be precise).

I'm fine with the currently proposed wording. I think it is clear. But of cause, there is always the possibility to phrase things better  or just differently. I therefore would like to leave it up to Patrick to find a wording that matches in the style in which the  specification is written. That also holds for the proposal under CLARIFICATION.



> Editor Note: Section 17.489 style:leader-text
> ---------------------------------------------
>
>                 Key: OFFICE-1739
>                 URL: http://tools.oasis-open.org/issues/browse/OFFICE-1739
>             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
>          Issue Type: Bug
>    Affects Versions: ODF 1.2
>            Reporter: Robert Weir 
>            Assignee: Patrick Durusau
>            Priority: Blocker
>             Fix For: ODF 1.2
>
>
> Transcribed from ODF_Revised_Editorial_Notes_27May2009.odt
> Original author: Patrick Durusau
> Section 17.489 style:leader-text
> Ed. Note The schema does not enforce the single Unicode character restriction. I have re-cast this text as it seemed deeply confusing to me. How an application could not support "textual" and still use any of the line leaders, which are also Unicode characters is beyond me. I suspect we need to change the substantive requirements of this attribute to simply use the specified text leader if specified and the line leader if not. 
> Oliver says: "Yes, the schema should reflect the restriction - Michael, changing its 
> data type to character? 
> No further input from my side, because I am also a little bit confused. "

-- 
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]