OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

wsdm message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [MUWS] Identity


Title: Message
Hi all,
 
I created a template for MUWS 0.5 and filled in the "identity" part based on our conf call last year. For your review, below is what I put in there.
 
Regards,
 
William
 
 

5        Manageability capabilities

5.1 Identity

 

The goal of identity is to establish whether two entities are the same. In order to enable this

process, MUWS defines the following identity-related management capabilities:

5.1.1 Properties

Property Name

Type

Required (Y/N)

Mutable (Y/N)

ResourceID

xsd:anyURI

Y

N

Name

xsd:string

N

Y

Version

xsd:string

N

Y

 

<ednote>Do we need to include a "mutable" attribute on the properties? Need to check with the group.</ednote>

5.1.1.1 ResourceID

ResourceID is an opaque identifier of the resource managed through the manageability endpoint. A manageability endpoint MUST create the ResourceID URI in a way that ensures that the ResourceID is unique to the resource managed through the manageability endpoint. Furthermore, a given ResourceID MUST NOT be reused by any manageability endpoint for another resource even after the resource it was attached to has stopped existing. In the general case it is not possible to guarantee that different manageability endpoints attached to the same resource will return the same ResourceID. Nevertheless, there are cases when this might be possible, such as when the ResourceID can be retrieved from the resource by the manageability endpoint or when an application of MUWS to a given domain specifies a method to build the ResourceID based on characteristics of the resources in that domain. In such cases, a manageability provider SHOULD use the ResourceID that is suggested by the characteristics of the resource to identify the resource. Furthermore, a manageability provider that exposes several manageability endpoints for the same resource SHOULD use the same ResourceID for all the manageability endpoints.

Manageability endpoints might go down at times and cannot always be expected to persist the ResourceID across power cycles of the manageability endpoint. Nevertheless, when possible a manageability endpoint SHOULD return the same ResourceID during the entire lifetime of the manageability endpoint.

Since there is no guarantee that the same ResourceID is provided across all manageability endpoints for a given resource and at all points in time, a manageability consumer MUST NOT assume that two manageability endpoints represent two different resources solely because the ResourceID is different. On the other hand, if the ResourceIDs are equal then the consumer can assume that the two manageability endpoints represent the same resource.

Since the ResourceID is defined as opaque, this specification does not allow the consumer to infer any characteristic of the resource by examining the ResourceID, other than comparing the ResourceID to another ResourceID as one way to establish oneness. Note that this specification does not define equivalence of URIs and the consumer should decide which level of the comparison ladder defined in section 6 of [RFC2396bis] is appropriate to use for this comparison.

5.1.1.2 Name

Name is a string containing a descriptive name for the resource being managed. The Name is intended for human consumption.

5.1.1.3 Version

Version is a string representing the version of the resource being managed. MUWS doesn’t specify how this string is constructed. This can be specified by domain-specific specifications that use MUWS.

5.1.2 Operations

No operation defined.

5.1.3 Events

No event defined.



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]