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

Change "Adapter" terminology #6

Open
jfexyz opened this issue Mar 18, 2015 · 3 comments
Open

Change "Adapter" terminology #6

jfexyz opened this issue Mar 18, 2015 · 3 comments
Assignees

Comments

@jfexyz
Copy link
Contributor

jfexyz commented Mar 18, 2015

We should just be more clear here, as adapter is too vague a word.

@jfexyz
Copy link
Contributor Author

jfexyz commented Mar 18, 2015

Here are the components (and my preferred terminology):

  • Specification: Specification or Spec (or do we needs terms for the spec document itself, and the Translator?)
  • Routes: Router or Engine
  • ORM: Mapper or DataStore or Storage
  • Output Format: Serializer or Transformer (or both?)

@jfexyz jfexyz changed the title Change "Adapter" to "Specification" or "Spec" Change "Adapter" terminology Mar 18, 2015
@jfexyz
Copy link
Contributor Author

jfexyz commented Mar 18, 2015

Or maybe we get all cheeky and use water-transportation-specific terms?

@desmondmorris
Copy link
Member

I think the class instance representation of a spec doc should be the Specification. The actual document should maybe be named source? Router - definitely and I like Storage. I do not have an opinion on the output format stuff yet

The water inspired theme would be fun too -- that may take a bit of research

@desmondmorris desmondmorris self-assigned this Mar 19, 2015
desmondmorris added a commit to desmondmorris/ferry that referenced this issue Mar 19, 2015
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

2 participants