Looking for work
Independent Developer of Advanced Software Technology, specializing in Software Agent Technology
There has been lots of chattering about "digital identity", and we certainly need improvements in how identification is performed on computer networks, but in my view such efforts are at least a bit misguided since you can't get very far with digital systems before you run into the wall of having to interface with real-world systems, such as credit cards, bank accounts, residential addresses, social security numbers, etc.
We need a true "universal identity" conceptual model that integrates both the digital world and the real world. A good starting point would be a robust problem statement, but there appears to be little interest in such an effort, at least at this time.
Maybe we need to stumble a few more times with "digital identity" (scandals, terrorism, theft, etc.) before people finally recognize that we need the kind of rock-solid foundation principles that only a robust problem statement can provide.
-- Jack Krupansky
The drafts explain how to express classification schemes, thesauruses, subject heading lists, taxonomies, terminologies, glossaries and other types of controlled vocabulary in RDF.
I'm struggling with how to treat location relative to identity. Frequently, location is simply an attribute or characteristic associated with an entity or identity, such as a product or service being delivered to a location on behalf of an entity with an identity. But, there are lots of situations where a product or service can be delivered to a location without any need to refer to the identity of the entity (or entities) that might be associated with that location. The location can be thought of as having an anonymous associated entity (e.g., "Resident" or "Family residing at" or "Computer connected to IP address port"), but the question remains whether we need a pseudo-entity and pseudo-identity, or whether the location itself can be thought of as an entity with an identity that directly parallels the location itself.
<DIV>I'm struggling with how to treat location relative to identity. Frequently, location is simply an attribute or characteristic associated with an entity or identity, such as a product or service being delivered to a location on behalf of an entity with an identity. But, there are lots of situations where a product or service can be delivered to a location without any need to refer to the identity of the entity (or entities) that might be associated with that location. The location can be thought of as having an anonymous associated entity (e.g., "Resident" or "Family residing at" or "Computer connected to IP address port"), but the question remains whether we need a pseudo-entity and pseudo-identity, or whether the location itself can be thought of as an entity with an identity that directly parallels the location itself.</DIV> <DIV> </DIV> <DIV>The significance of the similarity or distinction between location and identity and entity is itself not obvious. One intriguing possibility is to enable a form of privacy based on location rather than entity identity.</DIV> <DIV> </DIV> <DIV>There are of course governmental, law enforcement, and national security issues that arise related to any separation of entities, identities, and locations. That does not mean that the concepts need to be tightly integrated, but does at least suggest some form of linkage or coupling and even tracking.</DIV> <DIV> </DIV> <DIV>The first question to be addressed is whether location is a "first-class concept" at the level of entity and identity.</DIV> <DIV> </DIV> <DIV>-- <A href="mailto:Jack@BaseTechnology.com">Jack Krupansky</A></DIV>