The ORM Foundation

Hello all, here's my scenario: I have a bunch of ORM models stashed in a private Github repository, and I need a tool that grabs them, turns them into .jpg files (or some other image file format), and downloads them onto my computer. Can ORM Solutions' ORM viewer be configured to access non-public repositories?

Many thanks! 

 Have you tried to use NORMA to solve your problem?

Ken 

Ken Evans:

Have you tried to use NORMA to solve your problem?

Thanks, I need something web-API-based, hence something that does not require my downloading the files locally, opening them up in Visual Studio etc. People who do not have Visual Studio installed should be able to point their browsers to my Github, and download the JPEGs (or whatever).

Hmm, an interesting approach.

The purpose of .orm files is to help people to store and to re-use editable information models. 

So I'm curious to understand the problem that can be solved with un-editable .jpeg files?

It seems to me that generating .jpeg files from orm files removes 99% of their usefulness and value (if not more.)

Happy to have my ignorance corrected.

People I build these diagrams for need to see the ... diagrams . They have no knowledge of ORM, but just want to see how things tie together in a graphical fashion.

 Thanks for the clarification.

You should be aware of several things:
1: ORM diagrams are really "First Order Logic In Pictures".

2: ORM diagrams hide a lot of detail because they are intended for use by modelers rather than as an explanation.

Please refer to the next post that has a seemingly simple binary fact type.

I don't see how someone who does not understand ORM can infer the verbalisation from the diagram. 

Richard Feynman was talking about this kind of problem when he said:  " Don’t let yourself be fooled by others and don’t fool yourself. You can avoid being fooled by knowing how to separate truth from the appearance of truth."

Feynman, R. (1992). Surely You're Joking Mr Feynman (First Vintage Edition ed.): Vintage.

Refer to the fact type diagram at the bottom of this post.

  This is what it means:

PersonNr is an entity type.
Reference Scheme: PersonNr has PersonNr_nr.
Reference Mode: .nr.
Data Type: Numeric: Signed Integer.

Fact Types:
PersonNr has PersonNr_nr.
PersonNr has BankAccountNr.

BankAccountNr is an entity type.
Reference Scheme: BankAccountNr has BankAccountNr_nr.
Reference Mode: .nr.
Data Type: Numeric: Signed Integer.

Fact Types:
BankAccountNr has BankAccountNr_nr.
PersonNr has BankAccountNr.

PersonNr has BankAccountNr.
It is possible that some PersonNr has more than one BankAccountNr
and that for some BankAccountNr, more than one PersonNr has that BankAccountNr.
In each population of PersonNr has BankAccountNr, each PersonNr, BankAccountNr combination occurs at most once.
This association with PersonNr, BankAccountNr provides the preferred identification scheme for PersonNrHasBankAccountNr.
For each BankAccountNr, some PersonNr has that BankAccountNr.
Each BankAccountNr in the population of "PersonNr has BankAccountNr" occurs there at most 2 times.

Each BankAccountNr in the population of "PersonNr has BankAccountNr" occurs there at most 2 times.