Re: Potential proposal + request volunteers for champion mentor roles - MetaModel
On 1/28/2013 11:07 AM, Kasper Sørensen wrote: Dear all, After some time spent (yeah, sorry quite a lot more time than we had hoped), we finally now have the green light to officially post a proposal to the Incubator to take on MetaModel as a project. Since it's been a while, I wish to call out again for sponsors. We found a few some months ago, but we where out of contact for so long I feel it's most fair to ask again. Please find below the draft proposal which we would love to further work on together with sponsors before finally submitting it. (I tried posting it on the wiki but was not authorized, probably because my account is a new one). Best regards, Kasper Sørensen - MetaModel - uniform data access across datastores Proposal for Apache Incubator Hello, I made few weeks a go a proposal (in very early stages of conception) that may marry very well with this project. You find the infos (very short at the moment) at the following URL: https://sourceforge.net/projects/rdbmssr It has to do with software redundancy on RDBMS so I'll be pleased if you may have an opinion on it and send me some further pointers about MetaModel. My idea was to target the most commercial databases first (Oracle, MS SQL Server, etc...) as the most widely used and to use as a language C/C++ for reasons of efficiency. Kind regards Federico - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Potential proposal + request volunteers for champion mentor roles - MetaModel
Kasper Sørensen wrote: Thank you for helping David. My username is KasperSorensen. Can someone please provide me access to create a new proposal wiki page on http://wiki.apache.org/incubator/ProjectProposals ? Done. -David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: Potential proposal + request volunteers for champion mentor roles - MetaModel
The proposal is now available on the wiki: http://wiki.apache.org/incubator/MetaModelProposal Anyone who wants to help sponsor/champion this proposal? -Original Message- From: David Crossley [mailto:cross...@apache.org] Sent: 29. januar 2013 22:18 To: general@incubator.apache.org Subject: Re: Potential proposal + request volunteers for champion mentor roles - MetaModel Kasper Sørensen wrote: Thank you for helping David. My username is KasperSorensen. Can someone please provide me access to create a new proposal wiki page on http://wiki.apache.org/incubator/ProjectProposals ? Done. -David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Potential proposal + request volunteers for champion mentor roles - MetaModel
Dear all, After some time spent (yeah, sorry quite a lot more time than we had hoped), we finally now have the green light to officially post a proposal to the Incubator to take on MetaModel as a project. Since it's been a while, I wish to call out again for sponsors. We found a few some months ago, but we where out of contact for so long I feel it's most fair to ask again. Please find below the draft proposal which we would love to further work on together with sponsors before finally submitting it. (I tried posting it on the wiki but was not authorized, probably because my account is a new one). Best regards, Kasper Sørensen - MetaModel - uniform data access across datastores Proposal for Apache Incubator - Abstract MetaModel is a data access framework, providing a common interface for exploration and querying of different types of datastores. Proposal MetaModel provides a uniform meta-model for exploring and querying the structure of datastores, covering but not limited to relational databases. The scope of the project is to stay domain-agnostic, so the meta-model will be concerned with schemas, tables, columns, rows, relationships etc. On top of this meta-model a rich querying API is provided which resembles SQL, but built using compiler-checked Java language constructs. For datastores that do not have a native SQL-compatible query engine, the MetaModel project also includes an abstract Java-based query engine implementation which individual datastore-modules can adapt to fit the concrete datastore. Background The MetaModel project was initially developed by eobject.dk to service the DataCleaner application. The main requirement was to perform data querying and modification operations on a wide range of quite different datastores. Furthermore a programmatic query model was needed in order to allow different components to influence the query plan. In 2009, Human Inference acquired the eobjects projects including MetaModel. Since then MetaModel has been put to extensive use in the Human Inference products. The open source nature of the project was reinforced, leading to a significant growth in the community. MetaModel has successfully been used in a number of other open source projects as well as mission critical commercial software from Human Inference. Rationale Different types of datastores have different characteristics, which always lead to the interfaces for these being different from one another. Standards like JDBC and the SQL language attempt to standardize data access, but for some datastore types like flat files, spreadsheets, NoSQL databases and more, such standards are not even implementable. Specialization in interfaces obviously has merit for optimized usage, but for integration tools, batch applications and or generic data modification tools, this myriad of specialized interfaces is a big pain. Furthermore, being able to query every datastore with a basic set of SQL-like features can be a great productivity boost for a wide range of applications. Initial goals MetaModel is already a stable project, so initial goals are more oriented towards an adaption to the Apache ecosystem than about functional changes. We are constantly adding more datastore types to the portfolio (currently a Salesforce.com web service consumer datastore is being tested), but the core modules have not had drastic changes for some time. Our focus will be on making ties with other Apache projects (such as POI, Gora and CouchDB) and potentially renaming the 'MetaModel' project to something more rememberable. -- Current status Meritocracy We intend to do everything we can to encourage a meritocracy in the development of MetaModel. Currently most important development and design decisions have been made at Human Inference, but with an open window for anyone to participate on mailing lists and discussion forums. We believe that the approach going forward should be more encouraging by sharing all the design ideas and discussions in the open, not only just the topics that have been dragged into the open by third parties. We believe that meritocracy will be further stimulated by granting the control of the project to an independent committee. Community The community around MetaModel already exists, but we believe it will grow substantially by becoming an Apache project. With MetaModel used in a wide range of both open and closed source application, both at Human Inference (HIquality MDM), it's open source projects DataCleaner, SassyReader and AnalyzerBeans and by other parties (such as the Quipo data warehouse automation project), we believe that the critical mass to sustain a community is there. Core developers MetaModel was founded by Kasper Sørensen in 2009. Later it was incorporated as a core library by Human Inference, meaning that more than 20
Re: Potential proposal + request volunteers for champion mentor roles - MetaModel
Hi Kasper, the proposal looks quite interesting, but I have two questions: 1) How this is related with the emergent at ASF elated with RDF (mainly Jena and Marmotta)? I see some clear lines of cooperation there. 2) How this proposal is related with other well-established open source tools? Such as DataNucleus AccessPlatform http://www.datanucleus.org/products/accessplatform/. Greetings, On 28/01/13 11:07, Kasper Sørensen wrote: Dear all, After some time spent (yeah, sorry quite a lot more time than we had hoped), we finally now have the green light to officially post a proposal to the Incubator to take on MetaModel as a project. Since it's been a while, I wish to call out again for sponsors. We found a few some months ago, but we where out of contact for so long I feel it's most fair to ask again. Please find below the draft proposal which we would love to further work on together with sponsors before finally submitting it. (I tried posting it on the wiki but was not authorized, probably because my account is a new one). Best regards, Kasper Sørensen - MetaModel - uniform data access across datastores Proposal for Apache Incubator - Abstract MetaModel is a data access framework, providing a common interface for exploration and querying of different types of datastores. Proposal MetaModel provides a uniform meta-model for exploring and querying the structure of datastores, covering but not limited to relational databases. The scope of the project is to stay domain-agnostic, so the meta-model will be concerned with schemas, tables, columns, rows, relationships etc. On top of this meta-model a rich querying API is provided which resembles SQL, but built using compiler-checked Java language constructs. For datastores that do not have a native SQL-compatible query engine, the MetaModel project also includes an abstract Java-based query engine implementation which individual datastore-modules can adapt to fit the concrete datastore. Background The MetaModel project was initially developed by eobject.dk to service the DataCleaner application. The main requirement was to perform data querying and modification operations on a wide range of quite different datastores. Furthermore a programmatic query model was needed in order to allow different components to influence the query plan. In 2009, Human Inference acquired the eobjects projects including MetaModel. Since then MetaModel has been put to extensive use in the Human Inference products. The open source nature of the project was reinforced, leading to a significant growth in the community. MetaModel has successfully been used in a number of other open source projects as well as mission critical commercial software from Human Inference. Rationale Different types of datastores have different characteristics, which always lead to the interfaces for these being different from one another. Standards like JDBC and the SQL language attempt to standardize data access, but for some datastore types like flat files, spreadsheets, NoSQL databases and more, such standards are not even implementable. Specialization in interfaces obviously has merit for optimized usage, but for integration tools, batch applications and or generic data modification tools, this myriad of specialized interfaces is a big pain. Furthermore, being able to query every datastore with a basic set of SQL-like features can be a great productivity boost for a wide range of applications. Initial goals MetaModel is already a stable project, so initial goals are more oriented towards an adaption to the Apache ecosystem than about functional changes. We are constantly adding more datastore types to the portfolio (currently a Salesforce.com web service consumer datastore is being tested), but the core modules have not had drastic changes for some time. Our focus will be on making ties with other Apache projects (such as POI, Gora and CouchDB) and potentially renaming the 'MetaModel' project to something more rememberable. -- Current status Meritocracy We intend to do everything we can to encourage a meritocracy in the development of MetaModel. Currently most important development and design decisions have been made at Human Inference, but with an open window for anyone to participate on mailing lists and discussion forums. We believe that the approach going forward should be more encouraging by sharing all the design ideas and discussions in the open, not only just the topics that have been dragged into the open by third parties. We believe that meritocracy will be further stimulated by granting the control of the project to an independent committee. Community The community around MetaModel already exists, but we believe it will grow substantially by becoming an Apache project. With MetaModel used in a wide range of both open and
RE: Potential proposal + request volunteers for champion mentor roles - MetaModel
Hi Sergio, I am not sure how to characterize the comparison with RDF / Jena / Marmotta, since I actually didn't know about these topics before now. Linked data might be a relevant topic for MetaModel also, but in the current form MetaModel is very much focused on a tabular view of data, resembling that of RDBMs, CSV/spreadsheet files etc. But also to adapt other datastores to a similar tabular view so that very widely used SQL techniques and wisdom can be applied to it. Not because we love SQL (MetaModel also supports several NoSQL databases), but because we needed a common metaphor of all data and data tables was found to be the easiest metaphor to comprehend for the users. We've looked to DataNucleus a few times also. They do a good job in implementing the various object mapping protocols (JDO/JPA etc.) but less so (to my understanding) of exposing data in a dynamic model. As such I see them as a ORM library, where we're still metadata-driven. The metadata that drives MetaModel comes from the datastore itself, not from the application code. So if you add a column to your database, or a sheet to your spreadsheet - then it automatically is also available in MetaModel. In a ORM you would define a new entity type etc. which is what we needed to get rid of, because the kind of application that typically runs on MetaModel is focused on the data itself, not any specific domain. Hope this makes some sort of sense :-) Best regards, Kasper -Original Message- From: Sergio Fernández [mailto:sergio.fernan...@salzburgresearch.at] Sent: 28. januar 2013 12:21 To: general@incubator.apache.org Cc: Kasper Sørensen Subject: Re: Potential proposal + request volunteers for champion mentor roles - MetaModel Hi Kasper, the proposal looks quite interesting, but I have two questions: 1) How this is related with the emergent at ASF elated with RDF (mainly Jena and Marmotta)? I see some clear lines of cooperation there. 2) How this proposal is related with other well-established open source tools? Such as DataNucleus AccessPlatform http://www.datanucleus.org/products/accessplatform/. Greetings, On 28/01/13 11:07, Kasper Sørensen wrote: Dear all, After some time spent (yeah, sorry quite a lot more time than we had hoped), we finally now have the green light to officially post a proposal to the Incubator to take on MetaModel as a project. Since it's been a while, I wish to call out again for sponsors. We found a few some months ago, but we where out of contact for so long I feel it's most fair to ask again. Please find below the draft proposal which we would love to further work on together with sponsors before finally submitting it. (I tried posting it on the wiki but was not authorized, probably because my account is a new one). Best regards, Kasper Sørensen - MetaModel - uniform data access across datastores Proposal for Apache Incubator - Abstract MetaModel is a data access framework, providing a common interface for exploration and querying of different types of datastores. Proposal MetaModel provides a uniform meta-model for exploring and querying the structure of datastores, covering but not limited to relational databases. The scope of the project is to stay domain-agnostic, so the meta-model will be concerned with schemas, tables, columns, rows, relationships etc. On top of this meta-model a rich querying API is provided which resembles SQL, but built using compiler-checked Java language constructs. For datastores that do not have a native SQL-compatible query engine, the MetaModel project also includes an abstract Java-based query engine implementation which individual datastore-modules can adapt to fit the concrete datastore. Background The MetaModel project was initially developed by eobject.dk to service the DataCleaner application. The main requirement was to perform data querying and modification operations on a wide range of quite different datastores. Furthermore a programmatic query model was needed in order to allow different components to influence the query plan. In 2009, Human Inference acquired the eobjects projects including MetaModel. Since then MetaModel has been put to extensive use in the Human Inference products. The open source nature of the project was reinforced, leading to a significant growth in the community. MetaModel has successfully been used in a number of other open source projects as well as mission critical commercial software from Human Inference. Rationale Different types of datastores have different characteristics, which always lead to the interfaces for these being different from one another. Standards like JDBC and the SQL language attempt to standardize data access, but for some datastore types like flat files, spreadsheets, NoSQL databases and more, such standards
Re: Potential proposal + request volunteers for champion mentor roles - MetaModel
Kasper Sørensen wrote: Dear all, After some time spent (yeah, sorry quite a lot more time than we had hoped), we finally now have the green light to officially post a proposal to the Incubator to take on MetaModel as a project. Since it's been a while, I wish to call out again for sponsors. We found a few some months ago, but we where out of contact for so long I feel it's most fair to ask again. Please find below the draft proposal which we would love to further work on together with sponsors before finally submitting it. (I tried posting it on the wiki but was not authorized, probably because my account is a new one). You need to ask on this general@ list and tell your wiki username. See http://wiki.apache.org/incubator/FrontPage -David Best regards, Kasper Sørensen - MetaModel - uniform data access across datastores Proposal for Apache Incubator - Abstract MetaModel is a data access framework, providing a common interface for exploration and querying of different types of datastores. Proposal MetaModel provides a uniform meta-model for exploring and querying the structure of datastores, covering but not limited to relational databases. The scope of the project is to stay domain-agnostic, so the meta-model will be concerned with schemas, tables, columns, rows, relationships etc. On top of this meta-model a rich querying API is provided which resembles SQL, but built using compiler-checked Java language constructs. For datastores that do not have a native SQL-compatible query engine, the MetaModel project also includes an abstract Java-based query engine implementation which individual datastore-modules can adapt to fit the concrete datastore. Background The MetaModel project was initially developed by eobject.dk to service the DataCleaner application. The main requirement was to perform data querying and modification operations on a wide range of quite different datastores. Furthermore a programmatic query model was needed in order to allow different components to influence the query plan. In 2009, Human Inference acquired the eobjects projects including MetaModel. Since then MetaModel has been put to extensive use in the Human Inference products. The open source nature of the project was reinforced, leading to a significant growth in the community. MetaModel has successfully been used in a number of other open source projects as well as mission critical commercial software from Human Inference. Rationale Different types of datastores have different characteristics, which always lead to the interfaces for these being different from one another. Standards like JDBC and the SQL language attempt to standardize data access, but for some datastore types like flat files, spreadsheets, NoSQL databases and more, such standards are not even implementable. Specialization in interfaces obviously has merit for optimized usage, but for integration tools, batch applications and or generic data modification tools, this myriad of specialized interfaces is a big pain. Furthermore, being able to query every datastore with a basic set of SQL-like features can be a great productivity boost for a wide range of applications. Initial goals MetaModel is already a stable project, so initial goals are more oriented towards an adaption to the Apache ecosystem than about functional changes. We are constantly adding more datastore types to the portfolio (currently a Salesforce.com web service consumer datastore is being tested), but the core modules have not had drastic changes for some time. Our focus will be on making ties with other Apache projects (such as POI, Gora and CouchDB) and potentially renaming the 'MetaModel' project to something more rememberable. -- Current status Meritocracy We intend to do everything we can to encourage a meritocracy in the development of MetaModel. Currently most important development and design decisions have been made at Human Inference, but with an open window for anyone to participate on mailing lists and discussion forums. We believe that the approach going forward should be more encouraging by sharing all the design ideas and discussions in the open, not only just the topics that have been dragged into the open by third parties. We believe that meritocracy will be further stimulated by granting the control of the project to an independent committee. Community The community around MetaModel already exists, but we believe it will grow substantially by becoming an Apache project. With MetaModel used in a wide range of both open and closed source application, both at Human Inference (HIquality MDM), it's open source projects DataCleaner, SassyReader and AnalyzerBeans and by other parties (such as the Quipo data
RE: Potential proposal + request volunteers for champion mentor roles - MetaModel
Thank you for helping David. My username is KasperSorensen. Can someone please provide me access to create a new proposal wiki page on http://wiki.apache.org/incubator/ProjectProposals ? Best regards, Kasper -Original Message- From: David Crossley [mailto:cross...@apache.org] Sent: 29. januar 2013 04:51 To: general@incubator.apache.org Subject: Re: Potential proposal + request volunteers for champion mentor roles - MetaModel Kasper Sørensen wrote: Dear all, After some time spent (yeah, sorry quite a lot more time than we had hoped), we finally now have the green light to officially post a proposal to the Incubator to take on MetaModel as a project. Since it's been a while, I wish to call out again for sponsors. We found a few some months ago, but we where out of contact for so long I feel it's most fair to ask again. Please find below the draft proposal which we would love to further work on together with sponsors before finally submitting it. (I tried posting it on the wiki but was not authorized, probably because my account is a new one). You need to ask on this general@ list and tell your wiki username. See http://wiki.apache.org/incubator/FrontPage -David Best regards, Kasper Sørensen - MetaModel - uniform data access across datastores Proposal for Apache Incubator - Abstract MetaModel is a data access framework, providing a common interface for exploration and querying of different types of datastores. Proposal MetaModel provides a uniform meta-model for exploring and querying the structure of datastores, covering but not limited to relational databases. The scope of the project is to stay domain-agnostic, so the meta-model will be concerned with schemas, tables, columns, rows, relationships etc. On top of this meta-model a rich querying API is provided which resembles SQL, but built using compiler-checked Java language constructs. For datastores that do not have a native SQL-compatible query engine, the MetaModel project also includes an abstract Java-based query engine implementation which individual datastore-modules can adapt to fit the concrete datastore. Background The MetaModel project was initially developed by eobject.dk to service the DataCleaner application. The main requirement was to perform data querying and modification operations on a wide range of quite different datastores. Furthermore a programmatic query model was needed in order to allow different components to influence the query plan. In 2009, Human Inference acquired the eobjects projects including MetaModel. Since then MetaModel has been put to extensive use in the Human Inference products. The open source nature of the project was reinforced, leading to a significant growth in the community. MetaModel has successfully been used in a number of other open source projects as well as mission critical commercial software from Human Inference. Rationale Different types of datastores have different characteristics, which always lead to the interfaces for these being different from one another. Standards like JDBC and the SQL language attempt to standardize data access, but for some datastore types like flat files, spreadsheets, NoSQL databases and more, such standards are not even implementable. Specialization in interfaces obviously has merit for optimized usage, but for integration tools, batch applications and or generic data modification tools, this myriad of specialized interfaces is a big pain. Furthermore, being able to query every datastore with a basic set of SQL-like features can be a great productivity boost for a wide range of applications. Initial goals MetaModel is already a stable project, so initial goals are more oriented towards an adaption to the Apache ecosystem than about functional changes. We are constantly adding more datastore types to the portfolio (currently a Salesforce.com web service consumer datastore is being tested), but the core modules have not had drastic changes for some time. Our focus will be on making ties with other Apache projects (such as POI, Gora and CouchDB) and potentially renaming the 'MetaModel' project to something more rememberable. -- Current status Meritocracy We intend to do everything we can to encourage a meritocracy in the development of MetaModel. Currently most important development and design decisions have been made at Human Inference, but with an open window for anyone to participate on mailing lists and discussion forums. We believe that the approach going forward should be more encouraging by sharing all the design ideas and discussions in the open, not only just the topics that have been dragged into the open by third parties. We believe that meritocracy will be further stimulated
