Context Navigation

← Previous Change
Wiki History
Next Change →

TemplateRoleIds

Timestamp:: 10/18/10 21:27:58 (14 years ago)
Author:: dkanga (IP: 38.109.155.98)
Comment:: --

Legend:

: Unmodified
: Added
: Removed
: Modified

SigMmt/Templates/TemplateRoleIds

v1	v2
1		(Moved from an email thread)
	1	This post was moved from an email thread about the scope of uniqueness of IDS-ADI ("R number") IDs for template roles.
2	2
	3	----
3	4	Rahul,
4	5
5		We have loaded the proto and initial set templates here:
6		[[BR]]
7		http://facade.iringsandbox.org/TemporaryInitialSetTemplates/sparql
	6	We have loaded the proto and initial set templates here: [[BR]] http://facade.iringsandbox.org/TemporaryInitialSetTemplates/sparql
8	7
9		Please give it a try and let me know if you have any problems. I have
10		attached spreadsheets with the template and role IDs.
	8	Please give it a try and let me know if you have any problems. I have attached spreadsheets with the template and role IDs.
11	9
12	10	Darius
	11
13	12	----
14	13	Hi Darius,
15	14
16		I am continuing to look through this, still not finished. So far I have
17		one main question:
18		I see that there are things like "hasClass" "hasClass1" "hasClass2";
19		Shouldn't there be just one "hasClass" with just one R number?
	15	I am continuing to look through this, still not finished. So far I have one main question: I see that there are things like "hasClass" "hasClass1" "hasClass2"; Shouldn't there be just one "hasClass" with just one R number?
20	16
21		Thanks,
22		rahul
	17	Thanks, rahul
	18
23	19	----
24	20	Hi Rahul,
25	21
26		No, template roles with the same name are unique on their own, so if two
27		unrelated templates both have a role called hasClass then those two
28		roles will have different R number IDs. However specialized templates
29		have the same role IDs as their parents. This will let us easily
30		associate a template and other templates specialized from it, because
31		they will share the same role IDs, but they will not share role IDs with
32		any other templates.
	22	No, template roles with the same name are unique on their own, so if two unrelated templates both have a role called hasClass then those two roles will have different R number IDs. However specialized templates have the same role IDs as their parents. This will let us easily associate a template and other templates specialized from it, because they will share the same role IDs, but they will not share role IDs with any other templates.
33	23
34		Darius
	24	Darius
	25
35	26	----
36	27	Hi Darius,
37	28
38		>>No, template roles with the same name are unique on their own, so if
39		two unrelated templates both have a role called hasClass then those two
40		roles will have different R number IDs.
	29	> > No, template roles with the same name are unique on their own, so if
41	30
42		Can you please explain the assumption behind above statement bit more.
43		Is the assumption coming from part 7 or part 8? because I dont think
44		this is intended in part 7 and might cause issues while moving to JORD.
	31	two unrelated templates both have a role called hasClass then those two roles will have different R number IDs.
45	32
	33	Can you please explain the assumption behind above statement bit more. Is the assumption coming from part 7 or part 8? because I dont think this is intended in part 7 and might cause issues while moving to JORD.
46	34
47		thanks,
48		rahul
	35	thanks, rahul
	36
49	37	----
50	38	Hi Rahul,
51	39
52		I haven't seen anything about role IDs in Part 7 or 8. The Part 8 sample
53		OWL files use the role name as the ID. Certainly Parts 7 and 8 have
54		nothing about ids-adi (R number) IDs.
	40	I haven't seen anything about role IDs in Part 7 or 8. The Part 8 sample OWL files use the role name as the ID. Certainly Parts 7 and 8 have nothing about ids-adi (R number) IDs.
55	41
56		I remember some discussions with Julian about whether role IDs should be
57		unique or only unique in the context of a template, and the decision was
58		that they should be unique by themselves. I think this makes sense, and
59		it gives several advantages, such as the ability to change role metadata
60		without affecting other templates, and the ability for specialized and
61		non-specialized templates to interoperate as mentioned before. Do you
62		see any problems or disadvantages with this approach?
	42	I remember some discussions with Julian about whether role IDs should be unique or only unique in the context of a template, and the decision was that they should be unique by themselves. I think this makes sense, and it gives several advantages, such as the ability to change role metadata without affecting other templates, and the ability for specialized and non-specialized templates to interoperate as mentioned before. Do you see any problems or disadvantages with this approach?
63	43
64		Darius
	44	Darius
	45
65	46	----
66	47	Hi Darius,
67	48
68		Yes, there are issues. Let me try to explain.
69		First of all I agree with the statement :
	49	Yes, there are issues. Let me try to explain. First of all I agree with the statement :
70	50
71		>> I remember some discussions with Julian about whether role IDs should be
72		>> unique or only unique in the context of a template, and the decision was
73		>> that they should be unique by themselves.
	51	> > I remember some discussions with Julian about whether role IDs should be unique or only unique in the context of a template, and the decision was that they should be unique by themselves.
74	52
75		But unfortunately it is little off topic and if anything current implementation is contradicting it.
	53	But unfortunately it is little off topic and if anything current implementation is contradicting it.
76	54
77		e.g.
	55	e.g.
78	56
79	57	{{{
…	…
84	62	http://tpl.rdlfacade.org/data#R16697929282 hasClass
85	63	}}}
86
87	64	reasons :
88	65
89		1. Thought part 8 examples don't use R numbers they use same id similar to "#hasClass" when referring to this role in all the templates. (Verified for examples above). Since IDs are dumb, the only important fact remains that it is same in all the templates.
90		[[BR]]
91		2. Going back to Julian's statement above even a single id for hasClass is unique by itself. It is not dependent upon any specific template.
92		[[BR]]
93		3. All the templates which have role name "hasClass" are trying to convey same meaning at that "thing filling that role is at the class level as compared to thing filling the other role(s)" so each "hasClass" role need not have separate id. If the meaning changes then there should be a separate role all together and then off course separate id e.g. #hasRole1.
	66	1. Thought part 8 examples don't use R numbers they use same id similar to "#hasClass" when referring to this role in all the templates. (Verified for examples above). Since IDs are dumb, the only important fact remains that it is same in all the templates. [[BR]] 2. Going back to Julian's statement above even a single id for hasClass is unique by itself. It is not dependent upon any specific template. [[BR]] 3. All the templates which have role name "hasClass" are trying to convey same meaning at that "thing filling that role is at the class level as compared to thing filling the other role(s)" so each "hasClass" role need not have separate id. If the meaning changes then there should be a separate role all together and then off course separate id e.g. #hasRole1.
94	67
95		Thanks,
96		rahul
	68	Thanks, rahul