[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (EBXMLMSG-8) XSD type for ErrorDetail element
[ http://tools.oasis-open.org/issues/browse/EBXMLMSG-8?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=33729#action_33729 ]
Makesh Rao commented on EBXMLMSG-8:
-----------------------------------
Make the XSD consistent to the text.
Change it to xsd:String.
Decided TC meeting June 12, 2013
> XSD type for ErrorDetail element
> --------------------------------
>
> Key: EBXMLMSG-8
> URL: http://tools.oasis-open.org/issues/browse/EBXMLMSG-8
> Project: OASIS ebXML Messaging Services TC
> Issue Type: Improvement
> Components: Core Spec
> Reporter: Sander Fieten
> Priority: Minor
>
> Section 6.2.9 of the core spec explains the usage of the //eb:Error/eb:ErrorDetail element as: "provides additional details about the context in which the error occurred. For example, it may be an exception trace".
> The ebMS XSD defines the type of this as xsd:token. According to the XML Schema specification this means the value of this element must "not contain the carriage return (#xD), line feed (#xA) nor tab (#x9) characters, have no leading or trailing spaces (#x20) and have no internal sequences of two or more spaces" (quoted text taken from XML Schema spec).
> I think the type definition unnecessarily limits the text that can provided and makes it more difficult to provide a useful context of the error.
--
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]