[oslc-Metrics] What is URI of the dimension member undefined in the specification.

KASAI Masaki mogemoge at gmail.com
Thu Feb 14 10:59:41 EST 2013


Ryman,

> In the absence of a standard set of date URIs, you can maintain a set for 
> your company. For example, to represent the elapsed day 2013-02-13:

Thank you for your answer. OK, I understand. So I will think those by original URIs.

> May I ask how you plan to use this vocabulary?

I am investigating whether our measurement tool should provide OSLC-EM
(ems:Measurement, ems:Measure and ems:FactTable)  interface. 

Regards, Kasai

On 2013/02/14, at 1:52, Arthur Ryman <ryman at ca.ibm.com> wrote:

> Masaki,
> 
> Thanks for your note. May I ask how you plan to use this vocabulary? We 
> are interested in getting feedback from adopters so we can finalize it.
> 
> To answer your question, some dimensions cannot have a finite, 
> standardized list of members. The best we can do is define the grain size. 
> It is then up to the application to use whatever members are appropriate.
> 
> For example, consider grain:Task which is used in the work breakdown 
> dimension dimension:Wbs. The members of this dimension would the actual 
> tasks you perform in a project. This is a different list for every 
> project. If you are using the OSLC Change Management specification to 
> describe tasks, then the members of the dimension would be the URIs of the 
> actual oslc_cm:ChangeRequest resources.
> 
> Similarly, grain:Feature is used in dimension:Product. The members would 
> be URIs of actual features as definition in some product definition 
> application.
> 
> The situation for dimension:Time is a little different since we all use 
> the same calendar. Therefore it should be possible to use a standard set 
> of URIs to identify actual days, weeks, months, etc. I remember seeing an 
> experimental website (from someone at Talis?) that provided URIs for 
> dates. However, I can't locate it anymore.
> 
> In the absence of a standard set of date URIs, you can maintain a set for 
> your company. For example, to represent the elapsed day 2013-02-13:
> 
> http://mycompany.com/id/elapsed-day/2013-02-13
> 
> You could set up a server to return information about these URIs, e.g. 
> using the iCalendar RDF vocabulary.
> 
> Regards, 
> ___________________________________________________________________________ 
> 
> Arthur Ryman 
> 
> DE, Chief Architect, Reporting &
> Portfolio and Strategy Management
> IBM Software, Rational 
> 
> Toronto Lab | +1-905-413-3077 (office) | +1-416-939-5063 (mobile) 
> 
> 
> 
> 
> 
> From:   Masaki Kasai <mogemoge at gmail.com>
> To:     oslc-metrics at open-services.net, 
> Date:   02/13/2013 03:32 AM
> Subject:        [oslc-Metrics] What is URI of the dimension member 
> undefined in the        specification.
> Sent by:        "Oslc-Metrics" <oslc-metrics-bounces at open-services.net>
> 
> 
> 
> Hi.
> 
> There is a question for EMS1.0 REST API Standard URI.
> http://open-services.net/wiki/estimation-and-measurement/EMS-1.0-REST-API-Standard-URIs/
> 
> 
> What is URI of the dimension member for the grains of following list .
> 
>  grain:CalendarDay
>  grain:CalendarWeek
>  grain:CalendarMonth
>  grain:CalendarQuarter
>  grain:CalendarHalf
>  grain:CalendarYear
>  grain:ElapsedDay
>  grain:ElapsedWeek
>  grain:ElapsedMonth
>  grain:ElapsedQuarter
>  grain:ElapsedHalf
>  grain:ElapsedYear
>  grain:Iteration
>  grain:Activity
>  grain:Task
>  grain:WaterfallActivity
>  grain:System
>  grain:Subsystem
>  grain:Component
>  grain:Feature
>  grain:ProgrammingLanguageFamily
>  grain:Department
>  grain:Team
>  grain:Continent
>  grain:Country
>  grain:City
>  grain:Site
> 
> There are the dimension members of "grain:Role", "grain:DoD_Phase" and
> "grain:RUP_Phase" in the specification but there are not the
> dimension members of the above list.
> 
> -----
> mogemoge at gmail.com
> 
> _______________________________________________
> Oslc-Metrics mailing list
> Oslc-Metrics at open-services.net
> http://open-services.net/mailman/listinfo/oslc-metrics_open-services.net
> 
> 
> 





More information about the Oslc-Metrics mailing list