Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

Hi,

I’d like to give another use case today. I call it “The runaway dog”. This use case might be controversial because it’s about object ID’s that are not direct connected to the internet.

Intro

Today pets/animals are often tagged somehow. In Germany for example you can bring an RFID(?) tag under the skin of your cat or dog. The tag is registered at a private company (e.g. tasso.net)

When the pet runs away and is found by someone it can be identified and brought back to its owner.

The use case is not new and there are different solutions running already.

But the idea is to re-use the tag also for plenty of other services if the owner agrees on. Government could use the tag for checking whether the pet has vaccination or whether the tax was paid.

You can imagine a GEO fencing services for example or a kitty door: It just opens when the right cat wants to come in.

Do you want to put another Chip inside your pet for every service? No instead we should reuse the first one.

For re using the chip there are several side conditions:

Authorization / Access control

The owner needs to decide and technology to enforce who (which service) is able to use the chip of my cat? There might be many attributes / information linked to the chip (not necessarily stored on it). We need access control to this information.

Mapping / Addressing

If you have a web-service running and you want to deal with pet RFID chips your need a mapping.

If you want to check the vaccination you take the number and ask a mapping/discovery service for the location of the database that knows more about it.

  • No labels