The way you communicated was confusing, at least to someone who already knew what you were trying to say, because you used the wrong words. I'm sorry, but jargon matters. If you don't know the correct words, then you can't discuss the concepts without appearing really confused.

You keep telling me I'm using the wrong words when I'm not. I know jargon matters, but it's alright because I used the correct jargon or nearly correct jargon within reason. You're getting confused because apparently you don't understand their meaning in this context.

I'm not crazy, google it:

http://www.google.com/ search?hl=en&safe=off&rlz=1B2GGGL_enUS202US202&q=C%23+%2B+in terfaces+%2B+contract&btnG=Search
http://www.google.com/ search?hl=en&safe=off&rlz=1B2GGGL_enUS202US202&q=XML+%2B+sch ema+%2B+contract&btnG=Search

They are both commonly called contracts and they have the same functions.

When I called interfaces schemas I was only trying to reach a broader audience anyways. I didn't think anybody would know what an interface was unless they knew C#, but lots of people know XML.
Page: 1 2