Skip to content

Conversation

@rakhimov
Copy link
Member

  • Explore more alternative options: XInclude and multiple input files
  • Change the reasoning: portability and convenience
    (the performance gain is left implicit)
  • Clarify what "load" means: context-specific, implicit selective query
  • Clarify the resolution of relative paths
  • Allow easy automatic validation
    (each to-be-included file must be valid by itself against the schema)

Currently, the include directive can appear only
in fault-trees, components, model-data, and opsa-mef.
Therefore, wording is changed from "anywhere" to "specific places".

Closes #16

@cfolleau
Copy link
Member

@rakhimov You are totally right for Xinclude, Xinclude is XML standard, we should simply use it.

For people who don't know what it is: https://www.w3.org/TR/xinclude/#basic-example
I am not for "reinventing the wheel".

@ghost
Copy link

ghost commented Apr 20, 2017 via email

- Explore more alternative options: XInclude and multiple input files
- Change the reasoning: portability and convenience
  (the performance gain is left implicit)
- Clarify what "load" means: context-specific, implicit selective query
- Clarify the resolution of relative paths
- Allow easy automatic validation
  (each to-be-included file must be valid by itself against the schema)

Currently, the include directive can appear only
in fault-trees, components, model-data, and opsa-mef.
Therefore, wording is changed from "anywhere" to "specific places".
@rakhimov
Copy link
Member Author

Closing this in favor of #47

@rakhimov rakhimov closed this Apr 23, 2017
@rakhimov rakhimov deleted the include branch April 23, 2017 08:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants