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] Created: (OFFICE-3374) ODF 1.2-1 9.4.8<table:error-macro> contradictory and not implementable

ODF 1.2-1 9.4.8 <table:error-macro> contradictory and not implementable

                 Key: OFFICE-3374
                 URL: http://tools.oasis-open.org/issues/browse/OFFICE-3374
             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
          Issue Type: Bug
          Components: Part 1 (Schema), Table
    Affects Versions: ODF 1.2 CD 05
            Reporter: Dennis Hamilton
            Priority: Critical
             Fix For: ODF 1.2 CD 06

The description for 9.4.8 contradicts the schema and the possibilities of the <office:event-listeners> element.

The contradictory text and unimplementable cases start with this text in 9.4.8:

"The <table:error-macro> element specifies if a macro should be executed upon an attempt to enter invalid content.

Such a macro is specified by an <office:event-listeners> element. 14.4 The event name shall be one that specifies an event that is called on invalid user input.

Problem 1: The presence of a <table:error-macro> element in a <table:content-validation> element prevents the presence of a <table:error-message> element according to the current schema.  There is therefore no means to determine whether a validation failure is merely informational or a warning.

Problem 2: However, the <table:error-macro> table:execute attribute can specify that the macro is not to be executed.  In this case, it appears that validation can silently fail.

Problem 3: According to the schema for <table:content-validation>, it is optional for an <office:event-listeners> element to accompany the <table:error-macro> element.  This appears to contradict the *shall* provision and the need to specify an appropriate macro.

Problem 4: It would appear that the only meaningful case of <office:event-listeners> is with one or more (optional) <script:event-listener> elements.
Problem 5: There is no defined script:event-name defined in the schema, in section 19.431, or in [DOMEvents2] establisehd for "invalid user input" (see above), so there is no specified way for the *shall* to be honored.

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]