Re: [web-annotation] Requirements for Agents

I had already written a schema to check for presence of generator (and
 similar one for creator) that is perfectly happy with an empty object
 as value for generator. In part, the schema looks like (basically the
 value of moderator is either a string of format uri or an object, 
empty or otherwise, or an array comprised of these values:

            "properties": {"generator":  
              {"oneOf": [
                { "$ref": "id.json#/definitions/stringUri" },
                { "type": "object" },
                {
                    "type": "array",
                    "minItems": 1,
                    "items": 
                    { "oneOf": [
                        { "$ref": "id.json#/definitions/stringUri" },
                        { "type": "object" }
                      ]
                    }
                }
             ]
           }
          }

Separately I have schemas that check for single creator (a should) and
 for each property of agent that we allow in the model, but these are 
clearly indicated as optional -- either may or should. So I think the 
model is okay as is in terms of being able to validate and track 
implementation. And I tend to agree with Ivan that in this instance we
 do not need or want to dictate descriptions of agent beyond our 
existing shoulds and mays. A must is not needed here since it would be
 hard to pick the single Agent property we think essential, assuming 
as you say that it should not be id.

-- 
GitHub Notification of comment by tcole3
Please view or discuss this issue at 
https://github.com/w3c/web-annotation/issues/349#issuecomment-240436572
 using your GitHub account

Received on Wednesday, 17 August 2016 14:50:45 UTC