Skip to Content.
Sympa Menu

perfsonar-dev - Re: RNC files for registration

Subject: perfsonar development work

List archive

Re: RNC files for registration


Chronological Thread 
  • From: Loukik Kudarimoti <>
  • To: Maciej Glowiak <>
  • Cc: Perfsonar Development List <>
  • Subject: Re: RNC files for registration
  • Date: Fri, 19 Jan 2007 15:27:39 +0000

umm..I am trying to understand your suggestion Maciej. I have a question. Are you suggesting that the rnc specification for the LS registration message *of a particular service* (not the LS itself) be split across two documents - Interface Specification of the LS itself and the Interface specification of the particular service?

Loukik.



Maciej Glowiak wrote:
Hi Loukik,

I think the need of complete description LSRegisterRequest for all services is not appropriate. I've just browsed the registration part of RRD MA interface specification and I think we should divide the RNC file on two separate sections. One should define general LSRegisterRequest and should be put ONLY in LS interface specification (message & metadata elements), the second one should be defined by particular services (data element).

For instance (look at the end of the listing):

========================================================================
# ... namespaces ...

start = element nmwg:message { MessageContent }

MessageContent =
Identifier? &
MessageIdentifierRef? &
Type &
(
ServiceMetadata,
Data+
)

Identifier =
attribute id { xsd:string }

MessageIdentifierRef =
attribute messageIdRef { xsd:string }

Type =
attribute type { "LSRegisterRequest" }

ServiceMetadata=
element nmwg:metadata {
(
Identifier &
MetadataIdentifierRef? &
ServiceSubject
)
}

MetadataIdentifierRef =
attribute metadataIdRef { xsd:string }

ServiceSubject = element perfsonar:subject {
(
Identifier &
ServiceInfo
)
}

ServiceInfo =
element psservice:service {
(
Identifier &
element psservice:serviceName {text} &
element psservice:accessPoint {text} &
element psservice:serviceType {text} &
element psservice:serviceDescription {text} ?
)
}

Data =
element nmwg:data {
(
Identifier &
MetadataIdentifierRef &
Metadata
)
}

# --------------------------------------------------
# TO BE DEFINED in particular service documents
# --------------------------------------------------
#
# Metadata =
# element nmwg:metadata {
# (
# ...
# )
# }

========================================================================

Best regards
Maciej




Archive powered by MHonArc 2.6.16.

Top of Page