Unique Ids - Revision history

Rob at 09:26, 17 December 2008

2008-12-17T09:26:29Z

← Older revision		Revision as of 09:26, 17 December 2008
Line 4:		Line 4:

	#Unique ids can be a maximum of ten (10) characters in length.		#Unique ids can be a maximum of ten (10) characters in length.
	#Unique ids may only contain the standard alphabetic characters (A-Z and a-z), numeric characters (0-9), and the underscore (~~‘_’~~).		#Unique ids may only contain the standard alphabetic characters (A-Z and a-z), numeric characters (0-9), and the underscore ('_').
			#Unique ids are '''case sensitive''' ("foo" is not the same as "Foo" is not the same as "FOO").
	#While it is technically legal for a unique id to start with a numeric character (0-9), it is generally NOT a good idea to do so. If a unique id begins with a numeric character, it will not be able to be used in most scripts, rules, and tag expressions (since starting with a numeric character causes Hero Lab to think the unique id is a numeric value).		#While it is technically legal for a unique id to start with a numeric character (0-9), it is generally NOT a good idea to do so. If a unique id begins with a numeric character, it will not be able to be used in most scripts, rules, and tag expressions (since starting with a numeric character causes Hero Lab to think the unique id is a numeric value).
	#All unique ids must be unique within a defined context. For example, it is not valid to have two different tag groups with the unique id ~~“mygroup”~~. However, it IS perfectly reasonable to have a tag group named ~~“mine”~~ and a rule set that is also named ~~“mine”~~, since they represent different contexts.		#All unique ids must be unique within a defined context. For example, it is not valid to have two different tag groups with the unique id "mygroup". However, it IS perfectly reasonable to have a tag group named "mine" and a rule set that is also named "mine", since they represent different contexts.

	{{note}}The notable exception to #3 above is for tags, where purely numeric ids are common (to represent ranges, levels, resource costs, etc.). Since tags are always referenced with their tag group, a purely numeric tag id incurs none of the liabilities mentioned above.		{{note}}The notable exception to #4 above is for tags, where purely numeric ids are common (to represent ranges, levels, resource costs, etc.). Since tags are always referenced with their tag group, a purely numeric tag id incurs none of the liabilities mentioned above.

Rob at 06:59, 22 November 2008

2008-11-22T06:59:51Z

← Older revision		Revision as of 06:59, 22 November 2008
Line 1:		Line 1:
	~~[[Category:Basic Concepts and Terminology]]~~
	{{context\|Basic Concepts and Terminology}}		{{context\|Basic Concepts and Terminology}}

Rob at 06:53, 22 November 2008

2008-11-22T06:53:48Z

← Older revision		Revision as of 06:53, 22 November 2008
Line 1:		Line 1:
	[[Category:Basic Concepts and Terminology]]		[[Category:Basic Concepts and Terminology]]
	~~[Context: [[Home~~\|~~HL Kit]] [[~~Basic Concepts and Terminology~~]]]~~		{{context\|Basic Concepts and Terminology}}
	~~{{context\|x\|y\|z~~}}

	Most objects within HL are assigned a unique identifier so that they can be easily referenced throughout the data files. For example, each thing needs to have a unique value. HL uses unique ids for naming objects. Unique ids must comply with a number of rules, as outlined below. These rules enable HL to achieve significant performance optimizations at run-time, so these restrictions are important.		Most objects within HL are assigned a unique identifier so that they can be easily referenced throughout the data files. For example, each thing needs to have a unique value. HL uses unique ids for naming objects. Unique ids must comply with a number of rules, as outlined below. These rules enable HL to achieve significant performance optimizations at run-time, so these restrictions are important.

Rob at 06:46, 22 November 2008

2008-11-22T06:46:11Z

← Older revision		Revision as of 06:46, 22 November 2008
Line 1:		Line 1:
	[[Category:Basic Concepts and Terminology]]		[[Category:Basic Concepts and Terminology]]
	[Context: [[Home\|HL Kit]] [[Basic Concepts and Terminology]]]		[Context: [[Home\|HL Kit]] [[Basic Concepts and Terminology]]]
	{{context\|~~xyz~~}}		{{context\|x\|y\|z}}

	Most objects within HL are assigned a unique identifier so that they can be easily referenced throughout the data files. For example, each thing needs to have a unique value. HL uses unique ids for naming objects. Unique ids must comply with a number of rules, as outlined below. These rules enable HL to achieve significant performance optimizations at run-time, so these restrictions are important.		Most objects within HL are assigned a unique identifier so that they can be easily referenced throughout the data files. For example, each thing needs to have a unique value. HL uses unique ids for naming objects. Unique ids must comply with a number of rules, as outlined below. These rules enable HL to achieve significant performance optimizations at run-time, so these restrictions are important.

Rob at 06:41, 22 November 2008

2008-11-22T06:41:00Z

← Older revision		Revision as of 06:41, 22 November 2008
Line 1:		Line 1:
	[[Category:Basic Concepts and Terminology]]		[[Category:Basic Concepts and Terminology]]
	[Context: [[Home\|HL Kit]] [[Basic Concepts and Terminology]]]		[Context: [[Home\|HL Kit]] [[Basic Concepts and Terminology]]]
	{{context:\|xyz}}		{{context\|xyz}}

	Most objects within HL are assigned a unique identifier so that they can be easily referenced throughout the data files. For example, each thing needs to have a unique value. HL uses unique ids for naming objects. Unique ids must comply with a number of rules, as outlined below. These rules enable HL to achieve significant performance optimizations at run-time, so these restrictions are important.		Most objects within HL are assigned a unique identifier so that they can be easily referenced throughout the data files. For example, each thing needs to have a unique value. HL uses unique ids for naming objects. Unique ids must comply with a number of rules, as outlined below. These rules enable HL to achieve significant performance optimizations at run-time, so these restrictions are important.

Rob at 06:39, 22 November 2008

2008-11-22T06:39:04Z

← Older revision		Revision as of 06:39, 22 November 2008
Line 1:		Line 1:
	[[Category:Basic Concepts and Terminology]]		[[Category:Basic Concepts and Terminology]]
	[Context: [[Home\|HL Kit]] [[Basic Concepts and Terminology]]]		[Context: [[Home\|HL Kit]] [[Basic Concepts and Terminology]]]
			{{context:\|xyz}}

	Most objects within HL are assigned a unique identifier so that they can be easily referenced throughout the data files. For example, each thing needs to have a unique value. HL uses unique ids for naming objects. Unique ids must comply with a number of rules, as outlined below. These rules enable HL to achieve significant performance optimizations at run-time, so these restrictions are important.		Most objects within HL are assigned a unique identifier so that they can be easily referenced throughout the data files. For example, each thing needs to have a unique value. HL uses unique ids for naming objects. Unique ids must comply with a number of rules, as outlined below. These rules enable HL to achieve significant performance optimizations at run-time, so these restrictions are important.

Rob at 13:56, 21 November 2008

2008-11-21T13:56:50Z

← Older revision		Revision as of 13:56, 21 November 2008
Line 9:		Line 9:
	#All unique ids must be unique within a defined context. For example, it is not valid to have two different tag groups with the unique id “mygroup”. However, it IS perfectly reasonable to have a tag group named “mine” and a rule set that is also named “mine”, since they represent different contexts.		#All unique ids must be unique within a defined context. For example, it is not valid to have two different tag groups with the unique id “mygroup”. However, it IS perfectly reasonable to have a tag group named “mine” and a rule set that is also named “mine”, since they represent different contexts.

	~~'''NOTE!'''~~ The notable exception to #3 above is for tags, where purely numeric ids are common (to represent ranges, levels, resource costs, etc.). Since tags are always referenced with their tag group, a purely numeric tag id incurs none of the liabilities mentioned above.		{{note}}The notable exception to #3 above is for tags, where purely numeric ids are common (to represent ranges, levels, resource costs, etc.). Since tags are always referenced with their tag group, a purely numeric tag id incurs none of the liabilities mentioned above.

Rob at 11:04, 15 November 2008

2008-11-15T11:04:28Z

← Older revision		Revision as of 11:04, 15 November 2008
Line 1:		Line 1:
	[[Category:Basic Concepts and Terminology]]		[[Category:Basic Concepts and Terminology]]
	[Context: [[Basic Concepts and Terminology]]]		[Context: [[Home\|HL Kit]] [[Basic Concepts and Terminology]]]

	Most objects within HL are assigned a unique identifier so that they can be easily referenced throughout the data files. For example, each thing needs to have a unique value. HL uses unique ids for naming objects. Unique ids must comply with a number of rules, as outlined below. These rules enable HL to achieve significant performance optimizations at run-time, so these restrictions are important.		Most objects within HL are assigned a unique identifier so that they can be easily referenced throughout the data files. For example, each thing needs to have a unique value. HL uses unique ids for naming objects. Unique ids must comply with a number of rules, as outlined below. These rules enable HL to achieve significant performance optimizations at run-time, so these restrictions are important.

Rob at 10:21, 15 November 2008

2008-11-15T10:21:06Z

← Older revision		Revision as of 10:21, 15 November 2008
Line 1:		Line 1:
	[[Category:Basic Concepts and Terminology]]		[[Category:Basic Concepts and Terminology]]
			[Context: [[Basic Concepts and Terminology]]]

	Most objects within HL are assigned a unique identifier so that they can be easily referenced throughout the data files. For example, each thing needs to have a unique value. HL uses unique ids for naming objects. Unique ids must comply with a number of rules, as outlined below. These rules enable HL to achieve significant performance optimizations at run-time, so these restrictions are important.		Most objects within HL are assigned a unique identifier so that they can be easily referenced throughout the data files. For example, each thing needs to have a unique value. HL uses unique ids for naming objects. Unique ids must comply with a number of rules, as outlined below. These rules enable HL to achieve significant performance optimizations at run-time, so these restrictions are important.

Rob: New page: Category:Basic Concepts and Terminology Most objects within HL are assigned a unique identifier so that they can be easily referenced throughout the data files. For example, each thing...

2008-11-15T10:09:13Z

New page: Category:Basic Concepts and Terminology Most objects within HL are assigned a unique identifier so that they can be easily referenced throughout the data files. For example, each thing...

New page

[[Category:Basic Concepts and Terminology]]
Most objects within HL are assigned a unique identifier so that they can be easily referenced throughout the data files. For example, each thing needs to have a unique value. HL uses unique ids for naming objects. Unique ids must comply with a number of rules, as outlined below. These rules enable HL to achieve significant performance optimizations at run-time, so these restrictions are important.

#Unique ids can be a maximum of ten (10) characters in length.
#Unique ids may only contain the standard alphabetic characters (A-Z and a-z), numeric characters (0-9), and the underscore (‘_’).
#While it is technically legal for a unique id to start with a numeric character (0-9), it is generally NOT a good idea to do so. If a unique id begins with a numeric character, it will not be able to be used in most scripts, rules, and tag expressions (since starting with a numeric character causes Hero Lab to think the unique id is a numeric value).
#All unique ids must be unique within a defined context. For example, it is not valid to have two different tag groups with the unique id “mygroup”. However, it IS perfectly reasonable to have a tag group named “mine” and a rule set that is also named “mine”, since they represent different contexts.

'''NOTE!''' The notable exception to #3 above is for tags, where purely numeric ids are common (to represent ranges, levels, resource costs, etc.). Since tags are always referenced with their tag group, a purely numeric tag id incurs none of the liabilities mentioned above.