# Trusted Data Access Control Based on Logistics Business Collaboration Semantics
## 4 Construction of Access Control Model
### Semantic Access Policy Set
#### 4.3.2 Example Rules and Their Functions  
1. [label=(0)]
2. Granting Access Based on Role and Conditions _Rule1 = Subject(?x) Object(?y) Supplier(?a) hasRole(?x,?a) Receiveaddress(?y) Worksite(?b) WorkingHour(?c) hasTime(?x,?c) hasLocation(?x,?b) -> permit(?x,?y)_ Following Rule1, if the role of entity x is the supplier and the access request to the shipping address y is begun through the intranet during working hours, it is judged that entity x is permitted to access the shipping address y.
3. Denying Access Based on Role and Object _Rule2 = Subject(?x) Object(?y) Warehouseman(?a) hasRole(?x,?a) Worksite(?b) Shipper_ Information(?y) WorkingHour(?c) hasTime(?x,?c) hasLocation(?x,?b) -> deny(?x,?y)_  
\begin{table}
\begin{tabular}{p{142.3 pt} p{284.5 pt}} \hline \hline
**Role** & **Function** \\ \hline Supplier & Raw material suppliers or original manufacturers of products represented by enterprises \\ \hline Forwarder & Organize the entire process, such as developing transportation plans, contacting carriers, tracking goods, etc. \\ \hline Third-party logistics & Third-party logistics is responsible for managing and executing logistics activities related to goods transportation, warehousing management, supply chain management, etc. \\ \hline Carrier & The company or individual responsible for transporting goods can be a logistics company, transportation company, or individual operator, etc. \\ \hline Warehouseman & Responsible for managing all inventory in the warehouse, including receiving, storing, picking, packaging, and shipping \\ \hline QualityInspector & Responsible for checking the quality and quantity of goods to ensure that they meet the requirements of the shipper and consignee \\ \hline LogisticsCourier & Responsible for logistics distribution/reception work for the first and last mile \\ \hline Consignee & The person or company who received the goods \\ \hline \hline \end{tabular}
\end{table}
Table 3: Functional architecture in collaborative logistics Processes.  
If the role of entity x is the warehouseman, and an access request to the shipper information y is begun through the intranet during working hours, x is refuses to access the shipper information.
3. Emergency Access with Privilege Attribute Due to the system automatically adding a 'privilege' attribute after each policy result of 'deny', the added rules are as follows: _Rule3 = Subject(?x) Object(?y) Warehouseman (?a) hasRole(?x,?a) Worksite(?b) Shipper_information (?y) WorkingHour(?c) hasTime(?x,?c) hasLocation(?x,?b) emergent(?x, true) -> permit (?x,?y)_ If the role of entity x is a warehouseman and whose access request is for the shipper information y, and x in particular is really in an emergency situation, it is determined that entity x allows access to shipper information y.  
The above strategy for formulating SWRL grammar rules represents just a part of the application example. To more effectively cater to logistics scenarios, it necessitates further refinement, additions, and modifications to these rules.