We have a restriction in Daffodil that doesn't allow lengthKind pattern for hexBinary, but I recently reviewed the spec and can find no such restriction. Did I miss the restriction somewhere else? I find no occurrences of 'pattern' nor 'hexbinary' in the current errata document. I would say it is inconsistent to disallow lengthKind pattern for hexBinary, after all, we allow lengthKind 'delimited' which scans the binary bits/bytes, and that means dfdl:encoding is needed for hexBinary when lengthKind is 'delimited', so we're already allowing the other things we would need to support lengthKind 'pattern' also. We do have a workaround which is to use a string with encoding iso-8859-1, but that just proves the point that really there is no reason why hexBinary doesn't allow this. Mike Beckerle | OGF DFDL Workgroup Co-Chair | Tresys Technology | www.tresys.com Please note: Contributions to the DFDL Workgroup's email discussions are subject to the OGF Intellectual Property Policy <http://www.ogf.org/About/abt_policies.php>