MNet Roadmap - Revision history

Dougiamas at 09:51, 7 October 2014

2014-10-07T09:51:00Z

← Older revision		Revision as of 09:51, 7 October 2014
Line 4:		Line 4:
	\|tracker = MDL-40905		\|tracker = MDL-40905
	\|discussion = [https://moodle.org/mod/forum/discuss.php?d=175158 here]		\|discussion = [https://moodle.org/mod/forum/discuss.php?d=175158 here]
			\|assignee = many
	}}		}}

Dougiamas at 09:50, 7 October 2014

2014-10-07T09:50:25Z

← Older revision		Revision as of 09:50, 7 October 2014
Line 1:		Line 1:
			{{Infobox Project
			\|name = Mnet Standards Roadmap 2014
			\|state = Early specification]
			\|tracker = MDL-40905
			\|discussion = [https://moodle.org/mod/forum/discuss.php?d=175158 here]
			}}



	Key architectural considerations up for further discussion are:		Key architectural considerations up for further discussion are:

Dougiamas: Adding rough notes from Piers from the Mnet meeting in Wellington, 1st October 2014

2014-10-07T09:43:36Z

Adding rough notes from Piers from the Mnet meeting in Wellington, 1st October 2014

← Older revision		Revision as of 09:43, 7 October 2014
Line 1:		Line 1:
	~~==Changes Penny wants to make~~ for ~~Portfolio API/~~further ~~Mahara Integration==~~		Key architectural considerations up for further discussion are:

	~~===Splitting~~ of ~~Application from Services===~~		* importing SimpleSAMLphp as a first class addition to Moodle and Mahara to make the process of configuration simpler
			* introduction of wizards and automations that hide the complexity of SSO integration configuration

	As mnet evolves and potentially other services are offered than sso and enrolment, and potentially as more applications are written that talk mnet (there was a drupal mnet project, for example), it makes sense to start splitting out what services are offered by each application. To this end, I propse adding a new table, application2service, which links application to service, and moves the url field from the application table. It would look like this:		===Common Tasks===

			* Deprecation roadmap - figure out the tasks, and milestones required to determine what releases will mark out the deprecations of the existing MNet functionality as the web services and SAML authentication replacement becomes available.
			* Standardise on REST + JSON

	~~{\| border="1" cellpadding="2" cellspacing="0"~~		The following task lists are divided by system, but this does not necessarily delineate responsibility.
	\|-
	~~\|'''Field'''~~
	~~\|'''Datatype'''~~
	~~\|'''Comment'''~~
	\|-
	~~\|id~~
	~~\|integer~~
	~~\|sequence~~
	\|-
	~~\|applicationid~~
	~~\|integer~~
	~~\|fk to mnet_application~~
	\|-
	~~\|serviceid~~
	~~\|integer~~
	~~\|fk to mnet_service~~
	\|-
	~~\|url~~
	~~\|char (255)~~
	\|this ~~is to replace application~~.~~sso_land_url (application.xmlrpc_server_url should still stay where it is)~~
	\|}

	~~I had originally thought about adding publishable and subscribeable fields to this table, but really I think this should be dictated by what the remote hosts offer. Not convinced on this point yet.~~		===Mahara Centred Tasks===

	~~===More sensible namespacing===~~		* Land the Web Services plugin in Mahara core
			* Include SimpleSAMLphp as first class library
			* Connection manager for client connections in web services - ssphp connection wizard, wizard for inter-Moodle/Mahara connections "just enter URL + Token"
			* Migrate MNet functionality to Web Services for Portfolio, account provisioning
			* Update Launch block for network servers

	~~Currently the xmlrpc functions are namespaced according to what file in~~ Moodle ~~their php equivalents are. EG:~~		===Moodle Centred Tasks===

	~~enrol/mnet/enrol.php/enrol_user \| enrol_user~~		* Include SimpleSAMLphp as first class library
			* Connection manager for client connections in web services - ssphp connection wizard, wizard for inter-Moodle/Mahara connections "just enter URL + Token"
	~~This was logical when it was just Moodle talking to other Moodles, but now it's really not. For the Mahara Portfolio plugin~~, Moodle ~~needs to call two functions in~~ Mahara~~, content_intent and content_ready. It's logical~~ to ~~namespace them like~~ portfolio~~/content_* but this breaks the current trend.~~		* Migrate MNet functionality to Web Services for mahara portfolio plugin, assignment plugin, account provisioning
			* Assignment plugin was originally proposed to be replaced with LTI based functionality, but a better approach has been suggested using a repository plugin.
	~~===Split between xmlrpc functions offered and xmlrpc functions available===~~		* Authentication sources separate from mdl_user table
			* Investigate community hubs and MNet use ?
	~~Currently~~, ~~Moodle doesn't differentiate between functions it offers and functions it might call. These are symmetrical~~, ~~because Moodle~~ was originally ~~just going~~ to ~~talk to other Moodles. However now~~, ~~oodle must realise that mnet functions exist that it might never want to implement, only call (and the other way around)~~. ~~Ideally this would be done by linking applications to services, and services to rpc (and namespacing correctly)~~		* Launch block replacement for MNet servers jump point

	~~==Changes Catalyst will be making to improve Moodle/Mahara SSO==~~
	~~Nigel todo~~

	~~==Changes Catalyst want to make longer term==~~
	~~Nigel/Peterb todo~~

	~~[[Category:~~MNet]]

Tsala: category edit

2010-02-18T20:17:53Z

category edit

← Older revision		Revision as of 20:17, 18 February 2010
Line 49:		Line 49:
	Nigel/Peterb todo		Nigel/Peterb todo

	[[Category:~~MNET~~]]		[[Category:MNet]]

Tsala: MNET Roadmap moved to MNet Roadmap

2010-02-18T20:16:13Z

MNET Roadmap moved to MNet Roadmap

← Older revision	Revision as of 20:16, 18 February 2010
(No difference)

Tsala: category

2008-09-09T09:26:24Z

TimHunt: MNET Roadmap moved to MNET Roadmap

2008-07-22T14:52:20Z

MNET Roadmap moved to MNET Roadmap

← Older revision		Revision as of 14:52, 22 July 2008
(No difference)

Mjollnir: /* Changes Catalyst want to make longer term= */

2008-07-22T14:45:55Z

Changes Catalyst want to make longer term=

← Older revision		Revision as of 14:45, 22 July 2008
Line 46:		Line 46:
	Nigel todo		Nigel todo

	==Changes Catalyst want to make longer term===		==Changes Catalyst want to make longer term==
	Nigel/Peterb todo		Nigel/Peterb todo

Mjollnir: /* Changes Catalyst will be making to improve Moodle/Mahara SSO= */

2008-07-22T14:45:17Z

Changes Catalyst will be making to improve Moodle/Mahara SSO=

← Older revision		Revision as of 14:45, 22 July 2008
Line 43:		Line 43:
	Currently, Moodle doesn't differentiate between functions it offers and functions it might call. These are symmetrical, because Moodle was originally just going to talk to other Moodles. However now, oodle must realise that mnet functions exist that it might never want to implement, only call (and the other way around). Ideally this would be done by linking applications to services, and services to rpc (and namespacing correctly)		Currently, Moodle doesn't differentiate between functions it offers and functions it might call. These are symmetrical, because Moodle was originally just going to talk to other Moodles. However now, oodle must realise that mnet functions exist that it might never want to implement, only call (and the other way around). Ideally this would be done by linking applications to services, and services to rpc (and namespacing correctly)

	==Changes Catalyst will be making to improve Moodle/Mahara SSO===		==Changes Catalyst will be making to improve Moodle/Mahara SSO==
	Nigel todo		Nigel todo

	==Changes Catalyst want to make longer term===		==Changes Catalyst want to make longer term===
	Nigel/Peterb todo		Nigel/Peterb todo

Mjollnir: /* Changes Penny wants to make for Portfolio API/further Mahara Integration */

2008-07-22T14:44:41Z

Changes Penny wants to make for Portfolio API/further Mahara Integration

← Older revision		Revision as of 14:44, 22 July 2008
Line 1:		Line 1:
	==Changes Penny wants to make for Portfolio API/further Mahara Integration==		==Changes Penny wants to make for Portfolio API/further Mahara Integration==

			===Splitting of Application from Services===

	As mnet evolves and potentially other services are offered than sso and enrolment, and potentially as more applications are written that talk mnet (there was a drupal mnet project, for example), it makes sense to start splitting out what services are offered by each application. To this end, I propse adding a new table, application2service, which links application to service, and moves the url field from the application table. It would look like this:		As mnet evolves and potentially other services are offered than sso and enrolment, and potentially as more applications are written that talk mnet (there was a drupal mnet project, for example), it makes sense to start splitting out what services are offered by each application. To this end, I propse adding a new table, application2service, which links application to service, and moves the url field from the application table. It would look like this:
Line 29:		Line 31:
	I had originally thought about adding publishable and subscribeable fields to this table, but really I think this should be dictated by what the remote hosts offer. Not convinced on this point yet.		I had originally thought about adding publishable and subscribeable fields to this table, but really I think this should be dictated by what the remote hosts offer. Not convinced on this point yet.

			===More sensible namespacing===

			Currently the xmlrpc functions are namespaced according to what file in Moodle their php equivalents are. EG:

			enrol/mnet/enrol.php/enrol_user \| enrol_user

			This was logical when it was just Moodle talking to other Moodles, but now it's really not. For the Mahara Portfolio plugin, Moodle needs to call two functions in Mahara, content_intent and content_ready. It's logical to namespace them like portfolio/content_* but this breaks the current trend.

			===Split between xmlrpc functions offered and xmlrpc functions available===

			Currently, Moodle doesn't differentiate between functions it offers and functions it might call. These are symmetrical, because Moodle was originally just going to talk to other Moodles. However now, oodle must realise that mnet functions exist that it might never want to implement, only call (and the other way around). Ideally this would be done by linking applications to services, and services to rpc (and namespacing correctly)

	==Changes Catalyst will be making to improve Moodle/Mahara SSO===		==Changes Catalyst will be making to improve Moodle/Mahara SSO===

← Older revision		Revision as of 09:26, 9 September 2008
Line 48:		Line 48:
	==Changes Catalyst want to make longer term==		==Changes Catalyst want to make longer term==
	Nigel/Peterb todo		Nigel/Peterb todo

			[[Category:MNET]]