- From: Ivan Herman <ivan@w3.org>
- Date: Thu, 9 Feb 2012 10:47:47 +0100
- To: Shane P McCarron <shane@aptest.com>
- Cc: W3C RDFWA WG <public-rdfa-wg@w3.org>, James Leigh <james@leighnet.ca>
- Message-Id: <68656374-0C40-44C7-A81A-EB4A597B7E3A@w3.org>
Shane, James is correct in his remark. This is a purely editorial change, so I went ahead and changed the rdfa core working document (ie, Overview-src). I hope this is fine with you. James, thank you! Ivan Begin forwarded message: > From: James Leigh <james@3roundstones.com> > Subject: Hanging @property > Date: February 8, 2012 21:17:40 GMT+01:00 > To: Ivan Herman <ivan@w3.org> > > Hi Ivan, > > Apologies for sending this directly to you, but it seems like a quick > fix. > > Just noticed this and thought the wording could be better. This > paragraph below sounds like "One or more IRI objects are needed when > @property is present. The subject value of any nested statement will > cause triples to be generated if none of @href, @resource or @src are > present." - but that is wrong (@property cannot be used with hanging > relationships). > > http://www.w3.org/TR/2011/WD-rdfa-core-20111215/#iri-object-resolution > > One or more IRI objects are needed when @rel, @rev, or @property > is present. Each attribute will cause triples to be generated > when used with @href, @resource or @src, or with the subject > value of any nested statement if none of these attributes are > present. > > > I suggest pulling @property out of the above statement and clarifying > that present of @property does not necessarily produce IRI objects nor > does @property apply to nested statements. > > Regards, > James > > ---- Ivan Herman, W3C Semantic Web Activity Lead Home: http://www.w3.org/People/Ivan/ mobile: +31-641044153 FOAF: http://www.ivan-herman.net/foaf.rdf
Attachments
- application/pkcs7-signature attachment: smime.p7s
Received on Thursday, 9 February 2012 09:45:45 UTC