Michael Morris
First Post
Hello all. I've begun work on a database of feats (which should in all likelihood be followed by a database of spells at the least). This database will be integrated with the messageboards in a couple of ways, one of which will be the ablity to link a feat simply putting its name between UUB codes, like so.
{feat}Name{/feat}
The database will be populated by the community supporters here at EN World - registered users will be able to see the SRD items in the database but will be unable to view any custom items submitted by users or submit any of their own. The submission works using the same underpinnings as normal posts (essentially the feats forum is a post forum with extra message fields for prerequisites, comments, etc.)
Now to the sticking point. How should, or for that matter 'should' the database contain the open gaming content of books? Before you give an answer, please read over some of the ideas running in my head over this.
First, it's not my wish to adversely impact anyone's income. If anything I would hope the feats database would allow publishers free advertising for their products. Also, I would like it to serve the purpose of being an undisputable open content version of the materials. So, here then is a chance for publishers to outline precisely how they wish their materials to appear if reprinted.
Now, for some ideas on insuring such a database doesn't undercut anyone. One or more of these might be used in varying combinations.
[h3]Passwording[/h3]
The most complicated way is to have the user provide some proof that they own the book before viewing the material. This password would be something like "Open your book to page 123 and enter the 3rd word at the top of the 3rd paragraph." Alternately, the user could be required to enter the book's UPC code (the number beneath the bar code on the book for those unfamiliar with the term).
Problems:
Against a dedicated hacker this is more gesture than effective measure, but then again so is everything. A technical problem is that an extra datafield will have to be added to the users database (not so much of a problem, but it will require a shutdown of the server for about an hour to implement - updating 13,000 user fields is not a walk in the park).
[h3]Hobbled System[/h3]
Set the database up so that a given user can only look for X feats in a given time period before the system won't provide more feats. Note that I'm tempted to allow registered users to take 3 peaks / day anyway to encourage more community supporter accounts.
Problems:
More annoyance than barrier, and alts wouldn't be affected unless IP tracking is employed.
[h3]Subscription System[/h3]
This third setup, similar to vbulletin.org, put's the burden of sorting out who should and shouldn't view the files to the publishers in the following manner: Each publisher would maintain users list either at ENWorld or on their own machine that contains the user ids of those they want to have access to the feats from their products. Payments beyond those required to have a community supporters account are left up to the publishers.
Problems:
Pricing would be a sticky issue for many, and the larger publishers would have a pricing advantage over their peers. Also, arguments might erupt in cases where one publisher has reprinted another's work under the OGL and pricing is different.
[h3]Moratorium Approach[/h3]
My personal favorite approach, possibly because I think it would be the most effective but also because I know it's the easiest of all these to implement is a simple moratorium approach. Simply - no feats will be reprinted here until 6 months have passed since their release.
Problems:
The real patient community supporters are getting a bargain of sorts. However, many of them I feel may choose to make a purchase based on what they see here.
[h3]Legal Issues[/h3]
I am not a lawyer, but I am keenly interested in what steps must be taken to make sure that this database will comply with the OGL license.
Well, brainstorm over - I'm going back to coding on this thing.
{feat}Name{/feat}
The database will be populated by the community supporters here at EN World - registered users will be able to see the SRD items in the database but will be unable to view any custom items submitted by users or submit any of their own. The submission works using the same underpinnings as normal posts (essentially the feats forum is a post forum with extra message fields for prerequisites, comments, etc.)
Now to the sticking point. How should, or for that matter 'should' the database contain the open gaming content of books? Before you give an answer, please read over some of the ideas running in my head over this.
First, it's not my wish to adversely impact anyone's income. If anything I would hope the feats database would allow publishers free advertising for their products. Also, I would like it to serve the purpose of being an undisputable open content version of the materials. So, here then is a chance for publishers to outline precisely how they wish their materials to appear if reprinted.
Now, for some ideas on insuring such a database doesn't undercut anyone. One or more of these might be used in varying combinations.
[h3]Passwording[/h3]
The most complicated way is to have the user provide some proof that they own the book before viewing the material. This password would be something like "Open your book to page 123 and enter the 3rd word at the top of the 3rd paragraph." Alternately, the user could be required to enter the book's UPC code (the number beneath the bar code on the book for those unfamiliar with the term).
Problems:
Against a dedicated hacker this is more gesture than effective measure, but then again so is everything. A technical problem is that an extra datafield will have to be added to the users database (not so much of a problem, but it will require a shutdown of the server for about an hour to implement - updating 13,000 user fields is not a walk in the park).
[h3]Hobbled System[/h3]
Set the database up so that a given user can only look for X feats in a given time period before the system won't provide more feats. Note that I'm tempted to allow registered users to take 3 peaks / day anyway to encourage more community supporter accounts.
Problems:
More annoyance than barrier, and alts wouldn't be affected unless IP tracking is employed.
[h3]Subscription System[/h3]
This third setup, similar to vbulletin.org, put's the burden of sorting out who should and shouldn't view the files to the publishers in the following manner: Each publisher would maintain users list either at ENWorld or on their own machine that contains the user ids of those they want to have access to the feats from their products. Payments beyond those required to have a community supporters account are left up to the publishers.
Problems:
Pricing would be a sticky issue for many, and the larger publishers would have a pricing advantage over their peers. Also, arguments might erupt in cases where one publisher has reprinted another's work under the OGL and pricing is different.
[h3]Moratorium Approach[/h3]
My personal favorite approach, possibly because I think it would be the most effective but also because I know it's the easiest of all these to implement is a simple moratorium approach. Simply - no feats will be reprinted here until 6 months have passed since their release.
Problems:
The real patient community supporters are getting a bargain of sorts. However, many of them I feel may choose to make a purchase based on what they see here.
[h3]Legal Issues[/h3]
I am not a lawyer, but I am keenly interested in what steps must be taken to make sure that this database will comply with the OGL license.
Well, brainstorm over - I'm going back to coding on this thing.
Last edited: