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-1875)style:data-style-name, "must match the name of a data style."



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

Patrick Durusau commented on OFFICE-1875:
-----------------------------------------

Perhaps I wasn't clear:

1) We have attributes that reference named styles with no requirement that they "must match" any existing style.

2) The text for this attribute clearly requires that a reference to a named style match an existing style. 

Separate and apart from the issue of what an application may or may not do, or whether we say what an application does or not, my concern is that we are being inconsistent. 

It will cause fewer problems to make fewer requirements so my suggestion is that we simply say for this and other style references, that they match styles of whatever family. Take out the "must" language which implies that the matching style must exist. Simply pass over in silence what happens if the match fails. Yes? 

> style:data-style-name, "must match the name of a data style." 
> --------------------------------------------------------------
>
>                 Key: OFFICE-1875
>                 URL: http://tools.oasis-open.org/issues/browse/OFFICE-1875
>             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
>          Issue Type: Bug
>    Affects Versions: ODF 1.2
>            Reporter: Patrick Durusau
>            Assignee: Patrick Durusau
>
> The value of a style:data-style-name attribute is required to match the name of a data style. 
> We don't say what happens if it doesn't match the name of a data style. 
> Moreover, we don't have a similar "must" condition for other instances of attributes with styleNameRef values. 
> Shouldn't we:
> 1) Make it mandatory that all attribute values of type styleNameRef match a style of the appropriate type, and
> 2) Define what happens if an attribute with a value of type styleNameRef fails to match an existing style of the appropriate type?
> Being mindful that the question of *when* the style must exist is an issue. In other words the creation of the reference may come immediately before the creation of the style. Is that OK? 

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