comicmeta / comicbookontology Goto Github PK

It seems to have been superseded by the pageCount property... maybe I'm wrong?

If pageNumber is a distinct property-- it seems that it would be a literal field that can be used to indicate a particular page number within a published comic would be... helpful to me.

Or someone can explain instead how this property is intended to function?

Add PURLs for CBO classes

Add a qualifying property for the appearance of a character, object, etc. E.g. the first appearance of a character...

This area needs work, and would benefit from additional input.

See #11

Add cbo:Gutter class and cbo:gutter object property. This class represents the space between panels, and can be used to group sequences.

Transition all HTTP URIs to HTTPS.

• Replace http://comicmeta.org with https://comicmeta.org
• Add owl:sameAs for all URIs
• Update Wikidata references (see #17)

See notes below regarding LD HTTP vs HTTPS:

• https://schema.org/docs/faq.html#19
• https://wiki.dnb.de/display/DINIAGKIM/HTTP+vs.+HTTPS+in+resource+identification

Update cbo:Sequence class and subclasses (cbo:Page, etc.), and update the domain/range of related object properties.

There is not always a direct or consistent relationship between visual elements (a balloon does not always appear in a panel, etc.)

Definition of cbo:Comic should more explicitly define comics medium:

"A creative work of sequential art: the juxtaposition of text, images, and other pictorial elements to communicate information."

The current page says "Copyright: Copyright © PD&C, LLC". I'd remove the copyright because there is already a license statement and an author.

I'd also add a date to easily tell when the current draft is from.

I've started to align CBO with Wikidata properties and items. Mappings can directly be stored in Wikidata and queried like this at https://query.wikidata.org/:

# Ontology mapping between Comic Book Ontology and Wikidata
SELECT ?uri ?relation ?pLabel ?p WHERE {
  { ?p wdt:P2236 ?uri . BIND ("⊂" AS ?relation) } UNION # sub-property
  { ?p wdt:P2235 ?uri . BIND ("⊃" AS ?relation) } UNION # super-property
  { ?p wdt:P1628 ?uri . BIND ("=" AS ?relation) } UNION # equivalent property
  { ?p wdt:P1709 ?uri . BIND ("=" AS ?relation) } UNION # equivalent class
  { ?p wdt:P2888 ?uri . BIND ("=" AS ?relation) }       # exact match    
  FILTER(STRSTARTS(STR(?uri), "http://comicmeta.org/"))
  SERVICE wikibase:label { bd:serviceParam wikibase:language "en" }
}

It is some manual work to complete a mapping and some properties/classes have no counterpart but once the mapping exists, we can extract Comic Book Data from Wikidata in CBO format. By now there are around 25.000 comics and comic series in Wikidata.

Help in extending the mapping is welcome! I can then code the wrapper to extract CBO data from Wikidata.

An ordinary page within a comic might be described as a 1-page spread, I imagine, but perhaps there is reason to include a regular page?

In addition, study of comics as artifacts might include an "advertisement page" or something similar-- most comics ads are full pages, and even if they are not-- can a page be labeled as more than one type?

Lastly, would some foldouts simply extend the standard 2-page spread into a 3 or 4 page spread, or similar. However, other foldouts are more complex, and unfold top to bottom. Is this currently notable? I cannot bring to mind comic book examples at the moment. (Although I do have copies of The Lord of the Rings that contain foldout maps (I think they're a 3x3 fold that collapses to about 6.5"x10", expanding to a total size of 20" by 30".)

The link is: http://comicmeta.org/issueOf

Also: CoverPage, SplashPage, Spread as Individuals of http://comicmeta.org/cbo/PageType

(I will come back to this issue, should I find more)

I'm not sure if I've organized this wrong, or if there's a deeper problem with how CBO or RDF allows for multiple children of the same type.

I figured that a comic page could have multiple panels... but this is not yet working.

Is this because of some relationship to the sequence property/term? Does it need to built into the same document?

If Mr. Petiya (or anyone else) can help, let me know.

This is the relevant section:

<!-- Comic Page and Panels -->
	<rdf:Description rdf:about="https://dsps.lib.uiowa.edu/gibberishproject/wp-content/uploads/sites/84/2021/04/06-Asterix-and-Cleopatra_p17.jpg">
		<cbo:page>
			<cbo:panel rdf:resource="https://dsps.lib.uiowa.edu/gibberishproject/wp-content/uploads/sites/84/2021/04/06-Asterix-and-Cleopatra_p17-panel6.jpg"></cbo:panel>
			<cbo:panel rdf:resource="https://dsps.lib.uiowa.edu/gibberishproject/wp-content/uploads/sites/84/2021/04/06-Asterix-and-Cleopatra_p17-panel9.jpg"></cbo:panel>
		</cbo:page>
	</rdf:Description>

Here's the entire document:

<rdf:RDF xmlns="http://www.w3.org/2002/07/owl#"
      xml:base="http://www.w3.org/2002/07/owl"
      xmlns:dc="http://purl.org/dc/elements/1.1/"
      xmlns:cbo="http://comicmeta.org/cbo/"
      xmlns:owl="http://www.w3.org/2002/07/owl#"
      xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
      xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
      xmlns:schema="http://schema.org/">

	<!--Comic Series: Asterix (1969) -->
	<rdf:Description rdf:about="https://www.comics.org/series/20005/">
		<cbo:seriesTitle>Asterix</cbo:seriesTitle>
		<cbo:seriesYear>1969</cbo:seriesYear>
		<cbo:volumeNumber>6</cbo:volumeNumber>
		<cbo:issue rdf:resource="https://www.comics.org/issue/315214/"></cbo:issue>
		<cbo:publisher rdf:resource="https://www.comics.org/brand_group/2549/"></cbo:publisher>
		<cbo:language>en</cbo:language>
	</rdf:Description>

	<!-- Comic Issue: Asterix and Cleopatra (1969) #6 -->
	<rdf:Description rdf:about="https://www.comics.org/issue/315214/">
		<cbo:issueNumber>6</cbo:issueNumber>
		<cbo:publicationDate>1969</cbo:publicationDate>
		<cbo:edition>5</cbo:edition>

		<!-- Comic Story: 'Asterix and Cleopatra' -->
		<cbo:story>
		<rdf:Description>
			<cbo:storyTitle>Asterix and Cleopatra</cbo:storyTitle>
			<cbo:character rdf:resource="https://www.wikidata.org/wiki/Q7620503" schema:name="Asterix"></cbo:character>
			<cbo:character rdf:resource="https://www.wikidata.org/wiki/Q715597" schema:name="Obelix"></cbo:character>
			<cbo:character rdf:resource="https://www.wikidata.org/wiki/Q1752911" schema:name="Dogmatix"></cbo:character>
			<cbo:character rdf:resource="https://www.wikidata.org/wiki/Q635" schema:name="Cleopatra"></cbo:character>
			<cbo:character rdf:resource="https://www.wikidata.org/wiki/Q3188509" schema:name="Julius Caesar"></cbo:character>
			<cbo:writer rdf:resource="https://viaf.org/viaf/22142570/" schema:name="Rene Goscinny"></cbo:writer>
		</rdf:Description>
		</cbo:story>
	</rdf:Description>
	  
	<!-- Comic Page and Panels -->
	<rdf:Description rdf:about="https://dsps.lib.uiowa.edu/gibberishproject/wp-content/uploads/sites/84/2021/04/06-Asterix-and-Cleopatra_p17.jpg">
		<cbo:page>
			<cbo:panel rdf:resource="https://dsps.lib.uiowa.edu/gibberishproject/wp-content/uploads/sites/84/2021/04/06-Asterix-and-Cleopatra_p17-panel6.jpg"></cbo:panel>
			<cbo:panel rdf:resource="https://dsps.lib.uiowa.edu/gibberishproject/wp-content/uploads/sites/84/2021/04/06-Asterix-and-Cleopatra_p17-panel9.jpg"></cbo:panel>
		</cbo:page>
	</rdf:Description>

	<!-- Panel and Speech Balloons -->
	<rdf:Description rdf:about="https://dsps.lib.uiowa.edu/gibberishproject/wp-content/uploads/sites/84/2021/04/06-Asterix-and-Cleopatra_p17-panel6.jpg">
		<cbo:balloon rdf:resource="https://dsps.lib.uiowa.edu/gibberishproject/wp-content/uploads/sites/84/2021/04/06-Asterix-and-Cleopatra_p17-panel6-balloon1.jpg"></cbo:balloon>
		<cbo:balloon rdf:resource="https://dsps.lib.uiowa.edu/gibberishproject/wp-content/uploads/sites/84/2021/04/06-Asterix-and-Cleopatra_p17-panel6-balloon2.jpg"></cbo:balloon>
		<cbo:balloon rdf:resource="https://dsps.lib.uiowa.edu/gibberishproject/wp-content/uploads/sites/84/2021/04/06-Asterix-and-Cleopatra_p17-panel6-balloon3.jpg"></cbo:balloon>
	</rdf:Description>

	<!-- Panel and Speech Balloons -->
	<rdf:Description rdf:about="https://dsps.lib.uiowa.edu/gibberishproject/wp-content/uploads/sites/84/2021/04/06-Asterix-and-Cleopatra_p17-panel9.jpg">
		<cbo:balloon rdf:resource="https://dsps.lib.uiowa.edu/gibberishproject/wp-content/uploads/sites/84/2021/04/06-Asterix-and-Cleopatra_p17-panel9-balloon1.jpg" ></cbo:balloon>
	</rdf:Description>

</rdf:RDF>

Align cbo with bib.schema.org; replace references to schema:Publication, schema:PublicationIssue, etc. with appropriate comic classes and properties defined in bib.schema.org.

https://terms.tdwg.org/wiki/rdfs:isDefinedBy

Currently, throughout the ComicBookOntology when rdfs:isDefinedBy is used, the object is a string literal (ie with quotes around it) rather than being a Resource (ie with > and < around it ).

Thanks for the ontology, nice work!

The property cbo:page should be subproperty of dcterms:hasPart; a story has multiple pages.

The example here of RDF/XML, for Daredevil #67 may have an issue.

    <!-- Comic Page: Cover of Daredevil (1964) #67 -->
    <cbo:page>
      <rdf:Description rdf:about="http://example.org/issue/Daredevil_1964_67#cover">
        <cbo:pageType rdf:resource="http://comicmeta.org/vocab/CoverPage"></cbo:pageType>
        <cbo:penciller schema:name="Marie Severin"></cbo:penciller>
        <cbo:letterer schema:name="Sam Rosen"></cbo:letterer>
        <cbo:inker schema:name="Bill Everett"></cbo:inker>
      </rdf:Description>     <--------------
    </cbo:page>
    <cbo:coverPage rdf:resource="http://example.org/issue/Daredevil_1964_67#cover"></cbo:coverPage>
  </rdf:Description>

The line noted here-- line 54 in the original document, seems to have an additional RDF close tag.
Either I am very much misunderstanding XML, or RDF, or this is an error.

Can you confirm, or explain?

Thanks.

Hi, first of all sorry if I say something stupid, but this is my first try with rdf. I'm trying to use this vocabulary in a web app for a simple collection of comics, featuring by now just series and copy. However I haven't found a way to represent a textual description given by the user, that could be either a review (like 'great comic') or the actual state of the comic, or even a combination of both. That is, a generic description that has a meaning to the user that wrote it. I read you suggested to use http://purl.org/dc/terms/description in another issue, could this be good?

Also I haven't found a property about a rating given by the user, like from 1 to 5 or similar, I only found "official" ratings. However I found that often readers like to give a review of how much they liked the comic (the story). Is there a suggested way of doing this?

Thank for your work anyway, this has been very useful to me.

When working with CBO here's what I came across that struck me as confusing/unclear

1. I know this is fundamental...but according to Figure 26 on page 88 of your thesis, an issue is-a publication, a volume is-a publication a series is-a publication and a publication is-a comic.

I'm not super clear though on how that whole thing shakes out.

Some specific issue of Amazing Spider-Man, say 10.

Issue: Amazing Spider-Man 10
Series: Amazing Spider-Man
Volume: 1
Publication:
Comic:

Or are the breadth of the terms Publication and Comic intended to convey that *any graphic art can be analyzed as a Comic (like treating a collective resource as a single Work or analyzing it analytically as 4 different Works [in FRBR terms]), and Publication covers anything having been published at any level of description.

1. Follow up, in an ontology like this, do properties distribute down the heirarchy? That is, Publication has the property "distributedBy" which links a comic series to a distributor, so it seems I should be able to use it in a Series, but the property doesn't appear in Series.

2. Speaking of Series...is there an intended difference between the properties "dcterms:language" and "language"?

3. The property "imprint" is a property of Publisher, but can it also be a property of Series? That is, I have a comic series published by K.K. Publications, in the Gold Key imprint (example here: http://www.comics.org/issue/20119/) but when describing it, I can't put "imprint" as a property of Series.

   <rdf:Description rdf:about="http://www.comics.org/series/1763/">
   <rdf:type rdf:resource="http://comicmeta.org/cbo/Series"/>
   <cbo:country rdf:resource="http://id.loc.gov/authorities/names/n78095330.html"/>
   <cbo:language rdf:resource="http://id.loc.gov/vocabulary/iso639-2/eng"/>
   <cbo:publisher rdf:resource="http://id.loc.gov/authorities/names/n50059055.html"/>
   <cbo:indiciaPublisher rdf:resource="http://id.loc.gov/authorities/names/n89616660.html"/>
   <cbo:imprint rdf:resource="http://www.comics.org/brand/86/"/>
   <cbo:format rdf:resource="http://comicmeta.org/vocab/ComicBook"/>
   cbo:seriesTitleLaredo/cbo:seriesTitle
   cbo:seriesYear1966/cbo:seriesYear
   /rdf:Description

4. I was hoping to be able to identify a first appearance of a universe object/person. While there is a property of 'appearance' on domain Comic, do you think it'd be possible to also have a property of first appearance?

dcterms:language should be hidden from live CBO specification.

See #11

Thought bubbles are distinct from speech bubbles in the predictable 'cloud', but there are many varieties.
Border types, color of text, color of background within bubble, etc.

Fun examples:
The shape of a balloons is sometimes custom to mark a theme (Grimm Fairy Tales card Queens have bubbles either shaped like or decorated by their suit symbols).

Professor X's telepathy bubbles are often thought bubbles with 'ports' of parallel lines that actually break the border of the bubble, usually found at the low points of the typical cloud shape.

This sort of internal structure is not highly emphasized by CBO, but I'm curious about such an implementation-- thinking of creating an example database of fictive neographies from comic books, and it would be useful to be able to label the type of 'textual space' that a distinguishable, but not always readable, textual thing appears. I'm considering that not all 'textual spaces' in a comic book fall clearly into the balloon or caption category, although examples do not come to mind.

the current mapping is reverse

cbo:Page and cbo:Story should be subclasses of cbo:Sequence; a sequence is both the page and its contents, as well as the story.

Add PURLS for CBO data/object properties

CBO documentation is generated dynamically from RDF/XML using custom XSL transformations (XSLT). The XSL files are being added to the project for reference.

Remove cbo:Document; no value to this class after changes in #47, move cbo:pageCount and cbo:Page properties to cbo:Story