rthomas320 opened a new issue, #1200:

URL: 
https://usg02.safelinks.protection.office365.us/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fdaffodil-vscode%2Fissues%2F1200&data=05%7C02%7Cregis.thomas%40nteligen.com%7C6122af54751c469c881d08dd621daa4d%7C379c214c5c944e86a6062d047675f02a%7C0%7C0%7C638774601731427526%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=xipr8eeqwRqaumJcwv5dVahiQW4XzfLWSOQqTOtKPfw%3D&reserved=0<https://github.com/apache/daffodil-vscode/issues/1200>



   Looking at appendix G in 
https://usg02.safelinks.protection.office365.us/?url=https%3A%2F%2Fdaffodil.apache.org%2Fdocs%2Fdfd&data=05%7C02%7Cregis.thomas%40nteligen.com%7C6122af54751c469c881d08dd621daa4d%7C379c214c5c944e86a6062d047675f02a%7C0%7C0%7C638774601731440254%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=IFCh5WsqpYLJ%2BrBYB3TURX3CjqwvhVrgYIRVVcJUMsc%3D&reserved=0<https://daffodil.apache.org/docs/dfd>,

   dfdl:element is listed in 2 sections and 4 subsections



   36.1   Parsing

   - 36.1.1    dfdl:element (simple) and dfdl:simpleType

   - 36.1.2    dfdl:element (complex)

   36.2   Unparsing

   - 36.2.1    dfdl:element (simple) and dfdl:simpleType

   - 36.2.2    dfdl:element (complex)



   Should all of the dfdl:attributes listed in these section be presented as 
suggestions for dfdl:element?

   Should the suggestions be narrowed down based on (simple) or (complex)?

       If so, how is simple or complex determined?

           Based on xs:element, xs:simple, or xs:complexType?

   Appendix G separates dfdl:attributes by parsing or unparsing,

   from an intellisense perspective is it correct that the parsing and 
unparsing dfdl attributes would be suggested for the same element?

   Or is there some way to determine an element is defined for parsing or 
unparsing?



   I have similar questions for

   36.1.3    dfdl:sequence and dfdl:group (when reference is to a sequence)

   36.1.4    dfdl:choice and dfdl:group (when reference is to a choice)

   36.2.3    dfdl:sequence and dfdl:group (when reference is a sequence)

   36.2.4    dfdl:choice and dfdl:group (when reference is a choice)



   Is the determination of a reference type based on xs:sequence or xs:choice?

   Should dfdl:sequence, dfdl:choice, and dfdl:group be suggested for xs:group?



   Appendix G deals with parsing and unparsing order, but it seems to imply 
that certain dfdl:attributes should be suggested only if a "higher" level 
attribute is present.  For instance, dfdl:length should only be suggested if 
dfdl:lengthKind =  explicit.  From an intellisense perspective does that mean 
intellisense suggestions should only include dfdl:length after the 
dfdl:lengthKind attribute with a value of explicit is added?

   This would require parsing each attribute and its value in a tag to 
determine which attributes to add to the suggestion list.

   If this were to be implemented would the dfdl:length and dfdl:lengthKind 
attributes be added to the existing list of attribute suggestions?

   Or would dfdl:length and dfdl:lengthUnits as the appear only suggestions 
immediately following the insertion of the dfdl:lengthKind attribute with a 
value of explicit?

   How would intellisense determine when to start suggesting the higher level 
items again?



   Should all dfdl:attributes be suggested for the dfdl:format?



   I have more questions but answers to these will help with the next phase of 
dfdl intellisense development.


Regis Thomas
Nteligen, LLC
6716 Alexander Bell Drive,
Suite 120
Columbia, MD 20146
(240) 864-5042 x126
regis.tho...@nteligen.com

Reply via email to