Clearing the air about PCGen Data Files

[soulcatcher]

Speaking purely as a fan, that's something I would like to see as well (the major players working together on a common data reference format). If anything, we should learn from the wrangling going on between corps like Microsoft, Corel, etc. and figure out commonality of data sources, and at least translate between one another. I can open my documents from Word to Wordperfect - why can't I open my files between PCGen and Campaign Suite?

If nothing else, because the systems all do work VERY differently.

For those interested, I ahve posted a first draft of a list of items that I think an interoperable character export should be capable of storing. (note, I think some thigns should be required, and others optional)

Suite Interoperability

Devon Jones
GMGen Regent
PCGen BoD

 

[Fractalwave]

There are two conversations taking place on this thread. Interoperability, and wholesale useage of source data. I have always understood CS's desires to be one of interoperability. My concerns that I have aired here do not relate to interoperability. Not a problem. Bring it on.

There are many benefits of all 4 of us working together. I would like to see that. When do we start?

Devon

There was a third conversation...way up at the first post. It was Chris' post regarding some emails he was receiving. To me, it's important because all those types of emails seem to accomplish is irritate or create a devisiveness that slows our progress towards interoperability. Plus, it gives you finger sprain from hitting the delete key all the time.

To the fans of all the various software:
There's really no reason for those types of messages via email or otherwise. If you get nothing else from this thread, you should know that what we are working on is interoperability. It's a totally different animal from the "abuse" you were assuming.

Okay, I'm off my soapbox. Let's get to work!!

 

[karianna]

Some months ago, I posted on a thread regarding XML datasets for the popular character generator "PCGen". To clear the air about something, what I posted was that an end-user could make an XSL Stylesheet to transform one set of XML to another and use the files interchangibly.

Recently, this was shown to me, and my email box has been getting complaints:

"6.) A way of protecting PCGEN LMC created datasets (our section 15
statement should cover this).
<Paul> YES, but NOT to protect against CMP. Technically right now
ANYONE could swipe the datasets for their pay product (can we say Twin
Rose)"

Hi all,

Sorry I've been caught up on real life lately, so my apologies for not responding to this earlier.

Pauls's comment was made _before_ he knew what Twin Rose was actually trying to do (that is to use the Output Sheets like open RPG does and not the data sets) and therefore should not be taken as his or the BoD's actual viewpoint now (some other members of the BoD also didn't realise).

It was my fault for not removing that from our posted minutes and I humbly apologise for that, I'm sorry Chris.

I have posted back over @ pcgen Y! further comments on the BoD's position in dealing with publishers who want to use PCGen LST files vs using PCGEN's output. I suggest those who are interested, go view the threads over there .

Oh, and thanks for the beer @ Gencon Chris, it was nice to meet you!

Karianna
TM SB
PCGen BoD

 

[smetzger]

I have posted back over @ pcgen Y! further comments on the BoD's position in dealing with publishers who want to use PCGen LST files vs using PCGEN's output. I suggest those who are interested, go view the threads over there .

Could you post a link to that thread? I can't find it.

Thanks,
Scott