perfsonar-dev - metadata in the service setupDataResponse variations
Subject: perfsonar development work
List archive
- From: maxim <>
- To:
- Subject: metadata in the service setupDataResponse variations
- Date: Thu, 17 Jan 2008 15:01:20 -0600
Hello to Everyone,
I am looking into building PingER MA SetupDataResponse as the
interoperable piece pf perfSONAR infrastructure. For that I've tried to
gather information about what
kind of metadata variations were implemented by services as part of
SetupDataResponse messages.
I've taken these schema pieces from functional testing directory.
For example JavaRRD has this:
-----------------------------
( Subject | FilterMetadataContent | MetadataKeyContent
) &
EventType? &
Parameters?
----------------------
where Parameters = element nmwg:parameters { ParametersContent } &
element select:parameters { ParametersContent }?
and the same Parameters might be in the FilterMetadataContent part. Is it
expected behavior ?
On other hand the sshtelnet has this variation:
---------------------------
Subject,
Parameters?,
EventType?
----------------------
And E2Emon has very different piece of metadata and it seems like not
supporting eventType at all:
----------------------
element nmwg:subject {
Identifier &
SubjectIdRef? &
(
MessageNode |
MessageLink
)
-------------------
So, my question is - what pieces and in what order
"must be" supported by service for MDM release ?
Thanks,
Maxim Grigoriev.
- metadata in the service setupDataResponse variations, maxim, 01/17/2008
Archive powered by MHonArc 2.6.16.