[DFDL-WG] DFDL: Action 027 - rework of property precedence - plusissues arising

Mike Beckerle mbeckerle.dfdl at gmail.com
Tue May 19 18:03:45 CDT 2009


My markup on this attached - mostly using comment balloons on the side.
 
 
 

Mike Beckerle | OGF DFDL WG Co-Chair | CTO | Oco, Inc.
Tel:  781-810-2125  | 100 Fifth Ave., 4th Floor, Waltham MA 02451 |
<mailto:mbeckerle.dfdl at gmail.com> mbeckerle.dfdl at gmail.com 

 

  _____  

From: dfdl-wg-bounces at ogf.org [mailto:dfdl-wg-bounces at ogf.org] On Behalf Of
Steve Hanson
Sent: Friday, May 08, 2009 12:23 PM
To: dfdl-wg at ogf.org
Subject: [DFDL-WG] DFDL: Action 027 - rework of property precedence -
plusissues arising



I've created a separate property precedence for each schema object that can
carry non-scoping DFDL properties (attached for review). 


The following issues were noted: 

1) Missing property dfdl:textBooleanJustification - similar properties exist
for string, number and calendar types. 

2) What is the rule when the same DFDL properties occur on a xs:simpleType
and a xs:element that uses that type?  Does this work a) like element/group
references (ie, properties combined with element winning) or b) like complex
element and its sequence (ie, element and simpleType are considered separate
objects)? I don't think section 10 covers this case. 

3) Should we allow the DFDL nil & default control properties on a simple
type?  xs:nillable and xs:default are element only attributes in xsd. Spec
currently allows this. 

4) Should we allow DFDL occurs properties on global elements?  Whether
something repeats is a particle thing. Spec currently allows this. (IBM's
WTX and MRM don't allow this). 

5) Missing work item to get BiDi properties into shape and incorporated into
spec. Should these be grouped, like escape scheme, calendar scheme, etc? Do
they apply to calendar and number types? 

6) Should dfdl:integerBooleanXXXRep be renamed dfdl:binaryBooleanXXXRep ? 

7) We might want to reconsider the name of the new flag dfdl:initiated - it
could be read that the xs:sequence itself is initiated rather than its
children.   

8) Should dfdl:initiated also apply to xs:choice? 

9) Draft 33 property precedence had dfdl:outputLengthCalc - but that is not
in the spec anywhere else? 

Regards

Steve Hanson
Programming Model Architect
WebSphere Message Brokers
Hursley, UK
Internet: smh at uk.ibm.com
Phone (+44)/(0) 1962-815848



  _____  





Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number
741598. 
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU 









-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.ogf.org/pipermail/dfdl-wg/attachments/20090519/4aad9705/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Property Precedence 034-mikeb.doc
Type: application/msword
Size: 179200 bytes
Desc: not available
Url : http://www.ogf.org/pipermail/dfdl-wg/attachments/20090519/4aad9705/attachment-0001.doc 


More information about the dfdl-wg mailing list