pezagent
First Post
Hi gang,
Please excuse the title of this thread--the shameless plug if you will.
No doubt any serious, or even not so serious, roleplayer often toys with the "what if I could..." scenario of combining gaming systems. And perhaps these thoughts aren't even limited to d20 gaming systems, but all gaming systems.
Impossible?
Some may say yes, I say no.
RPGenesis is my first application module for a very "secret" project I'm working on right now. I'm very excited about it. Unfortunately, to get this program to work, I have to rely on a lot of people to understand some very fundamental concepts concerning data exchange between applications. Otherwise I've got a lot of work ahead of me.
Just as I have no doubts people are curious, or perhaps even excited about the possibilities of combining gaming systems, there needs to be a transition from idle curiosity to initiative. What I mean is, I think a lot of people are excited about the idea, take the preliminary steps to extinguish the curiosity flame, and then lose interest when the novelty wears off.
Without a defined project to adhere to and keep goals in focus, the scope of data exchange between d20 systems becomes overbearing, impossible, pointless--and better left to somebody else to figure out. Or worse--left to those with far too much time on their hands, and trivial matters become mountains of endless, pointless debate.
My passion for this concept has led me to do a great deal of research for my application needs. I have discovered over time that my needs are very similar to the needs of everyone else working on similar applications. So why has it been so difficult to produce source data or arrive at a solution towards data exchange?
1. Lack of Leadership. A project needs a team and a team needs a leader. I'm sorry that everyone can't be a leader, but sometimes it's just as important to be part of a team. A leader has a lot of responsibility. And the team is responsible to use their individual strengths to complete the tasks at hand. But leadership just doesn't "happen." Anyone who believes a good idea on it's own should merit leadership and attract followers should read Selling The Wheel. It's a great story(and reference) about how hard it is to sell an idea even if it's the best idea in the world. Lesson: Just about the time you're so sick of your idea you could care less is when people start listening. A leader is someone who follows a process through to completion when all others have lost hope. A leader is not someone who defends what hasn't been done in hopes that others will follow and pick up where s/he left off.
2. Goals too Vague. When I see people approaching a "solution" for data exchange, they're not really looking at the real "problem." They might be looking at potential problems--but this is a sure sign of ambiguity. There's too much "what if" going on. "What if somebody decides to do this? We need to implement this then!" is a common argument when people are shooting for the moon when they need to be focused on the sand beneath their feet. A lot of progress can be made taking baby steps. For example, rather than saying one wants to create an XML character sheet, ask "why?" If an answer can't be given instantly--and specifically (I want to import character data from PCGen into Campaign Suite), the idea hasn't been thought through far enough. The result: endless debates about which direction to take because nobody knows where to go. The solution: Be specific about your goals. Take baby steps and follow the process, not the outcome.
3. Lack of Intimate Knowledge. This is my biggest pet peeve. Everybody is a teacher, nobody wants to do be a student and do their homework. The tools for data exchange are on the table, but nobody is examining them, using them. The result: using the same tool (XML) to do the work of all of tools (XSL/T, XSD), without understanding how to use them in harmony. Or, using old tools (DTD) that aren't designed for the task at hand. The solution: Look for the solution within what you don't know, not what you do know. Ask others for help.
4. Authority Complexes. I don't care if you're a "professional software designer." I don't care if you've discussed the same subject for the last ten years. This doesn't make you a leader, nor does it turn fallacy into fact--or give one the right to act irresponsibly and decieve with personal opinions disguised as facts. If progress is to be made, then we must put our trust in the facts and the technology. And we must be able to trust project leaders to know and share the facts--and admit when they don't have them--so the facts can be obtained. In the age of hypertext, it always amazes me how people still have trouble verifying facts. The solution: Lead by example, not by status. Become trustworthy by getting the facts straight.
I believe these are the main roadblocks to progress in the world of data exchange projects, and that's why I started the d20-dataExchange. The concept of the group is simple--it's not an organization, it's an incubator. To keep discussions focused, participants/members are encouraged to start projects or join other projects that will solve specific problems facing the data exchange world. These small projects will, of course, lead to bigger ones, and eventually, the world of data exchange will become a very manageable place. But right now, it's still the Wild-Wild West. (Without the giant mechanical tarantulas, of course.)
So, if there's anyone out there seriously finding themselves at the point they need to take the concepts of data exchange beyond theory and into practice, feel free to join d20-dataExchange. Your participation is most welcome.
Regards,
/johnny
Please excuse the title of this thread--the shameless plug if you will.
No doubt any serious, or even not so serious, roleplayer often toys with the "what if I could..." scenario of combining gaming systems. And perhaps these thoughts aren't even limited to d20 gaming systems, but all gaming systems.
Impossible?
Some may say yes, I say no.
RPGenesis is my first application module for a very "secret" project I'm working on right now. I'm very excited about it. Unfortunately, to get this program to work, I have to rely on a lot of people to understand some very fundamental concepts concerning data exchange between applications. Otherwise I've got a lot of work ahead of me.
Just as I have no doubts people are curious, or perhaps even excited about the possibilities of combining gaming systems, there needs to be a transition from idle curiosity to initiative. What I mean is, I think a lot of people are excited about the idea, take the preliminary steps to extinguish the curiosity flame, and then lose interest when the novelty wears off.
Without a defined project to adhere to and keep goals in focus, the scope of data exchange between d20 systems becomes overbearing, impossible, pointless--and better left to somebody else to figure out. Or worse--left to those with far too much time on their hands, and trivial matters become mountains of endless, pointless debate.
My passion for this concept has led me to do a great deal of research for my application needs. I have discovered over time that my needs are very similar to the needs of everyone else working on similar applications. So why has it been so difficult to produce source data or arrive at a solution towards data exchange?
1. Lack of Leadership. A project needs a team and a team needs a leader. I'm sorry that everyone can't be a leader, but sometimes it's just as important to be part of a team. A leader has a lot of responsibility. And the team is responsible to use their individual strengths to complete the tasks at hand. But leadership just doesn't "happen." Anyone who believes a good idea on it's own should merit leadership and attract followers should read Selling The Wheel. It's a great story(and reference) about how hard it is to sell an idea even if it's the best idea in the world. Lesson: Just about the time you're so sick of your idea you could care less is when people start listening. A leader is someone who follows a process through to completion when all others have lost hope. A leader is not someone who defends what hasn't been done in hopes that others will follow and pick up where s/he left off.
2. Goals too Vague. When I see people approaching a "solution" for data exchange, they're not really looking at the real "problem." They might be looking at potential problems--but this is a sure sign of ambiguity. There's too much "what if" going on. "What if somebody decides to do this? We need to implement this then!" is a common argument when people are shooting for the moon when they need to be focused on the sand beneath their feet. A lot of progress can be made taking baby steps. For example, rather than saying one wants to create an XML character sheet, ask "why?" If an answer can't be given instantly--and specifically (I want to import character data from PCGen into Campaign Suite), the idea hasn't been thought through far enough. The result: endless debates about which direction to take because nobody knows where to go. The solution: Be specific about your goals. Take baby steps and follow the process, not the outcome.
3. Lack of Intimate Knowledge. This is my biggest pet peeve. Everybody is a teacher, nobody wants to do be a student and do their homework. The tools for data exchange are on the table, but nobody is examining them, using them. The result: using the same tool (XML) to do the work of all of tools (XSL/T, XSD), without understanding how to use them in harmony. Or, using old tools (DTD) that aren't designed for the task at hand. The solution: Look for the solution within what you don't know, not what you do know. Ask others for help.
4. Authority Complexes. I don't care if you're a "professional software designer." I don't care if you've discussed the same subject for the last ten years. This doesn't make you a leader, nor does it turn fallacy into fact--or give one the right to act irresponsibly and decieve with personal opinions disguised as facts. If progress is to be made, then we must put our trust in the facts and the technology. And we must be able to trust project leaders to know and share the facts--and admit when they don't have them--so the facts can be obtained. In the age of hypertext, it always amazes me how people still have trouble verifying facts. The solution: Lead by example, not by status. Become trustworthy by getting the facts straight.
I believe these are the main roadblocks to progress in the world of data exchange projects, and that's why I started the d20-dataExchange. The concept of the group is simple--it's not an organization, it's an incubator. To keep discussions focused, participants/members are encouraged to start projects or join other projects that will solve specific problems facing the data exchange world. These small projects will, of course, lead to bigger ones, and eventually, the world of data exchange will become a very manageable place. But right now, it's still the Wild-Wild West. (Without the giant mechanical tarantulas, of course.)
So, if there's anyone out there seriously finding themselves at the point they need to take the concepts of data exchange beyond theory and into practice, feel free to join d20-dataExchange. Your participation is most welcome.
Regards,
/johnny
Last edited:
