Make "Information Sources" entries in items a reference

[ribose-jeffreylau]

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

Updating an Information Source should automatically update it for all items referencing it.

from discussion with @maccraymer

[ronaldtse]

The goal here is to use the Bibliographic model from Relaton (which is an implementation of ISO 690) as a individual register item class so we can reuse these items.

This model should also be available from generic Registry Kit, I suppose. (@strogonoff )

[strogonoff]

The goal here is to use the Bibliographic model from Relaton (which is an implementation of ISO 690) as a individual register item class so we can reuse these items.

This model should also be available from generic Registry Kit, I suppose. (@strogonoff )

My impression is that we cannot introduce new item classes without going through a register data model change proposal and control body approval. Should we go ahead with that? What’s the process?

[ronaldtse]

This process happens at the ISO GR control body not at this repo. We have already previously discussed and agreed on it as part of the migration. I will raise it at the next CB meeting to confirm this change.

[maccraymer]

Actually, the Control Body is not responsible for the ISO 19111 data model. However, our view for many years now has been that, by introducing additional item classes (e.g., for citations and extents), we are not really violating the 19111 data model but merely extending it. Of course, it would be necessary to modify any extended item class to conform with a future 19111 model that implements such a class slightly differently.

The revision or amendment of 19111 can be proposed by any ISO/TC 211 member at any time. It could simply be a resolution to amend the existing standard as has been done two now for 19111:2019. I think a better place to initiated this is within the Register Management Group (AG 14), which I chair. I think this is really one of it's purposes.

And given that ISO 19127 (which defines the ISO Geodetic Register) is presently in the process of being revised, I think it could also add or specify additional classes it deems necessary for the management of the ISOGR (distinct from the data model for the geodetic information). That might be the best place to discuss the issue. I think 19127 could recommend additional classes to the RMG and they in turn recommend a 19111 amendment to TC 211.

The 19127 project team is meeting on April 6 together with the 19135 meeting (unfortunately, I'm giving a workshop that morning). We can also discuss this at the next RMG meeting (hopefully, next month if I can ever get out a Doodle poll for that).

-Mike

[strogonoff]

@ronaldtse

The goal here is to use the Bibliographic model from Relaton (which is an implementation of ISO 690) as a individual register item class so we can reuse these items.

This model should also be available from generic Registry Kit, I suppose. (@strogonoff )

To recap the overall medium term plan so far:

• Adopt ISO 690 bib data model for information sources

• Capture information sources at proposal time. Every proposal has information sources associated with it, almost like a structured supporting justification. Associate those sources with items added, clarified, amended in proposal at a level other than register item data (which indeed should contain subject domain specific, in this case geodetic, information)

• We have a choice to keep information sources as “special” separate register item class that can be independently clarified/amended, or as part of register item payload.

  I don’t like “special” so I like the latter one more but I guess it’s up to CB…

  (Also if we make it part of RegistryKit If we make it a separate register item class, then it becomes part of register data model, but dictating register data model in registry kit means any register that wants to start using this system will have to adopt this new register item class.)

[ronaldtse]

The bibliographic item model should just be a normal register item class to the user's perspective, hence not "special".

What is "special" about it is that we should treat it as a commonly used class that other registers that use RegisterKit can easily adopt.

This is easiest if we have a "register item class definition library" online or on GitHub that RegisterKit can pull the definition (of the bibliographic item class) from.