ncal:Attachment: Tracker Ontology Reference Manual

## ncal:Attachment ncal:Attachment |

## Description

An object attached to a calendar entity. This class has been introduced to serve as a structured value of the ncal:attach property. See the documentation of ncal:attach for details.

## Class hierarchy

        http://www.w3.org/2000/01/rdf-schema#Resource
            nie:DataObject
            ╰── nfo:FileDataObject
                ╰── nfo:EmbeddedFileDataObject
                    ╰── nfo:Attachment
                        ╰── ncal:Attachment

## Properties

### The `“ncal:attachmentContent”` property

    “ncal:attachmentContent”          http://www.w3.org/2001/XMLSchema#string

The uri of the attachment. Created to express the actual value of the ATTACH property defined in RFC 2445 sec. 4.8.1.1. This property expresses the BINARY datatype of that property. see ncal:attachmentUri for the URI datatype.

Number of possible elements per resource (Cardinality): 1

### The `“ncal:encoding”` property

    “ncal:encoding”          ncal:AttachmentEncoding

To specify an alternate inline encoding for the property value. Inspired by RFC 2445 sec. 4.2.7. Originally this property had a limited vocabulary. ('8BIT' and 'BASE64'). The terms of this vocabulary have been expressed as instances of the AttachmentEncoding class

Number of possible elements per resource (Cardinality): 1

### The `“ncal:fmttype”` property

    “ncal:fmttype”          http://www.w3.org/2001/XMLSchema#string

To specify the content type of a referenced object. Inspired by RFC 2445 sec. 4.2.8. The value of this property should be an IANA-registered content type (e.g. application/binary)

Number of possible elements per resource (Cardinality): 1

### The `“ncal:attachmentUri”` property

    “ncal:attachmentUri”          http://www.w3.org/2000/01/rdf-schema#Resource

The uri of the attachment. Created to express the actual value of the ATTACH property defined in RFC 2445 sec. 4.8.1.1. This property expresses the default URI datatype of that property. see ncal:attachmentContents for the BINARY datatype.

Number of possible elements per resource (Cardinality): 1