Subclasses of gist:ContentExpression

[rjyounes]

Make Address and Text subclasses of ContentExpression rather than Content.

[uscholdm]

This makes sense at first blush. What I am not sure about is whether the address I write down on a piece of paper has a gist:GeneralMediaType. ITs not too much of a stretch, is probably fine. Currently we have:

gist:Address
	a owl:Class ;
	rdfs:subClassOf gist:Content ;
	skos:definition "A reference to a place (real or virtual) that can be located by some routing algorithm and where messages or things can be sent to or received from."^^xsd:string ;
	skos:example "A PO Box, a URL to a PDF file."^^xsd:string ;
	skos:prefLabel "Address"^^xsd:string ;
	.

gist:ContentExpression
	a owl:Class ;
	rdfs:subClassOf
		gist:Content ,
		[
			a owl:Restriction ;
			owl:onProperty gist:isCategorizedBy ;
			owl:someValuesFrom gist:GeneralMediaType ;
		] ,
		[
			a owl:Restriction ;
			owl:onProperty gist:isExpressedIn ;
			owl:someValuesFrom gist:Language ;
		]
		;
	skos:definition "Intellectual Property reduced to text, audio etc.  If it contains text (written or spoken), it may be in a language."^^xsd:string ;
	skos:prefLabel "Content Expression"^^xsd:string 

gist:Text
	a owl:Class ;
	owl:equivalentClass [
		a owl:Class ;
		owl:intersectionOf (
			gist:Content
			[
				a owl:Restriction ;
				owl:onProperty gist:isExpressedIn ;
				owl:someValuesFrom gist:Language ;
			]
			[
				a owl:Restriction ;
				owl:onProperty gist:containedText ;
				owl:someValuesFrom xsd:string ;
			]
		) ;
	] ;
	skos:definition "Content expressed as words and numbers (not graphics)."^^xsd:string ;
	skos:prefLabel "Text"^^xsd:string ;
	.

[rjyounes]

Hm, I'm wondering if you're confusing MediaType with GeneralMediaType. The latter is for digital media types like png, docx, etc. An address wouldn't necessarily have that, but that's for FormattedContent. It would have a GeneralMediaType, which are real world categories like textual, audio, visual, etc. The address you write on a piece of paper certainly has that.

[rjyounes]

gist dev team meeting 4/10:

Text seems unarguably a ContentExpression.
DECISION: make Text a subclass of ContentExpression.

ID should go with Address. But these could be just concepts rather than expressions.

But when we talk about IDs and Addresses we are talking about the ContentExpression, but when we talk about, say, a book we might be talking either about the Content (FRBR Work) or the ContentExpression (FRBR Expression).

Michael/Rebecca: Are two addresses the same if one uses "St." and the other "Street"? If yes, then we are talking about Content. If no, we are talking about ContentExpression. What is most useful?

[rjyounes]

gist dev team meeting 5/22:

Michael/Phil: Address seems more like a "work," in that typographical differences in the representation of an address don't make two different addresses.

DECISION: Make Text a subclass of ContentExpression, leave Address as a subclass of Content.