- From: Michael Hopwood <michael@editeur.org>
- Date: Fri, 26 Oct 2012 16:45:52 +0100
- To: Dave Caroline <dave.thearchivist@gmail.com>
- CC: "Fegen, Neil" <N.Fegen@hw.ac.uk>, "public-vocabs@w3.org" <public-vocabs@w3.org>, Nicholas Shanks <nickshanks@nickshanks.com>, "Dan Brickley" <danbri@danbri.org>, "Sandhaus, Evan" <sandhes@nytimes.com>, "Martin Hepp" <martin.hepp@ebusiness-unibw.org>
Dave, That's true - precisely what's complex here is that there are actually at least 2 "somethings" being described; publication of the announcement of whatever, and the particular "whatever" which in this case may be what is legally an "offer" with its own variables attached. C.f. the complexity even of "publication date" and similar in the ONIX code lists (http://www.editeur.org/ONIX/book/codelists/current.html - see lists 163, 155)... -----Original Message----- From: Dave Caroline [mailto:dave.thearchivist@gmail.com] Sent: 26 October 2012 16:41 To: public-vocabs@w3.org Subject: Re: Proposal to add dateExpires to JobPosting On Fri, Oct 26, 2012 at 4:30 PM, Michael Hopwood <michael@editeur.org> wrote: > In a sense it doesn't matter what the property name is; it could be > "publishedDate" and "expiryDate". That would mean about the same in > all versions of English (context and connotation notwithstanding ;) You can publish something(publishDate) a length of time before something is valid(starts from), open (validThrough a period), ends(close date) Dave Caroline
Received on Friday, 26 October 2012 15:46:27 UTC