I went to join the project. But, I had to agree to the following
license. Before i do... does anyone see why any of us would not want
to agree to this? I would just hate for our eyes to see something m$
and get accused of some breach because we have code with similar
functionality. I am increasingly more cautious about m$ entering the
OSS arena. So , forgive my exaggerated since of caution.
Brandon
------------------------------------------------------------------------------------
LICENSE
-------------------------------------------------------------------------------------
Shared Source License for The Data Mapping Application Block
This license governs use of the accompanying software ('Software'), and your
use of the Software constitutes acceptance of this license.
You may use the Software for any commercial or noncommercial purpose,
including distributing derivative works.
In return, we simply require that you agree:
1. Not to remove any copyright or other notices from the Software.
2. That if you distribute the Software in source code form you do so only
under this license (i.e. you must include a complete copy of this license
with your distribution), and if you distribute the Software solely in
object form you only do so under a license that complies with this
license.
3. That the Software comes "as is", with no warranties. None whatsoever.
This means no express, implied or statutory warranty, including without
limitation, warranties of merchantability or fitness for a particular
purpose or any warranty of title or non-infringement. Also, you must pass
this disclaimer on whenever you distribute the Software or derivative
works.
4. That no contributor to the Software will be liable for any of those types
of damages known as indirect, special, consequential, or incidental
related to the Software or this license, to the maximum extent the law
permits, no matter what legal theory it's based on. Also, you must pass
this limitation of liability on whenever you distribute the Software or
derivative works.
5. That if you sue anyone over patents that you think may apply to the
Software for a person's use of the Software, your license to the Software
ends automatically.
6. That the patent rights, if any, granted in this license only apply to the
Software, not to any derivative works you make.
7. That the Software is subject to U.S. export jurisdiction at the time it
is licensed to you, and it may be subject to additional export or import
laws in other places. You agree to comply with all such laws and
regulations that may apply to the Software after delivery of the software
to you.
8. That if you are an agency of the U.S. Government, (i) Software provided
pursuant to a solicitation issued on or after December 1, 1995, is
provided with the commercial license rights set forth in this license,
and (ii) Software provided pursuant to a solicitation issued prior to
December 1, 1995, is provided with "Restricted Rights" as set forth in
FAR, 48 C.F.R. 52.227-14 (June 1987) or DFAR, 48 C.F.R. 252.227-7013
(Oct 1988), as applicable.
9. That your rights under this License end automatically if you breach it in
any way.
10.That all rights not expressly granted to you in this license are reserved.
On 5/27/05, Brandon Goodin <[EMAIL PROTECTED]> wrote:
> Does anyone know much about this project (Data Mapping Application Block)?
>
> The Data Mapping Application Block C#, VB.NET
>
> "The Data Mapper is a layer of software that separates the in-memory
> objects from the database. Its responsibility is to transfer data
> between the two ends to isolate them from each other. With Data Mapper
> the in-memory objects needn't know even that there's a database
> present; they need no SQL interface code, and certainly no knowledge
> of the database schema." (Fowler, Martin, Patterns of Enterprise
> Application Architecture, p. 165) Data Mappers equate to what is known
> as Data Access Logic Components (DALCs). This application block is
> intended to make it easier for producers of business DALCs to create
> common functionality that relates to managing "entities" with CRUD
> functions. The DataMapper also promotes the use of stored procedures
> as a best practice to abstract data access from the underlying data
> schema and increase performance. Finally, the DataMapper allows
> capabilities like the use of transactions, command timeouts, and
> caching properties to be added, removed, and modified through
> configuration when needed. For example, to add transactions or caching
> to a DALC, no code will need to be modified -- only configuration
> settings.
>
> http://www.gotdotnet.com/workspaces/directory.aspx?&Column=ActivityPercentile&Direction=DESC&Page=6&Size=10&FO=1&PPS=1
>
> Brandon
>
