Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for data source templates #12

Open
mwatts15 opened this issue Feb 21, 2019 · 0 comments
Open

Support for data source templates #12

mwatts15 opened this issue Feb 21, 2019 · 0 comments

Comments

@mwatts15
Copy link
Contributor

Data sources can have user-specific values associated with them like connection details and access date. Some of these values are only resolved at translation-time (i.e., when the data source is being used) and not relevant to reproduction (e.g., user name, local proxy host/port) while others may be useful for reproduction (e.g., access date, run-time computer specifications, time of execution). Such values would simply be a part of the data source, and recorded in the graph, if the source wasn't to be shared, but this sort of shareable value may apply even for resources which are shared. Furthermore, creating a class for each such data sources would create too many classes and, properly done, would require duplicating several attributes such that they apply to a class as well as an instance of a source.

The suggestion of this issue is to create a 'templatedBy' relation which captures this kind of specialization between data sources. This would be used in conjunction with the DataSource:source relation or may be created as a sub-property of that DataSource:source (and thus take its place).

  • There is already logic for 'capabilities' which resolve user-specific values at translation-time for data sources. This should be utilized and/or expanded to fill in shareable translation-time values as well, although the data sources themselves would retain the logic for filling the template values in where they belong.
  • The OWM.translate method would need to know which sources are templates in order to create a new non-templated version for translation purposes.
  • Data sources would need to have some kind of template/non-template marker--probably a sub-class of DataSource is best.
  • The fact that a data source is a template should be accessible in the graph
@mwatts15 mwatts15 changed the title Create support for data source templates Support for data source templates Feb 21, 2019
@mwatts15 mwatts15 transferred this issue from openworm/owmeta Feb 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant