search

fmidev / metcoop-wg-backend

MetCoOp Working Group Backend repository
0 stars 1 forks source link

Consider sender as urn:oid in MetCoOp CAP profile #5

Closed petringo closed 4 years ago

petringo commented 4 years ago

Current description (partial):

Format: WMO Organization ID (OID).

I would suggest to present the organization id as urn:oid instead of just oid value. For example use:

urn:oid:2.49.0.0.xxx.x

instead of

2.49.0.0.xxx.x

The suggested presentation would be self-explanatory. But doesn't have to be resolvable, as sender is merely used as a "namespace identifier" for cap document identifier.

tervo commented 4 years ago

urn:oid:2.49.0.0.xxx.x shall be used.

mrauhala commented 4 years ago

The correct one was urn:oid:2.49.0.1 according Elliot Christian. 1 is for message and 0 is for authority itself.

petringo commented 4 years ago

How is it here, is the \ related to authority or message? The CAP standard says that sender should identify globally the originator.

mrauhala commented 4 years ago

You are correct, we are talking about sender. My mistake. WMO position on is urn:oid:2.49.0.1

tervo commented 4 years ago

Done in https://git.smhi.se/metcoop/metcoop-cap-profile/blob/master/metcoop-cap-profile.md#sender