https://ontology.unifiedcyberontology.org/uco/observable/ContactSIP
A contact SIP is a grouping of characteristics unique to details for contacting a contact entity by Session Initiation Protocol (SIP).
Instances of observable:ContactSIP can have the following properties:
| PROPERTY | TYPE | DESCRIPTION | RANGE |
|---|---|---|---|
| From class owl:Thing | |||
| core:informalType | owl:DatatypeProperty | Informal Type serves as a parent property for string-valued properties meant to describe a type without implementing a class design. This property hierarchy supports a balancing point between semantic specificity and operational agility. The known benefits of describing types rather than implementing them include swift extensibility of some existing, or possibly non-existing, subclass hierarchy in UCO without requiring training in ontological development, taxonomic specification, or OWL, SHACL, or RDF maintenance logistics. The known detractions of using string-literals for type descriptions include that used vocabularies may require careful maintenance among data-sharing parties; that vocabularies require independent logistics (external to UCO) for providing definitions (i.e., dictionary-style semantics) to string-literals chosen; and that string-literals cannot by themselves encode hierarchical structure or entailments, such as the informal device type string 'ExamplePhone 8 P4321' entailing 'ExamplePhone 8', 'ExamplePhone', or 'ExamplePhone models discontinued in 2020'. Usage of Informal Type to house strings should be weighed against usage of classes when classes are available, and should periodically be reviewed for potential additions to UCO's class hierarchy or downstream extensions thereof. | owl:Thing |
| types:threadNextItem | owl:ObjectProperty | The link to a next item in a thread. | owl:Thing |
| types:threadPreviousItem | owl:ObjectProperty | A direct link to a previous item in a thread. | owl:Thing |
By the associated SHACL property shapes, instances of observable:ContactSIP can have the following properties:
PROPERTY |
PROPERTY TYPE |
DESCRIPTION |
MIN COUNT |
MAX COUNT |
LOCAL RANGE |
GLOBAL RANGE |
|
|---|---|---|---|---|---|---|---|
| observable:ContactSIP | |||||||
| observable:contactSIPScope | owl:DatatypeProperty |
Contact SIP scope specifies the relevant scope (home, work, school, etc) of details for contacting a contact entity by Session Initiation Protocol (SIP).
|
1 |
xsd:string
|
owl:Thing | ||
| observable:sipAddress | owl:ObjectProperty |
A SIP address specifies Session Initiation Protocol (SIP) identifier.
|
1 |
observable:ObservableObject
|
observable:ObservableObject
|
||
@prefix core: <https://ontology.unifiedcyberontology.org/uco/core/> .
@prefix observable: <https://ontology.unifiedcyberontology.org/uco/observable/> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix sh: <http://www.w3.org/ns/shacl#> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
observable:ContactSIP a owl:Class,
sh:NodeShape ;
rdfs:label "ContactSIP"@en ;
rdfs:comment "A contact SIP is a grouping of characteristics unique to details for contacting a contact entity by Session Initiation Protocol (SIP)."@en ;
rdfs:subClassOf core:UcoInherentCharacterizationThing ;
sh:property [ sh:class observable:ObservableObject ;
sh:maxCount 1 ;
sh:nodeKind sh:IRI ;
sh:path observable:sipAddress ],
[ sh:datatype xsd:string ;
sh:message "As of UCO 1.4.0, the datatype to use for observable:contactSIPScope should be xsd:string. Not using xsd:string will be an error in UCO 2.0.0." ;
sh:path observable:contactSIPScope ;
sh:severity sh:Warning ],
[ sh:maxCount 1 ;
sh:nodeKind sh:Literal ;
sh:path observable:contactSIPScope ],
observable:ContactSIP-contactSIPScope-in-shape ;
sh:targetClass observable:ContactSIP .