Skip to contentSkip to conversation

CTF model.emf.uri precision

DISCUSSION Mathieu Desnoyers 3 participants 3 messages Sep 25, 2012 3 messages not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

#1 lore raw
Quoted 8 lines · * Matthew Khouzam ([email protected]) wrote:

Hi tracing paladins,
I was going over the most recent CTF specs. I am curious, at the line:
1176 "model.emf.uri = "string";" this looks like a reference to
something from eclipse modeling framework.
http://download.eclipse.org/modeling/emf/emf/javadoc/2.7.0/org/eclipse/emf/common/util/URI.html

Is this part of the CTF specification? Shouldn't this be called model.uri or model_uri to respect the naming convention?

if we only call it model.uri, and come up with other model URIs that we want to encode in the future (not emf-related), then we would be stucked, wouldn't we ?

What is the benefit of removing the "emf" part ?

Thanks,

Mathieu

Quoted 9 lines

I hope someone could clarify this.

Matthew

_______________________________________________
lttng-dev mailing list
[email protected]
http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

Signature · 4 lines
Mathieu Desnoyers
Operating System Efficiency R&D Consultant
EfficiOS Inc.
http://www.efficios.com

A message that is not in the archive (sent off-list or not yet received): 20120925022530.GA12625@Krystal

#3 lore raw
Quoted 7 lines · Mathieu Desnoyers
Quoted 6 lines · * Matthew Khouzam ([email protected]) wrote:

Hi tracing paladins,
I was going over the most recent CTF specs. I am curious, at the line:
1176 "model.emf.uri = "string";" this looks like a reference to
something from eclipse modeling framework.
http://download.eclipse.org/modeling/emf/emf/javadoc/2.7.0/org/eclipse/emf/common/util/URI.html

Quoted 8 lines
Quoted 2 lines

Is this part of the CTF specification? Shouldn't this be called model.uri or model_uri to respect the naming convention?

if we only call it model.uri, and come up with other model URIs that we want to encode in the future (not emf-related), then we would be stucked, wouldn't we ?

What is the benefit of removing the "emf" part ?

I don't see the benifit of having the "emf". From what I see, its just an URI, so there is no real link to that an EMF. We could put any kind of model there?!?.

Also, why not just having a generic way to add a constant string to the event?

Yannick

A message that is not in the archive (sent off-list or not yet received): [email protected]

#5 lore raw

A fun solution could be a map of key values where you can put everything:
like
<tsdl>
event{
eventNameherething :={
{"loglevel" , "1"},
{"model.emf.uri" , "www.thingy"},
{"drink.coca.cola.(tm)" , "pepsi"},
...
}
fields:=...
}</tsdl>

Quoted 31 lines · Yannick Brosseau
Quoted 7 lines · Mathieu Desnoyers
Quoted 6 lines · * Matthew Khouzam ([email protected]) wrote:

Hi tracing paladins,
I was going over the most recent CTF specs. I am curious, at the line:
1176 "model.emf.uri = "string";" this looks like a reference to
something from eclipse modeling framework.
http://download.eclipse.org/modeling/emf/emf/javadoc/2.7.0/org/eclipse/emf/common/util/URI.html

Quoted 8 lines
Quoted 2 lines

Is this part of the CTF specification? Shouldn't this be called model.uri or model_uri to respect the naming convention?

if we only call it model.uri, and come up with other model URIs that we want to encode in the future (not emf-related), then we would be stucked, wouldn't we ?

What is the benefit of removing the "emf" part ?

I don't see the benifit of having the "emf". From what I see, its just an URI, so there is no real link to that an EMF. We could put any kind of model there?!?.

Also, why not just having a generic way to add a constant string to the event?

Yannick

_______________________________________________
lttng-dev mailing list
[email protected]
http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev