DFDL session - Manchester UK OGF meeting - Fw: [gf-chairs] OGF20 Group Session Scheduling is now open
FYI: My hope is that our UK contingent (IBMers, but perhaps including Martin if he happens to be in UK at the time) can do a status update session at this meeting. I would like to use this upcoming meeting in May as a target date for some real and tangible progress on the spec. ...mikeb Mike Beckerle STSM, Architect, Scalable Computing IBM Software Group Information Platforms and Solutions Westborough, MA 01581 voice and FAX 508-599-7148 home/mobile office 508-915-4795 ----- Forwarded by Mike Beckerle/Worcester/IBM on 02/14/2007 09:44 AM ----- Joel Replogle <replogle@ogf.org> Sent by: gf-chairs-bounces@ogf.org 02/12/2007 05:13 PM To gf-chairs@ggf.org cc Subject [gf-chairs] OGF20 Group Session Scheduling is now open OGF Chairs - Group Session Scheduling is now open for the next OGF event, OGF20! OGF20 will be held in the Manchester International Convention Center, Manchester UK from May 7-11, 2007. To request a group session for your WG/RG/CG or a BoF session, please go to the following page for Group Session Requesting instructions and the link to the request form: http://www.ogf.org/OGF20/events_chairinfo.php The scheduling deadlines are: Session Requests: - Deadline for session requests for a CG, WG or RG is 16 March, 2007. - Deadline for AD Hoc/Charter Discussion BOFs is 16 March, 2007. Draft Documents: - Deadline for submitting working drafts is 6 April, 2007. We anticipate that the schedule will be finalized by the end of March. Thanks, Joel ------------------------------------------------------------------------ ----------- Joel Replogle - Manager of Standards, Open Grid Forum replogle@ogf.org http://www.ogf.org -- gf-chairs mailing list gf-chairs@ogf.org http://www.ogf.org/mailman/listinfo/gf-chairs
I had an action item to update the definition of "validation error" to include output direction, and generally to improve it. Here's my proposed language: Validation Errors Logical validation errors are constraints expressed in XSD and they apply to the logical content of the model. DFDL processors may provide both validating and non-validating behaviors on either or both of parse and unparse. A conforming DFDL implementation could validate on parse, but not on unparse. This implies that validation errors cannot affect the ability of a DFDL processor to successfully parse or unparse data. The behavior of a DFDL processor when a validation error occurs is not specified by the DFDL language. An unparse validation error is defined in terms of a parse validation error. Specifically, an unparse validation error occurs when the physical representation being output would generate a validation error on parsing using the same DFDL schema. Unlike parse errors, the DFDL choice construct can not be used to suppress validation errors. The following DFDL schema constructs are checked for validation: DFDL Assertions XSD pattern facet XSD minOccurs, maxOccurs for variable-length data, and for fixed length data when the number of occurrences can be determined from markup in the representation. XSD minLength, maxLength (note: length should be used for fixed length case) XSD minInclusive, minExclusive, maxInclusive, maxExclusive XSD enumeration
participants (1)
-
Mike Beckerle