http://mrtopf.de/blog/data-portability/xrds-and-its-service-types-technical/ Geschreibsel von Christian Scholz Mon, 23 Jan 2012 08:52:26 +0000 hourly 1 http://wordpress.org/?v=3.2.1 http://mrtopf.de/blog/data-portability/xrds-and-its-service-types-technical/#comment-821 Christian Scholz Mon, 12 May 2008 23:29:57 +0000 http://mrtopf.de/blog/en/xrds-and-its-service-types-technical/#comment-821 pfefferle, xrdstype.net is only meant for those without an already existing URI. It's not about duplicating, more about a place to reference if you need an URI but there it none (yet). pfefferle, xrdstype.net is only meant for those without an already existing URI. It's not about duplicating, more about a place to reference if you need an URI but there it none (yet).

]]> http://mrtopf.de/blog/data-portability/xrds-and-its-service-types-technical/#comment-820 XRDSType.net - Type URIs für XRDS-Simple at notizBlog - a private weblog written by Matthias Pfefferle Mon, 05 May 2008 19:03:51 +0000 http://mrtopf.de/blog/en/xrds-and-its-service-types-technical/#comment-820 [...] Mr. Topf) « XRDS-Simple, eine [...] [...] Mr. Topf) « XRDS-Simple, eine [...]

]]> http://mrtopf.de/blog/data-portability/xrds-and-its-service-types-technical/#comment-819 pfefferle Mon, 05 May 2008 08:23:41 +0000 http://mrtopf.de/blog/en/xrds-and-its-service-types-technical/#comment-819 XRDSType.net is a nice idea for types without any profile-uri, but it makes parsing more complicated for those with a profile- and xrdstype-uri because the parser have to use both or even some more... the hCard (for example <a href="http://microformats.org/wiki/profile-uris)" rel="nofollow">http://microformats.org/wiki/profile-uris)</a> for example will have <a href="http://www.w3.org/2006/03/hcard" rel="nofollow">http://www.w3.org/2006/03/hcard</a> , <a href="http://purl.org/uF/hCard/1.0/" rel="nofollow">http://purl.org/uF/hCard/1.0/</a> and perhaps <a href="http://xrdstype.net/microformats/hCard" rel="nofollow">http://xrdstype.net/microformats/hCard</a> XRDSType.net is a nice idea for types without any profile-uri, but it makes parsing more complicated for those with a profile- and xrdstype-uri because the parser have to use both or even some more… the hCard (for example http://microformats.org/wiki/profile-uris) for example will have http://www.w3.org/2006/03/hcard , http://purl.org/uF/hCard/1.0/ and perhaps http://xrdstype.net/microformats/hCard

]]>