- From: Michael Brunnbauer <brunni@netestate.de>
- Date: Mon, 14 May 2012 13:22:58 +0200
- To: Michiel de Jong <michiel@unhosted.org>
- Cc: Danny Ayers <danny.ayers@gmail.com>, public-rww@w3.org
Hello Michiel, On Mon, May 14, 2012 at 12:20:04PM +0200, Michiel de Jong wrote: > i think Jeni's proposal is valid, and 303s and hash uri rule are not. I think a cleaner way would have been to introduce a content and a sense function for URLs and a way so specify which one should be applied in a statement to get the property argument. This way we would not have several properties where we really mean *one* property. But to specify which function should be applied requires additional elements which do not fit into the RDF abstract syntax. > > In the case of properties like dcterms:subject, we need four different > > properties. > > that was also my second thought. [...] > no. if a vocabulary has not already thought about which one of the 4 > options a certain property means, then it was broken. You just conceded that with dcterms:subject there are 4 valid options and not a single one. So you think the dcterms vocabulary is "broken" because it does not include the three variants of dcterms:subject that somehow relate to the content of a URL ? Would not the URL have to be a typed literal in this case ? Regards, Michael Brunnbauer -- ++ Michael Brunnbauer ++ netEstate GmbH ++ Geisenhausener Straße 11a ++ 81379 München ++ Tel +49 89 32 19 77 80 ++ Fax +49 89 32 19 77 89 ++ E-Mail brunni@netestate.de ++ http://www.netestate.de/ ++ ++ Sitz: München, HRB Nr.142452 (Handelsregister B München) ++ USt-IdNr. DE221033342 ++ Geschäftsführer: Michael Brunnbauer, Franz Brunnbauer ++ Prokurist: Dipl. Kfm. (Univ.) Markus Hendel
Received on Monday, 14 May 2012 11:23:28 UTC