Controls proposal

gistfile1.txt

editresource : {
	method : "PUT",
	action : "/someaction",
	encoding: "x-form-www-encoding"
	properties : {
		"username" : "Current Username",
		"email" : "current@user.com",
		"etag" : "123j123j1llkj31ljflkjsdlkj32lkjlkjf",
		"things" : [1, 2]
	},
	schema : {
		"username" : {
			type : "Text",
			validators : [
				required : true,
				pattern : /[A-Za-z0-9\s]/
			]
		},

		"email" : {
			type : "Email",
			validators : [
				required : false
			]
		},
		"etag" : {
			type : "Hidden",
			validators : [
				required : true,
				pattern : /[A-Za-z0-9\s]/
			]
		},
		"things" : {
			type : "SelectMany",
			validators : [
				required: true
			],
			options : [
				{
					value : 1,
					description : "Option one"
				},
				{
					value : 2,
					description : "Option two"
				},
				{
					value : 3,
					description : "Option three"
				}
			]
			/*
			// or this could actually be...
			options : [1, 2, 3]
			// which would just generate <option value="1">1</option>
			*/
		}		
	},
	enum : ["username", "email", "things", "etag"]
}

Hi.

I'm currently looking into adding actions/forms to my HAL API and was wondering whether this solution has evolved since you posted it and if you've got any insights after using it in production.

I'm also thinking I'll use JSON Schema to describe options and payloads so I can reuse existing tools to generate and validate the schemas.