Do you agree that:
No constraints SHOULD be placed on the xsd: string. These constraints SHOULD be handled by an implementation detail, and if found to err, raise an error.
The technical specification SHOULD provide a warning or implementor's hint about this possible condition. If appropriate, this hint SHOULD be referenced in descriptive text in the technical specification and any well-formedness rules referenced that may assist in ease of development.
References:
Martin, boundaries for v2.0 scope, 24 February: http://www.oasis-open.org/archives/ebxml-bp/200402/msg00250.html
Martin, informal F2F agenda and summary, http://www.oasis-open.org/archives/ebxml-bp/200404/msg00053.html
Martin, Summary: http://www.oasis-open.org/archives/ebxml-bp/200403/msg00096.html
Webber, suggestion, 29 March: http://www.oasis-open.org/archives/ebxml-bp/200403/msg00108.html |
