Hey Danny,
I *think* there might be a simpler way to take any particular combination of metadata, and keeping this and any other associated data under our own control such that giving this data out to any particular person remains our own choice, provide a way for anybody to associate any type of tag they might prefer to this information.
http://www.oreillynet.com/xml/blog/2006/04/mapping_data_between_domains_a.html
While the example used is obviously flawed -- would be a little too easy for someone to simply purchase the information contained in the database of the USPS, or any other particular countries postal system, and then map this data to the MD5 checksum to then query any public indexing service to gain access to the metadata associated with whomever happens to claim that particular address -- it seems to me that through a combination of various pieces of semantic information specified for a given tangible item (person, place, thing) you can then use OWL to associate the MD5 or SHA1 checksum with whatever your current URI happens to be,
2609f82f87ad8372c6863e8df8d9e0c3
owl:sameAs https://my-current-uri.info/access?2609f82f87ad8372c6863e8df8d9e0c3
maintaining complete control of that information, while at the same time allowing any public indexing service the ability to associate any metadata that is specified when the MD5 or SHA1 is originally registered with their system. In other words, making it impossible for someone to associate any particular checksum value with a URI and metadata in which they don't currently maintain some level of control over. When someone searches for a particular set of information, and decides "I'm pretty sure thats the person, place, or thing I am looking for" they can then send a query to this URI:
https://my-current-uri.info/access/2609f82f87ad8372c6863e8df8d9e0c3?https://requestors-current-uri/aboutme/metadata
which I can then use my system software to determine if this is someone in whom I want to share the associated information with. What kind of data would be needed for a system to make this determination is an obvious piece to this that is necessary to gain the benefits of a trust-based system that doesn't apply too much burden such that gaining the trust to access a set of information becomes a long and detailed process that no one will be willing to put up with from a large scale perspective, but this is a separate topic, therefore seperate conversation.
Thoughts? (note: I am going to add most of this comment as an update to the bottom of the above post, so if you have comments, feel free to leave them there if you would prefer)@en
I *think* there might be a simpler way to take any particular combination of metadata, and keeping this and any other associated data under our own control such that giving this data out to any particular person remains our own choice, provide a way for anybody to associate any type of tag they might prefer to this information.
http://www.oreillynet.com/xml/blog/2006/04/mapping_data_between_domains_a.html
While the example used is obviously flawed -- would be a little too easy for someone to simply purchase the information contained in the database of the USPS, or any other particular countries postal system, and then map this data to the MD5 checksum to then query any public indexing service to gain access to the metadata associated with whomever happens to claim that particular address -- it seems to me that through a combination of various pieces of semantic information specified for a given tangible item (person, place, thing) you can then use OWL to associate the MD5 or SHA1 checksum with whatever your current URI happens to be,
2609f82f87ad8372c6863e8df8d9e0c3
owl:sameAs https://my-current-uri.info/access?2609f82f87ad8372c6863e8df8d9e0c3
maintaining complete control of that information, while at the same time allowing any public indexing service the ability to associate any metadata that is specified when the MD5 or SHA1 is originally registered with their system. In other words, making it impossible for someone to associate any particular checksum value with a URI and metadata in which they don't currently maintain some level of control over. When someone searches for a particular set of information, and decides "I'm pretty sure thats the person, place, or thing I am looking for" they can then send a query to this URI:
https://my-current-uri.info/access/2609f82f87ad8372c6863e8df8d9e0c3?https://requestors-current-uri/aboutme/metadata
which I can then use my system software to determine if this is someone in whom I want to share the associated information with. What kind of data would be needed for a system to make this determination is an obvious piece to this that is necessary to gain the benefits of a trust-based system that doesn't apply too much burden such that gaining the trust to access a set of information becomes a long and detailed process that no one will be willing to put up with from a large scale perspective, but this is a separate topic, therefore seperate conversation.
Thoughts? (note: I am going to add most of this comment as an update to the bottom of the above post, so if you have comments, feel free to leave them there if you would prefer)@en
FOAF Profile
Feed
Google Plus
Twitter
Facebook
LinkedIn
Flickr
YouTube
slideshare
del.icio.us
GoodReads