[glue-wg] [rm-wg] reminder: Thursday phone conference

[Donal K. Fellows]

Fisher, SM (Steve) wrote:
> - It was mentioned in Seattle that AdminDomain.distributed was hard to
> define and of no value and so should be dropped
> 
> - It was also mentioned in Seattle that UserDomain.level was redundant
> and so should be removed

These two are both really very strange anyway. (And the level assumes
that everything is always a strict tree. That's not true. DAG is more
accurate.)

> - I don't see the value of AdminDomain.Owner. 

There should be the owner information in there somewhere, and it's
valuable in scenarios involving co-location facilities. Maybe you don't
do that, but we do. (It probably ought to be an association though.)

> - I don't think we need Domain.OtherInfo we have the description and the
> web page

Looks like some random extensibility. It's not clear how much of that
should be done by subclassing instead. And CSV? Oh dear...

> - IDs (as URIs) should be everywhere - but should never have meaning
> attached to them.

I certainly agree about not attaching meanings to IDs. And when they're
abused to mean "contact address", say that instead.

OK, now for *my* contributions from a quick glance...

1) It might be nice if each class listed the inherited properties it has
(even if it doesn't define what they mean). It'd make the schema easier
to read.

2) There probably ought to be a standard space in the Policy class for
describing the language/syntax/etc. used to describe the policy (as
opposed to the purpose of the policy, which is identified by the
particular subclass).

3) Are all Endpoints web-services endpoints? If not, consider defining a
subclass WebServiceEndpoint and moving some of the current Endpoint
attributes into it (e.g. WSDL URL, IssuerCA, TrustRootCA). I'd limit the
number of WSDL URLs per WSEndpoint to 1 though; doesn't make much sense
to state more than that. (I should check whether it's easy to refer to a
particular service within a WSDL document, since I know you can publish
many in the same doc...)

4) Categorizing by URI: Just define that a Compute Endpoint must have
the Category URN set to, say, urn:OGF:Glue2:EndpointCategory:Compute (or
you could substitute a URI or URL; it's an arbitrary string in the
format of a URI, just like an XML namespace name is. I've not thought
hard about the actual URN I gave as an example BTW, so I won't feel
offended if you change it!)

5) The other thing to check for consistency with is CIM. (Alas, that's a
hard task as CIM is colossal.) Try to sweet-talk Ellen Stokes into
helping! :-)

Donal.