NCBO-OOR Development - Revision history

Benjamindai: /* OOR Developer Collaboration */

2009-03-07T00:23:21Z

OOR Developer Collaboration

Benjamindai: /* OOR Developer Collaboration */

2009-02-19T19:37:56Z

OOR Developer Collaboration

Benjamindai: /* OOR Developer Collaboration */

2009-02-19T19:37:35Z

OOR Developer Collaboration

Benjamindai: /* NCBO-OOR Developer Collaboration */

2009-02-19T19:35:45Z

NCBO-OOR Developer Collaboration

Benjamindai at 19:34, 19 February 2009

2009-02-19T19:34:18Z

Benjamindai: /* NCBO-OOR Developer Collaboration */

2009-02-19T19:30:45Z

NCBO-OOR Developer Collaboration

Benjamindai at 19:18, 19 February 2009

2009-02-19T19:18:04Z

Benjamindai at 19:17, 19 February 2009

2009-02-19T19:17:35Z

Benjamindai: /* NCBO-OOR Developer Collaboration */

2009-02-19T19:11:23Z

NCBO-OOR Developer Collaboration

Benjamindai: /* NCBO-OOR Developer Collaboration */

2009-02-19T19:09:53Z

NCBO-OOR Developer Collaboration

← Older revision		Revision as of 00:23, 7 March 2009
Line 26:		Line 26:
	The OOR developer collaboration will leverage practices that have worked successfully for various OOR community participants. The collaboration approach is still under construction.		The OOR developer collaboration will leverage practices that have worked successfully for various OOR community participants. The collaboration approach is still under construction.

−	An example of practices that the OOR could leverage is the [[NCBO Developer Communications \| NCBO developer communications infrastructure]]. This has been established and driven by the NCBO Chief Software Architect (Benjamin Dai) which includes communications channels, source control processes/practices, and NCBO quarterly developer conferences for which all NCBO partners are invited. Though all NCBO partners are welcome to the conferences, they ~~focuses~~ primarily on how NCBO software can best serve biomedical communities.	+	An example of practices that the OOR could leverage is the [[NCBO Developer Communications \| NCBO developer communications infrastructure]]. This has been established and driven by the NCBO Chief Software Architect (Benjamin Dai) which includes communications channels, source control processes/practices, and NCBO quarterly developer conferences for which all NCBO partners are invited. Though all NCBO partners are welcome to the conferences, they focus primarily on how NCBO software can best serve biomedical communities.

← Older revision		Revision as of 19:37, 19 February 2009
Line 26:		Line 26:
	The OOR developer collaboration will leverage practices that have worked successfully for various OOR community participants. The collaboration approach is still under construction.		The OOR developer collaboration will leverage practices that have worked successfully for various OOR community participants. The collaboration approach is still under construction.

−	An example of practices that the OOR could leverage is the [[NCBO Developer Communications \| NCBO developer communications infrastructure]]. This has been established and driven by the NCBO Chief Software Architect (Benjamin Dai) which includes a communications channels, source control processes/practices, and NCBO quarterly developer conferences for which all NCBO partners are invited. Though all NCBO partners are welcome to the conferences, they focuses primarily on how NCBO software can best serve biomedical communities.	+	An example of practices that the OOR could leverage is the [[NCBO Developer Communications \| NCBO developer communications infrastructure]]. This has been established and driven by the NCBO Chief Software Architect (Benjamin Dai) which includes communications channels, source control processes/practices, and NCBO quarterly developer conferences for which all NCBO partners are invited. Though all NCBO partners are welcome to the conferences, they focuses primarily on how NCBO software can best serve biomedical communities.

← Older revision		Revision as of 19:37, 19 February 2009
Line 26:		Line 26:
	The OOR developer collaboration will leverage practices that have worked successfully for various OOR community participants. The collaboration approach is still under construction.		The OOR developer collaboration will leverage practices that have worked successfully for various OOR community participants. The collaboration approach is still under construction.

−	An example of practices that the OOR could leverage is the [[NCBO Developer Communications \| NCBO developer communications infrastructure]]. This has been established and driven by the NCBO Chief Software Architect (Benjamin Dai) which includes a NCBO quarterly developer conferences for which all NCBO partners are invited. Though all NCBO partners are welcome, ~~the conference~~ focuses primarily on how NCBO software can best serve ~~the~~ biomedical communities.	+	An example of practices that the OOR could leverage is the [[NCBO Developer Communications \| NCBO developer communications infrastructure]]. This has been established and driven by the NCBO Chief Software Architect (Benjamin Dai) which includes a communications channels, source control processes/practices, and NCBO quarterly developer conferences for which all NCBO partners are invited. Though all NCBO partners are welcome to the conferences, they focuses primarily on how NCBO software can best serve biomedical communities.

@@ Line 23: / Line 23: @@
 ) NCBO-OOR Production - Deployment of the NCBO-OOR software in a server environment that mimics the NCBO BioPortal Production environment.
-=NCBO-OOR Developer Collaboration=
+=OOR Developer Collaboration=
-The NCBO-OOR developer collaboration will leverage practices that have worked successfully for various OOR community participants.  The collaboration approach is still under construction.
+The OOR developer collaboration will leverage practices that have worked successfully for various OOR community participants.  The collaboration approach is still under construction.
 An example of practices that the OOR could leverage is the [[NCBO Developer Communications | NCBO developer communications infrastructure]].  This has been established and driven by the NCBO Chief Software Architect (Benjamin Dai) which includes a NCBO quarterly developer conferences for which all NCBO partners are invited.  Though all NCBO partners are welcome, the  conference focuses primarily on how NCBO software can best serve the biomedical communities.

@@ Line 3: / Line 3: @@
 * The [[NCBO-OOR Architecture]] page provides a general architecture and philosphy used in it's design and development.   This page is geared for any reader who has a basic understanding of multi-tier software architecture.
-* The [[NCBO-OOR Server-Side Customization]] page describes the design and approach to customization of NCBO-OOR server-side components.  To fully execute the examples presented on this page requires that the readers have an understanding of the principles of Aspect of Oriented programming and the [http://www.springsource.org/ Spring technology framework].  The author strongly recommends reading the [[NCBO-OOR Architecture]] page before diving into this document to ensure the reader has a good context.
+* The [[NCBO-OOR Server-Side Customization]] page describes the design and approach to customization of NCBO-OOR server-side components.  To fully execute the examples presented on this page requires that the readers have an understanding of the principles of Aspect of Oriented programming and the open source [http://www.springsource.org/ Spring technology framework].  The author strongly recommends reading the [[NCBO-OOR Architecture]] page before diving into this document to ensure the reader has a good context.
 * The [[NCBO-OOR Source Control Practices and Processes]] page describes the practices and processes expected to encourage the open source collaboration of geographically dispersed development teams.

← Older revision		Revision as of 19:30, 19 February 2009
Line 26:		Line 26:
	The NCBO-OOR developer collaboration will leverage practices that have worked successfully for various OOR community participants. The collaboration approach is still under construction.		The NCBO-OOR developer collaboration will leverage practices that have worked successfully for various OOR community participants. The collaboration approach is still under construction.

−	An example of practices that the OOR could leverage is the [[NCBO Developer Communications \| NCBO developer communications infrastructure]]. This has been established and driven by the NCBO Chief Software Architect which includes a NCBO quarterly developer conferences for which all NCBO partners are invited. Though all NCBO partners are welcome, the conference focuses primarily on how NCBO software can best serve the biomedical communities.	+	An example of practices that the OOR could leverage is the [[NCBO Developer Communications \| NCBO developer communications infrastructure]]. This has been established and driven by the NCBO Chief Software Architect (Benjamin Dai) which includes a NCBO quarterly developer conferences for which all NCBO partners are invited. Though all NCBO partners are welcome, the conference focuses primarily on how NCBO software can best serve the biomedical communities.

← Older revision		Revision as of 19:18, 19 February 2009
Line 1:		Line 1:
−	Welcome to the OOR Project! This developer's guide provides an introduction to the OOR architecture and steps (with examples) of how to customize server-side components. The ~~NCBO-~~OOR project is a collaborative open source endeavor to meet the needs of the [http://ontolog.cim3.net/cgi-bin/wiki.pl?OOR Open Ontology Repository (OOR) Initiative.] The Ontology Open Repository (OOR) initiative is using the BioPortal 2.0 software as a basis for their first "~~NCBO-~~OOR" deployment to begin serving its diverse communities. This page serves as a launch point for understanding the ~~NCBO-~~OOR architecture and getting started with customizing the code to advance OOR goals and objectives.	+	Welcome to the OOR Project! This developer's guide provides an introduction to the OOR architecture and steps (with examples) of how to customize server-side components. The OOR project is a collaborative open source endeavor to meet the needs of the [http://ontolog.cim3.net/cgi-bin/wiki.pl?OOR Open Ontology Repository (OOR) Initiative.] The Ontology Open Repository (OOR) initiative is using the BioPortal 2.0 software as a basis for their first "OOR" deployment to begin serving its diverse communities. This page serves as a launch point for understanding the OOR architecture and getting started with customizing the code to advance OOR goals and objectives.

	* The [[NCBO-OOR Architecture]] page provides a general architecture and philosphy used in it's design and development. This page is geared for any reader who has a basic understanding of multi-tier software architecture.		* The [[NCBO-OOR Architecture]] page provides a general architecture and philosphy used in it's design and development. This page is geared for any reader who has a basic understanding of multi-tier software architecture.

← Older revision		Revision as of 19:17, 19 February 2009
Line 1:		Line 1:
−	Welcome to the ~~NCBO-~~OOR Project! This developer's guide provides an introduction to the ~~NCBO-~~OOR architecture and steps (with examples) of how to customize server-side components. The NCBO-OOR project is a collaborative open source endeavor to meet the needs of the [http://ontolog.cim3.net/cgi-bin/wiki.pl?OOR Open Ontology Repository (OOR) Initiative.] The Ontology Open Repository (OOR) initiative is using the BioPortal 2.0 software as a basis for their first "NCBO-OOR" deployment to begin serving its diverse communities. This page serves as a launch point for understanding the NCBO-OOR architecture and getting started with customizing the code to advance OOR goals and objectives.	+	Welcome to the OOR Project! This developer's guide provides an introduction to the OOR architecture and steps (with examples) of how to customize server-side components. The NCBO-OOR project is a collaborative open source endeavor to meet the needs of the [http://ontolog.cim3.net/cgi-bin/wiki.pl?OOR Open Ontology Repository (OOR) Initiative.] The Ontology Open Repository (OOR) initiative is using the BioPortal 2.0 software as a basis for their first "NCBO-OOR" deployment to begin serving its diverse communities. This page serves as a launch point for understanding the NCBO-OOR architecture and getting started with customizing the code to advance OOR goals and objectives.

	* The [[NCBO-OOR Architecture]] page provides a general architecture and philosphy used in it's design and development. This page is geared for any reader who has a basic understanding of multi-tier software architecture.		* The [[NCBO-OOR Architecture]] page provides a general architecture and philosphy used in it's design and development. This page is geared for any reader who has a basic understanding of multi-tier software architecture.

← Older revision		Revision as of 19:11, 19 February 2009
Line 26:		Line 26:
	The NCBO-OOR developer collaboration will leverage practices that have worked successfully for various OOR community participants. The collaboration approach is still under construction.		The NCBO-OOR developer collaboration will leverage practices that have worked successfully for various OOR community participants. The collaboration approach is still under construction.

−	An example of ~~collaboration approaches~~ the OOR ~~can~~ leverage, the [[NCBO Developer Communications \| NCBO developer communications infrastructure]] has been established and driven by the NCBO Chief Software Architect which includes a NCBO quarterly developer conferences for which all NCBO partners are invited. Though all NCBO partners are welcome, the conference focuses primarily on how NCBO software can best serve the biomedical communities.	+	An example of practices that the OOR could leverage is the [[NCBO Developer Communications \| NCBO developer communications infrastructure]]. This has been established and driven by the NCBO Chief Software Architect which includes a NCBO quarterly developer conferences for which all NCBO partners are invited. Though all NCBO partners are welcome, the conference focuses primarily on how NCBO software can best serve the biomedical communities.

← Older revision		Revision as of 19:09, 19 February 2009
Line 24:		Line 24:

	=NCBO-OOR Developer Collaboration=		=NCBO-OOR Developer Collaboration=
−	The [[NCBO Developer Communications \| NCBO developer communications infrastructure]] has been established and driven by the NCBO Chief Software Architect which includes a NCBO quarterly developer conferences for which all NCBO partners are invited. Though all NCBO partners are welcome, the conference focuses primarily on how NCBO software can best serve the biomedical communities.	+	The NCBO-OOR developer collaboration will leverage practices that have worked successfully for various OOR community participants. The collaboration approach is still under construction.
		+
		+	An example of collaboration approaches the OOR can leverage, the [[NCBO Developer Communications \| NCBO developer communications infrastructure]] has been established and driven by the NCBO Chief Software Architect which includes a NCBO quarterly developer conferences for which all NCBO partners are invited. Though all NCBO partners are welcome, the conference focuses primarily on how NCBO software can best serve the biomedical communities.