Matches in LOV for { ?s <http://www.w3.org/2000/01/rdf-schema#comment> ?o. }
- M2MTechnology comment "".
- ManetAttack comment "Manet (Mobile ad hoc network) is a self-configuring network of mobile devices connected.".
- ManetSecurityMechanism comment "".
- ManetTechnology comment "".
- MeshArchitecture comment "".
- MeshAttack comment "".
- MeshSecurityMechanism comment "".
- MeshTechnology comment "".
- ModeOperation comment "A mode of operation describes the process of encrypting each of block cipher.".
- NetworkManagementAttack comment "".
- NetworkManagementSecurityMechanism comment "".
- NetworkManagementTechnology comment "".
- NonRepudiationMethod comment "Non repudiation means that a sender is unable to deny having sent a message or infoomation.".
- OSIModelLayer comment "".
- OperatingSystemAttack comment "".
- OperatingSystemSecurityMechanism comment "".
- OperatingSystemTechnology comment "".
- PhysicalAuthentication comment "".
- PrivateKey comment "The private key is used for computing signatures and decryption.".
- ProgrammingLanguageAttack comment "".
- ProgrammingLanguageSecurityMechanism comment "".
- ProgrammingLanguageTechnology comment "".
- Protocol comment "".
- PublicKey comment "The public key is used for verifying a digital signature and is used for encryption.".
- Requirement comment "The application to secure has requirements (e.g., high sensitive data or specific technologies).".
- RfidAttack comment "".
- RfidSecurityMechanism comment "".
- RfidTechnology comment "".
- SecurityAlgorithm comment "".
- SecurityMechanism comment "Security Mechanisms are processes that are used to detect, prevent and recover from security attacks.".
- SecurityProperty comment "".
- SecurityPropertyMethod comment "".
- SecurityTool comment "".
- SemanticSecurityMethod comment "Semantic security ensures that an eavesdropper has no information about the message, even if it sees multiple encryptions of the same messages.".
- SensorAttack comment "".
- SensorSecurityMechanism comment "Sensor nodes have very limited computationnal power, and traditional security and encryption techniques are not-well suitd to this domain.".
- SensorTechnology comment "".
- ServerAttack comment "".
- ServerSecurityMechanism comment "".
- ServerTechnology comment "".
- SymmetricAlgorithm comment "The same secret key is used for encryption and decryption.".
- SymmetricKey comment "Symmetric key: the same key is used for encryption and decryption.".
- Technology comment "Technologies can be wireless (Wi-Fi, Wimax), cellular (2G, 3G, 4G), sensor networks, web application, etc.".
- UMTSArchitecture comment "".
- UMTSAttack comment "".
- UMTSSecurityMechanism comment "".
- UMTSTechnology comment "Universal Mobile Telecommunications System (UMTS). Third Generation (3G)".
- UwbAttack comment "".
- UwbSecurityMechanism comment "".
- UwbTechnology comment "".
- Virus comment "".
- WebAttack comment "".
- WebSecurityMechanism comment "".
- WebServiceAttack comment "".
- WebTechnology comment "".
- WifiArchitecture comment "".
- WifiAttack comment "".
- WifiSecurityMechanism comment "".
- WifiTechnology comment "".
- WimaxArchitecture comment "".
- WimaxAttack comment "".
- WimaxSecurityMechanism comment "".
- WimaxTechnology comment "".
- ZigbeeSecurityMechanism comment "".
- ZigbeeTechnology comment "".
- hasArchitecture comment "A technology has a specific architecture.".
- hasFeature comment "A SecurityMechanism has specific features (secured, depreceted, low energy consuming). For example, an asymmetric algorithm is high energy consuming.".
- hasSecurityMechanism comment "".
- hasVulnerability comment "A technology can be vulnerable to some attacks.".
- isFeatureOf comment "Features are related to security mechanisms. For example, an asymmetric algorithm is high energy consuming.".
- isProtectedBy comment "".
- isReplacedBy comment "When a SecurityMechanism is not secured anymore, it is replaced by a more secure SecurityMechanism. This is also the case for technologies: a technology can be replaced by another one more recent. (E.G., 2G has been replaced by 3G)".
- isSecurityMechanismOf comment "".
- isVulnerabilityOf comment "Some attacks cannot be thwart in technologies. For example, the Denial of Service is difficult to thwart in different technologies.".
- occursInLayer comment "".
- protects comment "".
- protectsInLayer comment "".
- sio.owl comment "general class inclusion axioms:\n'is part of' some 'physical entity' subClassOf 'is located in' some 'physical entity'\n\nrole chains:\n'has capability' o 'is realized in' -> 'is participant in'".
- SIO_000001 comment "'is related to' is the top level relation in SIO".
- SIO_000391 comment "Time intervals are specified as date/datetime ranges.".
- SIO_000450 comment "The value of a plotted geometric objects (e.g. point) can be obtained from the perpendicular projection of the position of the object onto the axis. Axis may also be associated with a textual description of what the values on the axis represents.".
- SIO_000458 comment "A value axis holds the properties of having a minimum and a maximum value, and is usually associated with tickmarks that indicate intervals along the axis.".
- Actor comment "Actors are entities that take part in an Event, either actively or passively. Actors do not necessarily have to be sentient. They can also be objects. Actors are a thing, animate or inanimate, physical or non-physical.".
- ActorType comment "EventType contains all resources that are used to classify Actors, e.g. person".
- Authority comment "Authorities are entities that state SEM properties. Their nature is not specified. They can symbolize people, organizations, sources of information, etc.".
- Constraint comment "The SEM Constraint class contains instances of properties that have a constrained (i.e. not universal) validity. This includes time dependent validity (Temporary), validity in the guise of a specific role (Role), or validity according to a given Authority (View).".
- Core comment "The SEM Core class contains all entities that make up the context of an event: Events, Actors, Places, Times. This class is meant to be extended for each application domain.".
- Event comment "Events are things that happen. This comprises everything from historical events to web site sessions and mythical journeys. Event is the central class of SEM.".
- EventType comment "EventType contains all resources that are used to classify Events, e.g. meeting.".
- Place comment "Places are locations where an Event happens. They do not need to be physical places and hence do not necessarily need coordinates. Neither do they need to have any significance apart from them being the location of an Event.".
- PlaceType comment "EventType contains all resources that are used to classify Places, e.g. river.".
- Role comment "Roles are properties with a subspecified function or position indicated by a RoleType in the scope of an Event. For example, the sem:hasActor property can be subspecified with the RoleType attacker, to denote that the type of participation of the Actor in the scope of the Event is \"attacker\". The sem:hasPlace property can be subspecified with the RoleType origin, to denote that within the scope of the Event it is the origin.".
- RoleType comment "EventType contains all resources that are used to classify Roles, e.g. receiver.".
- Time comment "Time contains symbolic representations of when an Event took place. Time instances do not necessarily need to have a timestamp associated with them. The Time class exists to represent semantics of time, e.g. that one thing happens before another, even though the exact timestamps are unknown.".
- TimeType comment "EventType contains all resources that are used to classify Time, e.g. century.".
- Type comment "The SEM Type class contains all types of Core instances. These can be either individuals of classes themselves. This class is meant to be extended for each application domain.".
- View comment "Views are properties that only hold according to a certain Authority.".
- eventProperty comment "Event properties connect Events to other SEM Core entities.".
- hasBeginTimeStamp comment "Has begin timestamp is used to indicate the beginning of a time interval. Omitting the hasBeginTimeStamp while stating a hasEndTimeStamp is interpreted as an open ended interval.".
- hasEndTimeStamp comment "Has end timestamp is used to indicate the end of a time interval. Omitting the hasEndTimeStamp while stating a hasBeginTimeStamp is interpreted as an open ended interval.".