We are connecting a RFID reader and want when it reports a tag to tell if the tag is new (not previously reported - the device will track the tags in a database), or removed (no longer sensed) or an existing tag sensed. We could define separate percept address (RFIDReader.new, RFIDReader.removed, RFIDReader.existing) or use custom entryTypes (e.g. 10=New tag, 11=missing tag, 12=existing tag). I think using custom entryType fields would be a "cleaner" way to do this.
Comments? If we use the Percept entryType attribute, do they have to be numeric values? If so, is there a master database of these value so we can extend and add our own? Or can we define textual values (e.g. entryType="new | removed | existing")?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Maybe another option would be to specify a range of numeric values that the user could customize -- for example, anything in the range 100-199 is a 'custom' code that could be used for application-specific purposes?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
We are connecting a RFID reader and want when it reports a tag to tell if the tag is new (not previously reported - the device will track the tags in a database), or removed (no longer sensed) or an existing tag sensed. We could define separate percept address (RFIDReader.new, RFIDReader.removed, RFIDReader.existing) or use custom entryTypes (e.g. 10=New tag, 11=missing tag, 12=existing tag). I think using custom entryType fields would be a "cleaner" way to do this.
Comments? If we use the Percept entryType attribute, do they have to be numeric values? If so, is there a master database of these value so we can extend and add our own? Or can we define textual values (e.g. entryType="new | removed | existing")?
Maybe another option would be to specify a range of numeric values that the user could customize -- for example, anything in the range 100-199 is a 'custom' code that could be used for application-specific purposes?
I agree with the concept of using numeric values but defining a custom range. The major reason is ease of backwards compatibility.