# [09:59] <MikeSmith> Simon is basically suggesting that in cases of bad values for attributes that would be obsolete-but-conforming if they had different values, that we also report the same warning that we report if they were obsolete-but-conforming

# [13:54] <MikeSmith> not that I know much about database technologies anyway

# [14:05] <MikeSmith> hsivonen: about the script language attribute, the Assertions.java and ConformingButObsoleteWarner.java code now correctly handle all case of it on their own -- the assertions part generating an "The language attribute is obsolete" error if it's anything but "javascript", and the warnings part generating a "The language attribute is obsolete warning" if that value is "javascript"

# [18:49] <no_mind> I am going through the spec and thinking, is HTML5 going to have tags for input from devices other than keyboard and mouse ? Like can I input my webcam or audio directly without using flash ?

# [18:49] <Philip`> jarib: The ids in the other version are autogenerated and I guess they'd be a bit less stable

# [20:32] <no_mind> foolip, this is a nice idea, but I am looking at some other things too. Like using fingerprint recognition device to authenticate for web apps. In this case I need to send input from fingerprint scanner to webapp. Finger print scanner is like a camera

# [20:33] <no_mind> also, with microphone integration, we can have fields for audio input which can be used for sending voice messages

# [20:59] <foolip> no_mind: if you want a conservative answer on what belongs in HTML, this is a terrible place to ask. Personally I don't care either way, it's still a part of the web platform and what browsers implement.