JSON schema defining single use of elements from a set - json

Question

I using draft-04 to define JSON schema.
My original problem was something like i wanted to define schema for below structure
{
"config1" : [
{ <category-1> : {some Object which i know how to define schema} },
{ <category-2> : {some Object which i know how to define schema} }
],
"config2" : {some other structure}
}
here category-n is a category defined in n-element set containing categories.
I know a schema defines a static data structure hence we can't enumerate on keys (correct?) so as a work around, i need to have config1 as follows
"config1" : [
{ "categoryName" : "category-1"
"categoryPayload" : {some Object which i know how to define schema} },
{ "categoryName" : "category-2"
"categoryPayload" : {some Object which i know how to define schema} }
]
for each category definition, i know i can use like "enum": ["category-1", "category-1"] but the problem is, in the first json i was getting benefit of json recommendation of not using duplicate keys. Each category is unique and i dont want someone to use different categoryPayload for the same category. How can i restrict array elements of config-1 to just have 1 element per category (no duplicate category elements)
Edit-1
Taking example of my derived approach (using category as value instead of keys), suppose category-1, category-2 and category-3 are allowed categories. hence following json should pass the validation
{
"config-1": [
{
"categoryName": "category-1", //line-1
"categoryPayload": {
"key1": "value1",
"key2": "value2"
}
},
{
"categoryName": "category-2", //line-2
"categoryPayload": {
"key1": "value1",
"key3": "value3"
}
}
],
"config-2": "something"
}
If a replace line-1 with category-2 (both line-1 and 2 having same values), this should fail the validation. And obviously if i replace category-7 (not part of allowed enum) at line-1, it should also fail the validation.

Answer 1

Is schema for each category never be the same? You can't assert uniqueness of values of object but its uniqueness of schemas.
{
"type": "object",
"properties": {
"config1": {
"type": "array",
"items": {
"type": "object",
"patternProperties": {
"\\w+": {
"oneOf": [
{"type": "object", "properties": {"a": {}}, "additionalProperties": false},
{"type": "object", "properties": {"b": {}}, "additionalProperties": false}
]
}
},
"additionalProperties": false
}
}
}
}
Update:
This is an alternative way:
{
"type": "object",
"properties": {
"config1": {
"type": "array",
"items": [
{"type": "array", "items": {"type": "string"}, "uniqueItems": true},
{"type": "array", "items": {"type": "object"}, "uniqueItems": true},
]
}
}
}
This way you can have unique keys and values. And you zip two array in your application.
This is passed:
{
"config1" : [
["category-1", "category-2"],
[{"a": 1}, {"a": 2}]
]
}
This is failed:
{
"config1" : [
["category-1", "category-2"],
[{"a": 1}, {"a": 1}]
]
}