Example 58 of the spec contains the following example for the Mention type:
{
"@context": "https://www.w3.org/ns/activitystreams",
"summary": "Mention of Joe by Carrie in her note",
"type": "Mention",
"href": "http://example.org/joe",
"name": "Joe"
}
However, the presence of "summary" in this example is conflicting with the rest of the document. The domain of the "summary" property type is only "Object", supported by the "Object" type listing "summary" as a property while "Link" does not. Since "Mention" extends "Link" and not "Object", it does not inherit the "summary" property. Thus, there is a contradiction between this example and the specification.
Examples 79 & 80 both have the following snippets:
However, the "width" and "height" properties both only have a domain of "Link". The "Image" type extends "Document" which extends "Object", none of which have neither the "width" nor "height" properties. So this is the same kind of conflict between specification and example as #1.
Please Indicate One:
Please Describe the Issue:
(I am splitting my email to the public-socialweb mailing list into separate issues, for background please see those emails).
This is ActivityStream vocabulary specific: https://www.w3.org/TR/activitystreams-vocabulary
However, the presence of "summary" in this example is conflicting with the rest of the document. The domain of the "summary" property type is only "Object", supported by the "Object" type listing "summary" as a property while "Link" does not. Since "Mention" extends "Link" and not "Object", it does not inherit the "summary" property. Thus, there is a contradiction between this example and the specification.
However, the "width" and "height" properties both only have a domain of "Link". The "Image" type extends "Document" which extends "Object", none of which have neither the "width" nor "height" properties. So this is the same kind of conflict between specification and example as #1.