This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "April 13th, 2010 Security Conference Call"

From HL7Wiki
Jump to navigation Jump to search
Line 50: Line 50:
 
**Classes: when you’re dealing with a kind-of-something (concepts) and when you want to allow further precision
 
**Classes: when you’re dealing with a kind-of-something (concepts) and when you want to allow further precision
 
**Individuals: when you’re dealing with things that have an identity and can be counted (atoms), or you don’t need further precision.
 
**Individuals: when you’re dealing with things that have an identity and can be counted (atoms), or you don’t need further precision.
*Open world assumption:  Anything may be true unless it is proven false.   
+
*Open world assumption:  Anything may be true unless it is proven false.  This is in contrast to Closed-world assumption (e.g., database) where anything that cannot be found is assumed to be false.
**This contrasts with the Closed-world assumption (e.g., database) where anything that cannot be found is assumed to be false.
+
*Necessary and Sufficient Conditions (≡): In logic, the words necessity and sufficiency refer to the implicational relationships between statements. The assertion that one statement is a necessary and sufficient condition of another means that the former statement is true if and only if the latter is true.
*Necessary and Sufficient Conditions:  
 
 
*Primitive classes versus Fully Defined classes
 
*Primitive classes versus Fully Defined classes
*Subsumption
+
**Primitive: To be a member of a primitive class, an individual must either be directly asserted to be a member, or must be a member, by assertion or by inference, of a subclass. Primitive classes have only necessary conditions.
 +
**Fully Defined: Defined classes have one or more necessary and sufficient conditions.
 +
*Subsumption: Class-Superclass relationships.  Each class includes its subclasses, but classes can have multiple parents. 
 
*Disjointness: Classes are not disjoint by default; partial overlap of classes is assumed.  Disjointness must be made explicit.
 
*Disjointness: Classes are not disjoint by default; partial overlap of classes is assumed.  Disjointness must be made explicit.
*No unique name assumption:
+
*No unique name assumption:   different names may refer to the same entity, but OWL provides explicit constructs to express that two names denote distinct entities
 +
*Reasoner: OWL provides the necessary expressivity to write class expressions that are rich enough for the reasoner to infer the polyhierarchy: universal restriction (only), existential restriction (some), number restriction (min, max, exactly), boolean operators (or, and, not), etc.

Revision as of 05:00, 16 April 2010

Security Working Group Meeting

Back to Security Main Page

Attendees

Agenda

  1. (05 min) Roll Call, Approve minutes 6 April 2010 & Accept Agenda
  2. (55 min) Security and Privacy Ontology Project

Minutes

1. Action Items

Reminder: Composite Security and Privacy Domain Analysis Model ballot is now open. Please vote!

2. Resolutions

Minutes of 6 April were approved. Motion to approve by Mike Davis, seconded by Suzanne Gonzales-Webb

3. Updates/Discussion

Security and Privacy Ontology Project

  • Mike attended the SOA Ontology project call on Monday, April 12 and reported that Protégé v.4.0.2 has been selected for use (the most recent and stable version of Protégé)
  • Mike also reported on discussions taking place within the OASISXACML committee with respect to ontologies
    • The committee approved a work item to investigate ontologioes and a follow up call took place with Jericho Systems to discuss strategies and determine how Jericho would be involved. The management of Jericho is concerned about how this work might impact their products so this needs to be resolved.
  • The Security and Privacy Ontology project will be following the OASIS XACML committee activities as well as the SOA Ontology project as there are there opportunities for us to harmonize wit those efforts
  • The focus of the rest of today’s meeting (which extended into the CBCC WG) for the next two hours was a presentation of the work underway by Tony Weida on developing an ontology for Role-based Access Control using Protégé. (The demonstration today was using the alpha version of Protégé v.4.1)
    • Tony began with an overview of Description Logic (DL), OWL and the Protégé-OWL editor plug-in. Tony then proceeded into the RBAC ontology demonstration.

Some important concepts related to ontologies that were touched on include:

  • Classes versus individuals
    • Classes: when you’re dealing with a kind-of-something (concepts) and when you want to allow further precision
    • Individuals: when you’re dealing with things that have an identity and can be counted (atoms), or you don’t need further precision.
  • Open world assumption: Anything may be true unless it is proven false. This is in contrast to Closed-world assumption (e.g., database) where anything that cannot be found is assumed to be false.
  • Necessary and Sufficient Conditions (≡): In logic, the words necessity and sufficiency refer to the implicational relationships between statements. The assertion that one statement is a necessary and sufficient condition of another means that the former statement is true if and only if the latter is true.
  • Primitive classes versus Fully Defined classes
    • Primitive: To be a member of a primitive class, an individual must either be directly asserted to be a member, or must be a member, by assertion or by inference, of a subclass. Primitive classes have only necessary conditions.
    • Fully Defined: Defined classes have one or more necessary and sufficient conditions.
  • Subsumption: Class-Superclass relationships. Each class includes its subclasses, but classes can have multiple parents.
  • Disjointness: Classes are not disjoint by default; partial overlap of classes is assumed. Disjointness must be made explicit.
  • No unique name assumption: different names may refer to the same entity, but OWL provides explicit constructs to express that two names denote distinct entities
  • Reasoner: OWL provides the necessary expressivity to write class expressions that are rich enough for the reasoner to infer the polyhierarchy: universal restriction (only), existential restriction (some), number restriction (min, max, exactly), boolean operators (or, and, not), etc.