Make "Extent" entries in items a reference

[ribose-jeffreylau]

... so that they can be reused by different items.

Updating an Extent should automatically update it for all items referencing it.

from discussion with @maccraymer

[strogonoff]

I think we cannot make it a reference because we cannot introduce a register item class without going through control body register model/data model change approval. What we can do is a feature that allows to import an extent from another item, similar to how it works in Java backend.

[maccraymer]

I think Ron had an idea for how extents and citations could be referenced and reused. I suggest to discuss this with him. I can't recall what his suggestion was but it may have been similar to what Anton has suggested. I think the idea may have been to keep a list of all extents/citations in the register, from which we could pick one to reuse. -Mike

[maccraymer]

On second thought, just picking an extent from existing ones will not be enough. As for information sources (citations), we need to be able to correct a single common extent used by multiple items (the extents are reused MANY times). It would be far to onerous to have to correct the same extent in every single item using it (there could be hundreds!). So I see no way around having separate items in the register for extents and information sources. These can be hidden from the general public but accessible by submitters, the Register Manager, the Control Body and the Register Owner. They would be approved along with the rest of the proposal. They just would be visible to the general public as separate item classes.

…

-Mike From: Craymer, Michael ***@***.***> Sent: March 23, 2023 8:53 AM To: paneron/registry-kit ***@***.***>; paneron/registry-kit ***@***.***> Cc: Michael Craymer ***@***.***>; Mention ***@***.***> Subject: RE: [paneron/registry-kit] Make "Extent" entries in items a reference (Issue paneron/extension-geodetic-registry#14) I think Ron had an idea for how extents and citations could be referenced and reused. I suggest to discuss this with him. I can't recall what his suggestion was but it may have been similar to what Anton has suggested. I think the idea may have been to keep a list of all extents/citations in the register, from which we could pick one to reuse. -Mike

[ronaldtse]

@maccraymer is correct that we should make the Extent a register item class (or concept class in the new 19135 terminology). Since Extents are often reused, we should manage them as register items.

[strogonoff]

@maccraymer is correct that we should make the Extent a register item class (or concept class in the new 19135 terminology). Since Extents are often reused, we should manage them as register items.

@ronaldtse From our meeting last Monday I got a strong impression that we are not to make unilateral changes to register data model. Should we submit the addition of a new register item class “Extent” for consideration to control body?

[ronaldtse]

@maccraymer is the chair of the control body; this topic has been discussed extensively at the control body. However I do not know if we have had a formal "control body decision"?

[strogonoff]

For now extent import had been implemented for feature parity. This was discussed on the call first (but the issue was not filed, perhaps that point slipped through the cracks) as an important feature while extents are not separate items and cannot be referenced.