Yes :)
Rob
On Mon, Dec 15, 2014 at 10:32 AM, Ivan Herman <ivan@w3.org> wrote:
>
> Just for my understanding, before I call it a day...
>
> > On 15 Dec 2014, at 17:27 , Robert Sanderson <azaroth42@gmail.com> wrote:
> >
>
> <skip/>
> >
> > I would propose oa:bodyValue for the string (json-ld key "bodyValue")
> and require oa:hasBody / "body" to be always a resource.
> >
> > It still allows for an annotation of the form:
> >
> > {
> > "@type": "oa:Annotation",
> > "bodyValue": {"@value": "abcd", "@language":"en"},
> > "body": {"value": "efgh", "language": "en"},
> > "target": "http://example.org/"
> > }
> >
>
> But that would also allow to say
>
> {
> "bodyValue": "abcd",
> }
>
> right? Model wise, that is the same as using xsd:string. If so, I think
> this is the right way to go.
>
> Ivan
>
>
> ----
> Ivan Herman, W3C
> Digital Publishing Activity Lead
> Home: http://www.w3.org/People/Ivan/
> mobile: +31-641044153
> ORCID ID: http://orcid.org/0000-0003-0782-2704
>
>
>
>
>
--
Rob Sanderson
Information Standards Advocate
Digital Library Systems and Services
Stanford, CA 94305
Received on Monday, 15 December 2014 18:47:37 UTC