Delete class gist:SchemaMetaData

[rjyounes]

[uscholdm]

If this is to be removed, there should be a clear alternative for putting things that would currently be under SchemaMetaData.

[rjyounes]

gist dev team meeting 4/10:

Michael has subclassed this: e.g., tables, rows and columns; data fields

Jamie: in favor of keeping it

We need input from @mkumba on why he wants to delete it and what would replace it as a covering class for cases like Michael's examples above.

[mkumba]

what is gist computing using for the covering class now. I'm torn between generative content and just content. Dave McComb, CEO https://www.semanticarts.com On Apr 10, 2025 at 9:54 AM -0600, Rebecca Younes ***@***.***>, wrote: gist dev team meeting 4/10: Michael has subclassed this: e.g., tables, rows and columns; data fields Jamie: in favor of keeping it We need input from @mkumba<https://github.com/mkumba> on why he wants to delete it and what would replace it as a covering class for cases like Michael's examples above. — Reply to this email directly, view it on GitHub<#1200 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAAGJPVALKVXOEWQ23ORSWD2Y2H33AVCNFSM6AAAAABXAYU7CSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOOJUGMZTGOJWGI>. You are receiving this because you were mentioned.Message ID: ***@***.***> [https://avatars.githubusercontent.com/u/1693668?s=20&v=4]rjyounes left a comment (semanticarts/gist#1200)<#1200 (comment)> gist dev team meeting 4/10: Michael has subclassed this: e.g., tables, rows and columns; data fields Jamie: in favor of keeping it We need input from @mkumba<https://github.com/mkumba> on why he wants to delete it and what would replace it as a covering class for cases like Michael's examples above. — Reply to this email directly, view it on GitHub<#1200 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAAGJPVALKVXOEWQ23ORSWD2Y2H33AVCNFSM6AAAAABXAYU7CSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOOJUGMZTGOJWGI>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[uscholdm]

gistComputing currenlty uses ContentExpression for some metadata and data classes. Interestingly, SchemaMetadata is a subclass, which does not seem right to me at first blush.

[rjyounes]

Dev team meeting 4/24:

Dave: gistComputing has a lot of related concepts. Would remove from both gistCore and gistComputing. gistComputing has concepts like DataField which can be used instead. Three choices:

• Use gistComputing
• Define in client ontology
• Use DCAT/DPROD - but it's not well-defined

Jamie: Useful to have a top-level place to put schema metadata.

David B: Could SchemaMetadata be a subclass of ReferenceData? How are they distinct?

Dave: What are instances of SchemaMetadata? Names of legacy tables, column headings, data sets, etc. Not reference data.
In practice, when modeling schema metadata you usually define classes like Table, Column, etc.

Rebecca: SchemaMetadata could be the parent of Table, Column.

Straw poll:
Keep SchemaMetadata: 1
Move it to gistComputing: 9
Remove SchemaMetadata altogether: 0

DECISION: Remove from gistCore.

Definition in gistComputing needs to be tightened up.

gist:SchemaMetadata
	rdfs:subClassOf gist:DigitalContent ;
	owl:equivalentClass [
		a owl:Class ;
		owl:intersectionOf (
			gist:DigitalContent
			[
				a owl:Restriction ;
				owl:onProperty gist:describes ;
				owl:someValuesFrom gist:DigitalContent ;
			]
		) ;
	] ;
	skos:definition "Schema Metadata"^^xsd:string ;
	skos:editorialNote "KC: This is also defined in gistCore, but not nearly as rigorously. We should reconcile these and use only one."^^xsd:string ;
	.

• Add text definition
• Not all digital content that describes digital content is schema metadata. Do we need a different predicate, e.g. structures. Or use a subclass?

[rjyounes]

Dave: Define a class ContentMetadata to distinguish from SchemaMetadata? Example: the author field of a MARC record, vs the value of the field on a particular record.

Jamie: But ContentMetadata is not likely to go into gistComputing.