Skip to content
This repository has been archived by the owner on Jan 19, 2018. It is now read-only.

How to define providers and extensions #18

Closed
aweiteka opened this issue Apr 16, 2015 · 3 comments
Closed

How to define providers and extensions #18

aweiteka opened this issue Apr 16, 2015 · 3 comments

Comments

@aweiteka
Copy link
Contributor

How much do we need to define for specific providers and extensions? Are these defined externally to the spec or does it need to be consolidated here?

@tradej
Copy link
Contributor

tradej commented Apr 16, 2015

I believe there should indeed be an easy way to add information for other programs, e. g. in a form of extensions, mentioned in the spec. For example making it a requirement in the spec that parsing mustn't be strict should prevent a lot of problems with extensibility in the future IMO.

Speaking from the point of DevAssistant, we are very open to taking as much metadata from the Atomicfile as possible - this makes the maintenance easier for the upstream developer. However, we would appreciate having the possibility to have some bits of information in the Atomicfile too. A concrete example of what we may need is a freeform field in the Atomicfile where we can link DevAssistant-specific files (those are stored elsewhere in the tree), and maybe add some other information not useful to other consumers of the Atomicfile.

@aweiteka
Copy link
Contributor Author

@tradej is this question satisfied for now? Can we close?

@tradej
Copy link
Contributor

tradej commented May 21, 2015

Yes, the spec allows for additional metadata, so I believe this is okay.

@tradej tradej closed this as completed May 21, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants