<feed xmlns="http://www.w3.org/2005/Atom" xmlns:foaf="http://xmlns.com/foaf/0.1/"><title>norman.walsh.name: Comments on /2005/12/12/vcard</title><link rel="alternate" type="text/html" href="http://norman.walsh.name/2005/12/12/vcard"/><id>http://norman.walsh.name/2005/12/12/vcard/comments.atom</id><updated>2012-02-13T06:16:53.118458Z</updated><entry><title>Comment 1 on /2005/12/12/vcard</title><link rel="alternate" type="text/html" href="http://norman.walsh.name/2005/12/12/vcard#comment0001"/><id>http://norman.walsh.name/2010/09/25/oauth#comment0001</id><published>2005-12-13T08:57:11Z</published><updated>2005-12-13T08:57:11Z</updated><author><name>Benjamin Nowack</name><foaf:mbox_sha1sum>da39a3ee5e6b4b0d3255bfef95601890afd80709</foaf:mbox_sha1sum></author><content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">
    <p>Heyup Norm,
there are rdfs:subClassOfs + property restrictions associated with properties instead of classes.</p>
  </div></content></entry><entry><title>Comment 2 on /2005/12/12/vcard</title><link rel="alternate" type="text/html" href="http://norman.walsh.name/2005/12/12/vcard#comment0002"/><id>http://norman.walsh.name/2010/09/25/oauth#comment0002</id><published>2005-12-13T10:35:02Z</published><updated>2005-12-13T10:35:02Z</updated><author><name>Susan</name><foaf:mbox_sha1sum>da39a3ee5e6b4b0d3255bfef95601890afd80709</foaf:mbox_sha1sum></author><content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">
    <p>Really useful, thanks.</p>
  </div></content></entry><entry><title>Comment 3 on /2005/12/12/vcard</title><link rel="alternate" type="text/html" href="http://norman.walsh.name/2005/12/12/vcard#comment0003"/><id>http://norman.walsh.name/2010/09/25/oauth#comment0003</id><published>2005-12-13T11:20:26Z</published><updated>2005-12-13T11:20:26Z</updated><author><name>Norman Walsh</name><foaf:mbox_sha1sum>da39a3ee5e6b4b0d3255bfef95601890afd80709</foaf:mbox_sha1sum></author><content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">
    <p>*Blush* Thank you, Benjamin. I knew I was rushing. Fixed.</p>
  </div></content></entry><entry><title>Comment 4 on /2005/12/12/vcard</title><link rel="alternate" type="text/html" href="http://norman.walsh.name/2005/12/12/vcard#comment0004"/><id>http://norman.walsh.name/2010/09/25/oauth#comment0004</id><published>2005-12-13T22:23:48Z</published><updated>2005-12-13T22:23:48Z</updated><author><name>Dan Connolly</name><foaf:mbox_sha1sum>da39a3ee5e6b4b0d3255bfef95601890afd80709</foaf:mbox_sha1sum></author><content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">
    <p>"1"^^xs:nonNegativeInteger is a mouthful; in N3/turtle, you can just write 1.</p>
  </div></content></entry><entry><title>Comment 5 on /2005/12/12/vcard</title><link rel="alternate" type="text/html" href="http://norman.walsh.name/2005/12/12/vcard#comment0005"/><id>http://norman.walsh.name/2010/09/25/oauth#comment0005</id><published>2005-12-14T12:59:34Z</published><updated>2005-12-14T12:59:34Z</updated><author><name>Reto</name><foaf:mbox_sha1sum>da39a3ee5e6b4b0d3255bfef95601890afd80709</foaf:mbox_sha1sum></author><content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">
    <p>Hi Norm, not sure anout the cardinality on v:rev. What happens whan a vcard changes (say you add a v:sound), does it gets a new uid and it becomes a new and distinct vcard-resource, or does it keep the uid and get's the v:rev replaced which makes the new graph a contradiction to the previous one? I think the easiest would be to allow multiple v:rev.</p>
  </div></content></entry><entry><title>Comment 6 on /2005/12/12/vcard</title><link rel="alternate" type="text/html" href="http://norman.walsh.name/2005/12/12/vcard#comment0006"/><id>http://norman.walsh.name/2010/09/25/oauth#comment0006</id><published>2005-12-14T13:13:22Z</published><updated>2005-12-14T13:13:22Z</updated><author><name>Norman Walsh</name><foaf:mbox_sha1sum>da39a3ee5e6b4b0d3255bfef95601890afd80709</foaf:mbox_sha1sum></author><content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">
    <p>Yeah, I don't know about the cardinality of v:rev either. My thinking was: if tracking revisions is important enough to you that you've bothered to put a v:rev property on your objects, you probably want to keep them distinct somehow. Once you find a v:VCard with two v:rev properties, you can be sure you've got no way to reconstruct either revision from the collection of properties on that v:VCard.
</p>
    <p>
But it's probably still a bad idea to impose the cardinality restriction, I suppose.</p>
  </div></content></entry><entry><title>Comment 7 on /2005/12/12/vcard</title><link rel="alternate" type="text/html" href="http://norman.walsh.name/2005/12/12/vcard#comment0007"/><id>http://norman.walsh.name/2010/09/25/oauth#comment0007</id><published>2005-12-16T10:29:07Z</published><updated>2005-12-16T10:29:07Z</updated><author><name>Dave Pawson</name><foaf:mbox_sha1sum>da39a3ee5e6b4b0d3255bfef95601890afd80709</foaf:mbox_sha1sum></author><content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">
    <p>Could you provide a couple of instances please Norm,
one form or another; fictitious or otherwise - it would help
in comprehension for those trailing?
</p>
    <p>
TIA DaveP</p>
  </div></content></entry></feed>

