Resource ID or Resource Id?

ID versus Id.

I see that Wikipedia redirects from Id to ID.

I hope we can settle this. I know it’s picky but we’re currently not consistent about this and we probably should be. I have to be consistent in the book and don’t know which to pick. (I’m referring strictly to documentation, not code.)

I like ID.

Quote from: rthrash at Mar 02, 2009, 02:02 AM

I like ID.

You may like it but all attributes are technically lowercase. So neither, it should be Resource "id", if you are talking about the class var/field/table column.

Quote from: OpenGeek at Mar 02, 2009, 08:32 AM

Quote from: rthrash at Mar 02, 2009, 02:02 AM

I like ID.

You may like it but all attributes are technically lowercase. So neither, it should be Resource "id", if you are talking about the class var/field/table column.

No argument there, and it will always be id in code examples. When discussiing the object in general, though, "id" just won’t work so it has to be Id or ID. You can’t start a sentence with "id" or use it in a heading.

Ryan’s preference is good enough for me.

What should be the suggested usage in snippet parameters?

Quote from: rthrash at Mar 02, 2009, 04:41 PM

What should be the suggested usage in snippet parameters?

You mean startId versus startID? Good question. It would be nice to have a recommendation for snippet developers.

Indeed. That gets confusing as all get out between different ones. I honestly like how ditto handled that one since it now allows for multiple starting docs: &parents=`1,2,3...`

For documentation I’d definitely put a vote in for ID. For snippet parameters, I like to stick to camel-casing of variables so I’d go with &startId.

Quote from: garryn at Mar 04, 2009, 04:05 AM

For documentation I’d definitely put a vote in for ID. For snippet parameters, I like to stick to camel-casing of variables so I’d go with &startId.

That makes perfect sense to me.