The BioC format provides a lightweight offline annotation framework (for JSON or XML-formatted data) with very lightweight semantics but has not, to date, been developed as linked data. In this ontology, we provide a simple serialization of BioC classes and attributes for easy publishing to a semantic-web-compatible framework. This is preliminary work and will require additional mapping to existing Web Annotation standards. A bridging ontology for easy publishing of annotations developed under the National Library of Medicine's BioC format as linked data. Comeau DC, Islamaj Doğan R, Ciccarese P, Cohen KB, Krallinger M, Leitner F, Lu Z, Peng Y, Rinaldi F, Torii M, Valencia A, Verspoor K, Wiegers TC, Wu CH, Wilbur WJ. 'BioC: a minimalist approach to interoperability for biomedical text processing.' Database (Oxford). 2013 Sep 18;2013:bat064. doi:10.1093/database/bat064. Print 2013. PubMed PMID: 24048470; PubMed Central PMCID:PMC3889917.' BioC Linked Data bioc http://purl.org/bioc/ (This does not imply any endorsement from any members of this group and are listed here for the purpose of attribution) The BioC group: P. Ciccarese, K. Cohen, M. Krallinger, F. Leitner, L. Hirschman, Z. Lu, Y. Peng, F. Rinaldi, M. Torii, A. Valencia, K. Verspoor, T. Wiegers, C. Wu G. Burns 07/22/2017 0.1 http://bioc.sourceforge.org/ annotations documents locations nodes passages relations sentences date id key length offset refid role source text Annotations associated with a specific Passage. A note about 'infons': we translate the infons construct to <emph>any object relation that is not contained within the BioC namespace</emph>. The BioC format uses general associative arrays to describe these additional metadata, but linked data naturally provides this structure natively BioCAnnotation Collection of documents nnCollection of documents for a project. They may be an entire corpus or some portion of a corpus. Fields are provided to describe the collection. Documents may appear empty if doing document at a time IO. A note about 'infons': we translate the infons construct to <emph>any object relation that is not contained within the BioC namespace</emph>. The BioC format uses general associative arrays to describe these additional metadata, but linked data naturally provides this structure natively BioCCollection Each bioc:Document in the bioc:Collection. An id, typically from the original corpus, identifies the particular document. It includes bioc:Passages in the document and possibly bioc:Relations over annotations on the document. A note about 'infons': we translate the infons construct to <emph>any object relation that is not contained within the BioC namespace</emph>. The BioC format uses general associative arrays to describe these additional metadata, but linked data naturally provides this structure natively BioCDocument The connection to the original text can be made through the :offset, :length, and possibly the :text data properties. BioCLocation BioCNode One passage in a bioc:Document. This might be the bioc:text in the passage and possibly bioc:Annotations over that text. It could be the bioc:Sentences in the passage. In either case it might include bioc:Relations over annotations on the passage. A note about 'infons': we translate the infons construct to <emph>any object relation that is not contained within the BioC namespace</emph>. The BioC format uses general associative arrays to describe these additional metadata, but linked data naturally provides this structure natively. BioCPassage Relationship between multiple bioc:Annotations and possibly other bioc:Relations. BioCRelation A bioc:Document offset to where the sentence begins in the bioc:Passage. This value is the sum of the passage offset and the local offset within the passage. BioCSentence