Community Use Policy vs. Open Gaming License.
The rules content needs to be OGL to be used in the databases. The CUP affects how the names appear. PathfinderCommunity.net appears to be affiliated with d20pfsrd, which lost the rights to use the CUP when it became a commercial site. The rules content remains OGL regardless, but the use of Golarion-specific names in rules elements (such as named of countries, organizations, or NPCs, etc. in the names and requirements of Feats, Traits, Prestige Classes, etc.) is allowed under the CUP but not under OGL. So d20pfsrd has to re-name content that uses the protected names, and drop requirements that use the protected names. This leads to occasional frustration for HeroLab users relying on d20pfsrd... they don't realize that the names were altered, and so can't find the d20pfsrd names in HeroLab (because they are present under their 'proper' names). I don't know which names are in the pathfindercommunity.net files. |
Quote:
|
Quote:
Just because Paizo does not put it in the PRD does not mean it is Protected content. However, the restrictions on using the names may be an issue that forces renaming some items. The Community Use Policy allows the use of Protected content (such as names, but also art) within limits and according to the terms of the policy. The wrinkle here may be the requirement that any distribution of the OGL content requires that a human-readable copy of the OGL itself with its "Section 15" (copyright listing) be included with the distribution. That's more likely to be an issue than the actual content. I certainly agree that separation by source for those who do not want to include world-specific content is advisable. |
Look at it this way, it isn't going to be feasible for most people to import all that stuff to anything other than a Golarian realm and even then I think they're going to have to pick and choose. 5 GB of mechanics data? That's a lot of overhead for very little gain.
|
I'm withholding comments pending Rob's reply.
|
Quote:
Exporting and importing something between 20% and 33% (at most, probably much closer to the 20% figure) of my 1.3 GB data caused the file to grow from 1.3 GB to 7.5 GB, Prior to "shrinking" the db down to 1.3 GB, it had been as large as 16.8 GB ... and of that, 15.3 GB was empty/wasted space, probably from other export/import testing. That 15.3 GB was "recovered" by deleting my local MASTER.realm and re-syncing the data from the cloud to local. |
Quote:
|
What's another 5gb?
|
Quote:
As you've already begun to tease apart, there are a bunch of complicating factors involved with this project and how you're going about it, many of which could undermine the success of your efforts in a diverse range of ways. I want to work with you guys to navigate those complications and come up with an approach that will work well for everyone involved: you guys, Lone Wolf, and RW users who want to use what you guys are putting together. :) So keep working on your respective projects. My desire is to figure out how to make them a success. |
Quote:
to be told you'll be serving detention for the rest of the week. It can have either connotation, and you never know which one until you walk into the office and sit down. But I think we now know what kind of a student you were. ;-) |
All times are GMT -8. The time now is 02:36 PM. |
Powered by vBulletin® - Copyright ©2000 - 2024, vBulletin Solutions, Inc.
wolflair.com copyright ©1998-2016 Lone Wolf Development, Inc. View our Privacy Policy here.