1. Authority Vectors David E. Ellis March 9th, 2010

2. Types of Authority Vectors

3. Authority Relationship

4. Slide 3 Explanation • Another important concept from this figure is that COIs (e.g. “Social Structures”) define Authority. Authority is not a single COI parameter however, and in fact has significant importance in “Policy-oriented” routing. Authority can be delegated down or allowed up. • There is a concept of an “Authority Vector” which is critical to the routing of messages via a SPOR. The “Vector” can be “Hierarchical” or “Set” based on potential Participants. The “Hierarchical” vector is just a special case of the “Set” vector where the subset of Participants is grouped because they all have some common attribute. • The Geospatial authority is an example of a mixed type of “policy” vector where the two components being mixed are the “Geographical” and the Geopolitical” components. • If we consider the subdivisions of areas on the surface of the earth, we can divide the regions by geographic locations into any number of arbitrary labels and granularity (e.g. UnLoCodes, FIPS, ZIP, etc.) Regions can include sub-regions in this area scheme (e.g. counties within a state.) However, if we consider the earth as a planet in the Solar System, the Earth is just a member of the “Set” of planets. • This concept is critically important in determining the level of authority or rights of a COI within a multi-dimensional Authority Space. The Geo-Political label includes a third type of vector which is a composite of two or more basic vector spaces

5. Geopolitical --------- Geographical

6. How to Construct URNRFC 2141 • The URN is a pointer to the Ontological Class used to construct Predicate Calculus • IT must represent a unique path in the ontology • Construction should follow a Ruleset that will include Authority Vector, Type, Level, Class and possibly Location • !Authority, *Type, $Level, =Class, @Location • Label = Value • Examples • URN::!GP:*Mixed:$UN;US;NM;BE;ABQ:=something:@UNLOCODE • URN::AU=GP:TY=Mixed:LV=UN;US;NM;BE;ABQ; CL=something:AT=UNLOCODE • URN::1234 ANYTHING used to access Database • Once you have decided on URN Representation of Ontology you can register it with IANA for Universal Usage

7. URN Predicate Calculus Using Existential Quantification:Each delimited URN Identifier (part of an Authority Vector) or Group of Identifiers (set of Authority Vector parts)has a Quantifiable Value$(For some – There is - a) n (variable - URN identifier) 0 (an element of)N (where N = the set of allowable URN Identifiers)= O (some Value);So some formula of mathematical operatorsacting on the sequence of URN IDs will match a specified URN result Value.for the collective Authority Vector

8. SQL Extraction • Populate with Recipient Roles • SELECT OperationalNode.Name • FROM • OperationalNode INNER JOIN InformationExchange ON OperationalNode.id = InformationExchange.ReceivingOperationalNodeIdentifier • WHERE • InformationExchange.SendingOperationalNodeIdentifier = • (SELECT id FROM OperationalNode WHERE Name = '${/EDXLDistribution/senderRole/value}.Value') • AND • InformationExchange.InformationElementIdentifier = • (SELECT id From InformationElement WHERE Name = '${/EDXLDistribution/keyword/value}.Value'); • Populate with Explicit adrresses • SELECT * FROM OperationalNodeHasExplicitAddress • WHERE OperationalNodeIdentifier = • (SELECT id FROM OperationalNode WHERE Name = '${/EDXLDistribution/recipientRole/value}.Value') • Add EDXL DE to Cache • INSERT INTO edxl (dateTime, distributionID, edxl) • VALUES ('${/EDXLDistribution/dateTimeSent}.Value', • '${/EDXLDistribution/distributionID}.Value',