You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have found that using a general reference type to refer to any type of (document-level) object makes the design of libraries to implement the specification more complex as it is often required to open up references as they are added and check what type they are. Therefore I think it would be simpler if there was a specific reference type for each element that can be referred to i.e.:
This would also make the serialised files more easy to visually parse, especially for elements such as the Network class where populations and projections are mixed in together, and would simplify the specification where they appear (and allow it to be represented in XML schema).
The text was updated successfully, but these errors were encountered:
I have found that using a general reference type to refer to any type of (document-level) object makes the design of libraries to implement the specification more complex as it is often required to open up references as they are added and check what type they are. Therefore I think it would be simpler if there was a specific reference type for each element that can be referred to i.e.:
and if #109 is accepted
This would also make the serialised files more easy to visually parse, especially for elements such as the
Network
class where populations and projections are mixed in together, and would simplify the specification where they appear (and allow it to be represented in XML schema).The text was updated successfully, but these errors were encountered: