<?xml version="1.0" encoding="US-ASCII"?>
<!-- This template is for creating an Internet Draft using xml2rfc,
    which is available here: http://xml.resource.org. -->
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
<!-- One method to get references from the online citation libraries.
    There has to be one entity for each item to be referenced. 
    An alternate method (rfc include) is described in the references. -->

<!ENTITY RFC2119 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml">
<!ENTITY RFC2629 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2629.xml">
<!ENTITY RFC3552 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3552.xml">
<!ENTITY RFC5226 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5226.xml">
]>
<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
<!-- used by XSLT processors -->
<!-- For a complete list and description of processing instructions (PIs), 
    please see http://xml.resource.org/authoring/README.html. -->
<!-- Below are generally applicable Processing Instructions (PIs) that most I-Ds might want to use.
    (Here they are set differently than their defaults in xml2rfc v1.32) -->
<?rfc strict="yes" ?>
<!-- give errors regarding ID-nits and DTD validation -->
<!-- control the table of contents (ToC) -->
<?rfc toc="yes"?>
<!-- generate a ToC -->
<?rfc tocdepth="4"?>
<!-- the number of levels of subsections in ToC. default: 3 -->
<!-- control references -->
<?rfc symrefs="yes"?>
<!-- use symbolic references tags, i.e, [RFC2119] instead of [1] -->
<?rfc sortrefs="yes" ?>
<!-- sort the reference entries alphabetically -->
<!-- control vertical white space 
    (using these PIs as follows is recommended by the RFC Editor) -->
<?rfc compact="yes" ?>
<!-- do not start each main section on a new page -->
<?rfc subcompact="no" ?>
<!-- keep one blank line between list items -->
<!-- end of list of popular I-D processing instructions -->
<rfc category="info" docName="draft-jilongwang-opsawg-csp-01" ipr="trust200902">
 <!-- category values: std, bcp, info, exp, and historic
    ipr values: trust200902, noModificationTrust200902, noDerivativesTrust200902,
       or pre5378Trust200902
    you can add the attributes updates="NNNN" and obsoletes="NNNN" 
    they will automatically be output with "(if approved)" -->

 <!-- ***** FRONT MATTER ***** -->

 <front>
   <!-- The abbreviated title is used in the page header - it is only necessary if the 
        full title is longer than 39 characters -->

   <title abbrev="Network Resource Property Description">Framework for Network Resource Property Description</title>

   <!-- add 'role="editor"' below for the editors if appropriate -->

   <!-- Another author who claims to be an editor -->

   <author fullname="Zhi Sun" initials="SZ" role="editor"
           surname="Sun">
     <organization>CETC 30</organization>

     <address>
       <postal>
         <street></street>

         <!-- Reorder these if your country does things differently -->

         <city>Chengdu</city>

         <region></region>

         <code>610000</code>

         <country>China</country>
       </postal>
       
       <phone></phone>
       
       <email>sunzhi1019@163.com</email>
       
       <!-- uri and facsimile elements may also be added -->
     </address>
   </author>
  
   <author fullname="Da He" initials="HD" role="editor"
     surname="He">
     <organization>CETC 30</organization>
     
     <address>
       <postal>
         <street></street>
         
         <!-- Reorder these if your country does things differently -->
         
         <city>Chengdu</city>
         
         <region></region>
         
         <code>610000</code>
         
         <country>China</country>
       </postal>
       
       <phone></phone>
       
       <email>edawrdheda@outlook.com</email>
       
       <!-- uri and facsimile elements may also be added -->
     </address>
   </author>
   <author fullname="Jianfeng Chen" initials="CJF" role="editor"
     surname="Chen">
     <organization>CETC 30</organization>
     
     <address>
       <postal>
         <street></street>
         
         <!-- Reorder these if your country does things differently -->
         
         <city>Chengdu</city>
         
         <region></region>
         
         <code>610000</code>
         
         <country>China</country>
       </postal>
       
       <phone></phone>
       
       <email>atrix@163.com</email>
       
       <!-- uri and facsimile elements may also be added -->
     </address>
   </author>
      
   <author fullname="Rui Xu" initials="XR" role="editor"
     surname="Xu">
     <organization>CETC 30</organization>
     
     <address>
       <postal>
         <street></street>
         
         <!-- Reorder these if your country does things differently -->
         
         <city>Chengdu</city>
         
         <region></region>
         
         <code>610000</code>
         
         <country>China</country>
       </postal>
       
       <phone></phone>
       
       <email>jasmine_x@163.com</email>
       
       <!-- uri and facsimile elements may also be added -->
     </address>
   </author>
   
      <author fullname="Jilong Wang" initials="WJL" role="editor"
           surname="Wang">
     <organization>Tsinghua University</organization>

     <address>
       <postal>
         <street></street>

         <!-- Reorder these if your country does things differently -->

         <city>Beijing</city>

         <region></region>

         <code>100084</code>

         <country>China</country>
       </postal>
       
       <phone></phone>
       
       <email>wjl@tsinghua.edu.cn</email>
       
       <!-- uri and facsimile elements may also be added -->
     </address>
   </author>
   
   <date year="2019" />

   <!-- If the month and year are both specified and are the current ones, xml2rfc will fill 
        in the current day for you. If only the current year is specified, xml2rfc will fill 
	 in the current day and month for you. If the year is not the current one, it is 
	 necessary to specify at least a month (xml2rfc assumes day="1" if not specified for the 
	 purpose of calculating the expiry date).  With drafts it is normally sufficient to 
	 specify just the year. -->

   <!-- Meta-data Declarations -->

   <area>Management</area>

   <workgroup>opsawg</workgroup>

   <!-- WG name at the upperleft corner of the doc,
        IETF is fine for individual submissions.  
	 If this element is not present, the default is "Network Working Group",
        which is used by the RFC Editor as a nod to the history of the IETF. -->

   <keyword>Internet-Draft</keyword>

   <!-- Keywords will be incorporated into HTML output
        files in a meta tag but they have no effect on text or nroff
        output. If you submit your draft to the RFC Editor, the
        keywords will be used for the search engine. -->

   <abstract>
     <t>This memo discusses and defines a framework for cyberspace resource property description, which is suitable for the unified classification organization and description of multi-source network resource measurement information. 
	 Now, there is no unified description framework for network resource property. 
	 The objective of this draft is to establish a general model based on cyberspace identification reference, and implement the reuse of survey data in different users and occasions.
	 Then discuss the basic methodology and propose a less mature framework for further complement and improvement
       </t>
   </abstract>
 </front>

 <middle>
   <section title="Introduction">
     <t>Network space measurement is based on certain methods, techniques and standards. It uses software or hardware tools to test the composition, behavior and development of cyberspace by testing multiple indicators that characterize the state, property and relationships of various layers of cyberspace. The range of measurement can be local to the network space or global. The objects to be measured include the composition, structure, property, behavior, characteristics, laws and trends of the network space. The information obtained by measurement is a kind of typical big data. The content is diverse in format, complex in structure and rapid in change. It is difficult to understand, interact with, and disseminate the information.</t>
     <t>Given that network measurement data may be used by many people other than producers. It is usually produced by an individual or organization and used by others or organizations. Building a unified entity encoding rule enables people or organizations that are less familiar with each other to better share data and use the data appropriately. As web measurement data producers and users process more and more data, appropriate textual data can provide them with rich information about the data, enabling them to better manage, store, share, update and reuse data products.</t>
     <t>This memo can support the integration and management of surveying and mapping information across departments, cross-domains, time space, multi-source and multi-scale networks through the unified description of network space property. It can be used as cyberspace management in the future. It adopts a markup language RDF for describing network resource property, and focuses on the classification and coding rules of network measurement elements and their expansion methods.</t>
 
 <!-- This PI places the pagebreak correctly (before the section title) in the text output. -->
   <?rfc needLines="8" ?>
    
   </section>
     <section title="Terminology and Definition">
	      <section title="Terminology and Definition">
		  <t>In this memo, individuals represent the objects of interest in the field of network mapping space, and OWL does not use the Unique Name Assumption. It must clearly indicate whether individuals are identical, otherwise their relationship is unclear.</t>
		  <t>Note: Individuals are sometimes referred to as Instances.</t>
		  </section>
		  
	      <section title="Property">
		  	<t>Properties are binary relationships between individuals. In the description logic, the concept of a Role is represented. Properties can be divided into the following categories:</t>
			<t>Functional property</t>
			<t>Functional property can only be connected to one individual.</t>
			<t>Inverse Functional Property</t>
			<t>The inverse functional property is that for a given individual, only at most one individual can be connected through this property. That is, the inverse property of this property is a functional property.</t>
			<t>Inverse Property</t>
			<t>The inverse property uses only one property name as a parameter, indicating the inversion of the relationship.</t>
			<t>Transitive Property</t>
			<t>Transitive property means that the property can be passed.</t>
			<t>Object Property</t>
			<t>The Object property represents the relationship between instances of two classes.</t>
			<t>Datatype Property</t>
			<t>Connect individual and XML Schema data type values or RDF literals, Datatype property cannot be passed, symmetric, or inverse functional.</t>
		  </section>	      
		  <section title="Cyberspace Feature">
		  <t>Cyberspace is a virtual and real space where human beings use information facilities to construct and realize the information interaction, and then influence human thoughts and behaviors. It relies on the carrier of information and communication technology infrastructure carriers such as Internet, telecommunication networks, and various control systems and devices.</t>
		  <t>In cyberspace, the use of cyberspace means to detect and perceive entities, including the Internet, telecommunications networks, industrial control networks and other types of network resources. Specifically, cyberspace resources include physical equipment such as network infrastructure and network access; information resources and network services such as audio, video, websites and text data; virtual characters, various IP-based telecommunication network equipment and industrial control systems, etc.</t>
		  <t>The feature is an abstract representation of an entity. Note: Features can appear as types or as instances. When expressing only one meaning, you should use a feature type or a feature instance.A single cyberspace resource object existing in cyberspace is a specific unit of cyberspace resource feature, and it is also the smallest component of the corresponding feature types, and can be represented by specific symbols.</t>
		  </section>
	 
	</section>
   
   
   <section title="Symbol and Abbreviation">
    
<t>RDF:	 Resource Description Framework</t>
<t>RDFS:	Resource Description Framework Schema</t>
<t>XML:	 Extensible Markup Language </t>
<t>OWL:	Ontology Web Language</t>
<t>URI:	Uniform Resource Identifier</t>
<t>DTD:	Document Type Definition</t>
<t>IDL:	Interface Description Language</t>
<t>OCL:	Object Constraint Language</t>

     
   </section>
   
   <section title="Use cases">
     <t>The following sections highlight some of the most common framework for network resource property description use case scenarios and are in no way exhaustive.</t>
     <section title="Intelligent semantic search">
       <t>The traditional search method mainly uses keyword matching to realize the retrieval of information. Therefore, it is difficult for the user to simply use the keyword or keyword string to retrieve the content that he really needs, and the natural language changes with time, region or field. The same concept can be expressed in different language expressions. For the same concept retrieval, different users may use different keywords to query, resulting in a large amount of irrelevant information being returned to the user.
       </t>
	   <t>Intelligent semantic search based on framework for network resource property description is an advanced form of information retrieval, which can provide users with search results in an accurate and concise natural language. When the user initiates the query, the search engine will provides unique identities for each resource, map to parse and reason the keywords of the user query, and then map it to one or a set of concepts, and then according to the concept level in the framework.</t>
	 </section>
     <section title="Network security situational awareness">
       <t>
         There are many elements involved in cyber security. These elements often play a role in the attack threat. According to the order of context, the layers are progressive, and finally reflect the macro network security situation. The purpose of each element is different, and the network security situation process can be divided into several situational segments. Various situational elements are extracted through network security events.
       </t>
       <t>Network security situational awareness based on framework for network resource property description can be regarded as a specific situational segment. Through the structure of the security situational, the role of various situational elements is hierarchically displayed, enabling managers to grasp the current network security more deeply and accurately. </t>
       
     </section>
    
     <section title="Network Security">
       <t>Network viruses and worms themselves are also a kind of network
         resources. With the deepening of network opening and complexity,
         network viruses and worms are evolving constantly, and the 
         characteristics of diversity and spatial discretization are 
         increasing, resulting in a great hidden danger of network 
         security. </t>
       <t>The framework for network resources categorization can locate 
         the network resources more accurately and distinguish the 
         benign or malignant network resources,  study the process of 
         virus evolution and the possible effects according to the 
         attached attributes , and provide a clearer way to safeguard 
         the operation of network space security, such as anti 
         virus, antivirus and so on.
         
       </t>  
     </section>
             
   </section>
   
   <section title="Methodology for Network Resources Attribute Description"> 
     <section title="Basic Principles">
   
       <section title="Scientific principle">
         <t>The attribute description should conform to the basic organizational rules of cyberspace resource mapping information. The selection of attribute classification perspective should meet the integration requirements of multi-source cyberspace resource mapping information, and fully take into account the traditional information classification system in various fields, thus covering network mapping information at various levels and fields.</t>
       </section>
       <section title="Systematic principle">
         <t>The methodology of Attribute description should be designed with good compatibility and can cover the requirements of the attribute representation of network measuring and mapping feature of different scales, different properties and different types. The attribute categorization system should correctly reflect the measuring and mapping feature and the vertical and horizontal architecture attributes. The level of information categorization and grading should be clear and reasonable. The same perspective should be adopted for the categorization of objects at the same level.
         </t>
       </section>
       <section title="Consistency  principle ">
         <t> The design of attribute categorization and description should meet the uniqueness of the measuring and mapping feature attributes of cyberspace resources in the same mapping system, in which the values and units of the physical domain, logical domain and cognitive domain attributes of entities should be consistent with the national and international standards in related fields. When the scale of resources and attributes in cyberspace is modified and redirected, the description of resource attributes and the relationship between resources and attributes should be stable and semantically consistent.
         </t>    
       </section>
       
       
       <section title="Scalability  principle">
         <t>The attribute description, meta property description, resource-attribute relationship description and attribute-attribute relationship description of cyberspace resources are able to perfect and expand when facing the future development of cyberspace, multi-domain information integration and sharing, mapping of unknown resources and user requirements in different fields.
         </t>
       
       </section>
       
     </section>
     
     
     
 
   
   
   <section title="Attribute description framework"> 
     <t>In this memo, the attributes of cyberspace resources are described by RDF resource description framework, and metadata is described as a data model through XML syntax and RDFS. The basic RDF specification only defines the rules, and does not define the vocabularies for describing resources. It should be refined for practical application in different fields.</t>
     <t>RDF uses Web identifiers (URI) to identify things, and attributes and attribute values to describe resources, allowing RDF to represent one or more simple statements about resources as a graph of nodes and arcs, where nodes represent resource and attribute values and arcs represent attributes.</t>
     <t>The RDF description for the cyberspace resource attribute consists of a file, resource description, and statement three-level structure, which is serialized by RDF/XML syntax. A file can contain multiple resource descriptions, and a resource description can contain multiple statements, a statement can be expressed as a triplet composed of {subject, predicate, object} in natural language. In the cyberspace resource and the attribute description, the cyberspace resource entity is corresponding to the subject in the triplet, the cyberspace attribute type is corresponding to the predicate in the triplet, and the attribute value is corresponding to the object in the triplet, which constitute the{cyberspace resource entity, cyberspace attribute type, attribute value} triplet can accurately and unambiguously record and describe all the information obtained during the measuring and mapping process.</t>
   </section>
    <section title="Description of association rules for attributes description"> 
	<t>The association rules of attributes represent the internal relations between attributes, and the possible associations or relations between things can be found behind the data. Unsupervised machine learning methods commonly found in data mining can be used for knowledge discovery and building knowledge maps. In this memo, various attribute association operations are defined: alias relationship, synonym relationship, ownership relationship, and aggregation relationship.</t>
        <section title="Alias relationship"> 
		<t>1) Relationship name: ch: Alias</t>
        <t>2) Relational meaning: representing different names of the same attribute</t>
        <t>3) Constraints: optional </t>
        <t>4) Range: no specific requirements</t>
		</section>
		 <section title="Synonym  relationship"> 
<t>1) Relationship name: ch: Synonymy</t> 
<t>2) Relational meaning: representing the same meaning of multiple attributes</t> 
<t>3) Constraints: optional</t> 
<t>4) Range: no specific requirements</t> 

		</section>
		<section title="Ownership relationship"> 
<t>1) Relationship name: ch: Ownership</t> 
<t>2) Relational meaning: representing the inclusion relationship between attributes</t> 
<t>3) Constraints: optional</t> 
<t>4) Range: no specific requirements</t> 

		</section>
		<section title="Aggregation relationship"> 
<t>1) Relationship name: ch: Aggregation</t> 
<t>2) Relational meaning: representing the clustering relationship of multiple attributes</t> 
<t>3) Constraints: optional</t> 
<t>4) Range: no specific requirements</t> 

		</section>

	</section>
     		<section title="Meta property"> 
<t>The meta property is defined as an attribute of a measuring and mapping data attribute, and is used to describe information such as a feature type, a domain, a range, a hierarchy, an aggregate, and a reference attribute.</t> 
		<section title="Property type"> 
<t>1) Metaproperty name: meta_property: type</t> 
<t>2) Metaproperty meaning: Representing the category of an attribute</t> 
<t>3) Data type: STRING (XML Schema.STRING)</t> 
<t>4) Constraints: mandatory</t> 
<t>5) Range: sub-classification results of attributes</t> 

		</section>
				<section title="Property hierarchy"> 
<t>1) Metaproperty name: meta_property: hierarchy</t> 
<t>2) Metaproperty meaning: Representing the hierarchy to which the attribute belongs</t> 
<t>3) Data type: STRING (XML Schema.STRING)</t> 
<t>4) Constraints: mandatory</t> 
<t>5) Range: physics, logic, cognition and society</t> 

		</section>
						<section title="Property range"> 
<t>1) Metaproperty name: meta_property: range</t> 
<t>2) Metaproperty meaning: Representing the attribute value range</t> 
<t>3) Data type: STRING (XML Schema.STRING)</t> 
<t>4) Constraints: mandatory</t> 
<t>5) Range: depending on the value of the property</t> 

		</section>
		
								<section title="Hash of property value"> 
<t>1) Metaproperty name: meta_property: hash</t> 
<t>2) Metaproperty meaning: The hash of property</t> 
<t>3) Data type: INT (XMLSchema.INT)</t> 
<t>4) Constraints: mandatory</t> 
<t>5) Range: 8-bit hash</t> 

		</section>
						<section title="Property keyword"> 
<t>1) Metaproperty name: meta_property: keyword</t> 
<t>2) Metaproperty meaning: Keyword that represents the value of the property; if not, fill in null</t> 
<t>3) Data type: STRING (XML Schema.STRING)</t> 
<t>4) Constraints: mandatory</t> 
<t>5) Range: no specific requirements</t> 

		</section>
		
		<section title="Rate of property change"> 
<t>1) Metaproperty name: meta_property: rate</t> 
<t>2) Metaproperty meaning: Representing the frequency of change of attributes</t> 
<t>3) Data type: STRING (XML Schema.STRING)</t> 
<t>4) Constraints: mandatory</t> 
<t>5) Range: Static, slow change, fast change, change as needed</t> 

		</section>
				<section title="Property dependency"> 
<t>1) Metaproperty name: meta_property: depend</t> 
<t>2) Metaproperty meaning: Representation attribute generation depends on additional attributes.</t> 
<t>3) Data type: STRING (XML Schema.STRING)</t> 
<t>4) Constraints: optional</t> 
<t>5) Range: Other attribute name</t> 

		</section>
		</section>
     
     
   </section>
   
   
   <section title="Framework for Network Resources Attribute Description">
     <t>According to the state, structure and behavior characteristics of resources at different levels in cyberspace, this memo divides the properties of resources in cyberspace into four categories, namely physical domain, logical domain, cognitive domain and social domain, which are respectively used to describe the explicit and partial implicit characteristics of resources at corresponding levels. In addition to representing the properties of cyberspace resources, the memo also includes nine meta property, which represent the common features of attributes. The attribute description specifies its meaning, data type, range of values, and so on as much as possible.
     </t>
     <section title="Physical domain attributes">
       <t>The physical domain attribute represents a subset of features that can be observed, queried, recorded, and measured in the physical space and geospatial of each resource feature constituting the cyberspace. Each attribute value is closely related to the objective existence of the corresponding resource feature in the physical world. Resources are at a higher level, the material basis of services. According to the attribute, the focus of the resource entity is reflected, and further subdivided into basic attributes, electrical attributes and security attributes..</t>
        <section title="Basic attributes of the entity">
			<t>The basic attributes of the entity cover the general characteristics of the naming, identification, location, attribution, appearance, material, and price of the resource in the physical space. Most of the basic attributes of resources of a single entity, once determined, change little during the run and can be considered a more stable base class feature.</t>
       <t>	name</t> 
<t>1) Attribute name: exns_property: phys_name</t> 
<t>2) Attribute meaning: the name of the entity</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: no specific requirements</t> 
<t>	Country</t> 
<t>1) Attribute name: exns_property: phys_country</t> 
<t>2) Attribute meaning: the country of the entity</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: meet the GB/T 2659-2000 standard specification</t> 
<t>	Country Code</t> 
<t>1) Attribute name: exns_property: phys_countrycode</t> 
<t>2) Attribute meaning: country code of the entity</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: meet the GB/T 2659-2000 standard specification</t> 
<t>	City</t> 
<t>1) Attribute name: exns_property: phys_city</t> 
<t>2) Attribute meaning: the city to which the entity belongs</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: meet the GB/T 2659-2000 standard specification</t> 
<t>	Streets</t> 
<t>1) Attribute name: exns_property: phys_street</t> 
<t>2) Attribute meaning: the street to which the entity belongs</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: meet the GB/T 2659-2000 standard specification</t> 
<t>	Latitude</t> 
<t>1) Attribute name: exns_property: phys_latitude</t> 
<t>2) Attribute meaning: the geographic latitude of the entity</t> 
<t>3) Data type: floating point number (XMLSchema.FLOAT)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: meet the GB/T 28589-2012 standard specification</t> 
<t>	Longitude</t> 
<t>1) Attribute name: exns_property: phys_longitude</t> 
<t>2) Attribute meaning: the geographical longitude of the entity</t> 
<t>3) Data type: floating point number (XMLSchema.FLOAT)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: meet the GB/T 28589-2012 standard specification</t> 
<t>	Affiliation</t> 
<t>1) Attribute name: exns_property: phys_organization</t> 
<t>2) Attribute meaning: the Chinese name of the organization to which the entity belongs</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: no specific requirements</t> 
<t>	Manufacturer</t> 
<t>1) Attribute name: exns_property: phys_manufacturer</t> 
<t>2) Attribute meaning: the manufacturer of the entity</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: no specific requirements</t> 
<t>	Model code</t> 
<t>1) Attribute name: exns_property: phys_entity_model</t> 
<t>2) Attribute meaning: the specific model code of the entity</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: required</t> 
<t>5) Range of values: no specific requirements</t> 
<t>	Date of manufacture</t> 
<t>1) Attribute name: exns_property: phys_manufacturedata</t> 
<t>2) Attribute meaning: the date of production of the entity</t> 
<t>3) Data type: date type (XMLSchema.DATETIME)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: meet the GB/T 7408-1994 standard specification</t> 
       
        </section>
       <section title="Electrical attributes of the entity">
	   <t>The electrical attributes of the entity are used to describe the component characteristics, signal characteristics, electrical characteristics, connection characteristics, energy conversion characteristics, etc. necessary for the resource to support the operation of the network space. These characteristics reflect and constrain the realization level of the function and performance of the resource entity at a higher level.</t>
       <t>	Boot date</t> 
<t>1) Attribute name: exns_property: phys_startdate</t> 
<t>2) Attribute meaning: the boot date of the entity</t> 
<t>3) Data type: date type (XMLSchema.DATETIME)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: meet the GB/T 7408-1994 standard specification</t> 
<t>	Chip temperature</t> 
<t>1) Attribute name: exns_property: phys_chiptemperature</t> 
<t>2) Attribute meaning: physical sensor chip temperature</t> 
<t>3) Data type: floating point number (XMLSchema.FLOAT)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: no specific requirements</t> 
<t>	Power consumption</t> 
<t>1) Attribute name: exns_property: phys_power</t> 
<t>2) Attribute meaning: average power consumption of physical work</t> 
<t>3) Data type: floating point number (XMLSchema.FLOAT)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: greater than zero</t> 
<t>	Input voltage</t> 
<t>1) Attribute name: exns_property: phys_inputvoltage</t> 
<t>2) Attribute meaning: physical input voltage</t> 
<t>3) Data type: floating point number (XMLSchema.FLOAT)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: no specific requirements</t> 
<t>	The output voltage</t> 
<t>1) Attribute name: exns_property: phys_outputvoltage</t> 
<t>2) Attribute meaning: the output voltage of the entity</t> 
<t>3) Data type: floating point number (XMLSchema.FLOAT)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: no specific requirements</t> 
<t>	Input Current</t> 
<t>1) Attribute name: exns_property: phys_inputcurrent</t> 
<t>2) Attribute meaning: physical input current</t> 
<t>3) Data type: floating point number (XMLSchema.FLOAT)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: no specific requirements</t> 
<t>	Output current</t> 
<t>1) Attribute name: exns_property: phys_outputcurrent</t> 
<t>2) Attribute meaning: the output current of the entity</t> 
<t>3) Data type: floating point number (XMLSchema.FLOAT)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: no specific requirements</t> 
<t>	Baud rate</t> 
<t>1) Attribute name: exns_property: phys_baudrate</t> 
<t>2) Attribute meaning: physical serial communication baud rate</t> 
<t>3) Data type: floating point number (XMLSchema.FLOAT)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: no specific requirements</t> 
<t>	Firmware</t> 
<t>1) Attribute name: exns_property: phys_firmware</t> 
<t>2) Attribute meaning: firmware version of the entity</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: no specific requirements</t> 
	   </section>
       <section title="Environmental adaptation attributes of the entity">
	   <t>The environmental adaptation attributes of the entity reflect the relevant characteristics of the entity itself to avoid the impact and destruction of the source from the physical world in anticipation and unanticipated circumstances, and to avoid the disruption of the integrity and availability of its functions within certain limits, and reflects the self-protection ability of the entity in the physical world.</t>
	   <t>	Stability</t> 
<t>1) Attribute name: exns_property: phys_safe_stability</t> 
<t>2) Attribute meaning: characterize the stability of the entity in the physical domain</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: no specific requirements</t> 
<t>	Heat resistance</t> 
<t>1) Attribute name: exns_property: phys_ safe_heatresistance</t> 
<t>2) Attribute meaning: characterize the heat resistance of the entity in the physical domain, the highest temperature at which the entity works normally.</t> 
<t>3) Data type: floating point number (XMLSchema.FLOAT)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: no specific requirements</t> 
<t>	High frequency oscillation</t> 
<t>1) Attribute name: exns_property: phys_ safe_oscillationresistance</t> 
<t>2) Attribute meaning: characterize the highest oscillation frequency that the entity can withstand</t> 
<t>3) Data type: floating point number (XMLSchema.FLOAT)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: no specific requirements</t> 
<t>	Resistance to surge</t> 
<t>1) Attribute name: exns_property: phys_ safe_surgeresistance</t> 
<t>2) Attribute meaning: characterizing the immunity of the entity in the physical domain</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: no specific requirements</t> 
<t>	Corrosion resistance</t> 
<t>1) Attribute name: exns_property: phys_ safe_corrosionistance</t> 
<t>2) Attribute meaning: characterize the corrosion resistance of the entity in the physical domain</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: no specific requirements</t> 
	   </section>
	   </section>
       <section title="logical domain attributes">
	   <t>The logical attributes describe the characteristics inherent, endowed, maintained or changed in the process of the generation, transmission, storage, exchange, use and clearing of the data and information of the various resource features constituting the cyberspace. Including the basic attributes of network equipment, network service attributes, network performance attributes, network topology attributes and network security attributes.</t>
		       <section title="Basic attributes of network devices">
				<t>The basic attributes of network devices are the basic characteristics of the naming, address, structure and composition of resource entities in cyberspace, which are used to realize the ability of identification, query and communication, etc., and are generally shared by all network devices.</t>
				<t>	MAC address</t> 
<t>1) Attribute name: exns_property: logi_mac</t> 
<t>2) Attribute meaning: MAC address of the network device</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: required</t> 
<t>5) Range of values: conforms to the unified mac address format provided by TCP/IP protocol</t> 
<t>	IP address</t> 
<t>1) Attribute name: exns_property: logi_ip</t> 
<t>2) Attribute meaning: IP address of the network device</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: required</t> 
<t>5) Range of values: in accordance with IP address notation</t> 
<t>	Subnet mask</t> 
<t>1) Attribute name: exns_property: logi_mask</t> 
<t>2) Attribute meaning: subnet mask of the network device</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: required</t> 
<t>5) Range of values: conforms to the subnet mask representation specification</t> 
<t>	Gateway address</t> 
<t>1) Attribute name: exns_property: logi_gateway</t> 
<t>2) Attribute meaning: gateway address of the network device</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: required</t> 
<t>5) Range of values: in accordance with IP address notation</t> 
<t>	DNS address</t> 
<t>1) Attribute name: exns_property: logi_dns</t> 
<t>2) Attribute meaning: domain name server address of the network device</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: required</t> 
<t>5) Range of values: in accordance with IP address notation</t> 
<t>	DHCP address</t> 
<t>1) Attribute name: exns_property: logi_dhcp</t> 
<t>2) Attribute meaning: Dynamic allocation of IP server address of network device</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: in accordance with IP address notation</t> 
<t>	host name</t> 
<t>1) Attribute name: exns_property: logi_hostname</t> 
<t>2) Attribute meaning: host name of the network device</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: no specific requirements</t> 
<t>	domain name</t> 
<t>1) Attribute name: exns_property: logi_domain</t> 
<t>2) Attribute meaning: the name of the domain to which the network device belongs</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: no specific requirements</t> 

				</section>
		  <section title="Attributes of network services">
		  <t>The attributes of network services are used to describe the mechanism, mode, scope, condition and other characteristics of the interaction between entity resources and other entities in the network, including but not limited to the processes of establishing connections, providing data, obtaining data, and transferring data.</t>
          <t>	Data Format</t> 
<t>1) Attribute name: exns_property: logi_datatype</t> 
<t>2) Attribute meaning: end-to-end data format</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: no specific requirements</t> 
<t>	Projection entity</t> 
<t>1) Attribute name: exns_property: logi_projectiveentity</t> 
<t>2) Attribute meaning: network equipment providing network services</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: no specific requirements</t> 
<t>	Service type</t> 
<t>1) Attribute name: exns_property: logi_servicetype</t> 
<t>2) Attribute meaning: the protocol type of the network service, for example: ftp, http, https, etc.</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: no specific requirements</t> 
<t>	Known port</t> 
<t>1) Attribute name: exns_property: logi_port _wellknow</t> 
<t>2) Attribute meaning: a recognized port open to the network device</t> 
<t>3) Data type: integer array (XMLSchema.INT)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: range from 0 to 1023</t> 
<t>	Registered port</t> 
<t>1) Attribute name: exns_property: logi_port_registered</t> 
<t>2) Attribute meaning: the registered port of the network device is open to the outside world.</t> 
<t>3) Data type: integer array (XMLSchema.INT)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: range from 1024 to 49151</t> 
<t>	Dynamic port</t> 
<t>1) Attribute name: exns_property: logi_port _dynamic</t> 
<t>2) Attribute meaning: dynamic port open to network devices</t> 
<t>3) Data type: integer array (XMLSchema.INT)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: ranging from 49152 to 65535</t> 
<t>	Port banner information</t> 
<t>1) Attribute name: exns_property: logi_port_banner</t> 
<t>2) Attribute meaning: banner information that the network device is open to the outside world</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: no specific requirements</t> 
<t>	Port rate</t> 
<t>1) Attribute name: exns_property: logi_port_rate</t> 
<t>2) Attribute meaning: real-time rate of network device open port</t> 
<t>3) Data type: floating point number (XMLSchema.FLOAT)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: rate statistics should be greater than zero, generally in MB/S units</t> 
<t>	Port throughput</t> 
<t>1) Attribute name: exns_property: logi_port_ flux</t> 
<t>2) Attribute meaning: traffic statistics of network device open ports</t> 
<t>3) Data type: floating point number (XMLSchema.FLOAT)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: Traffic statistics should be greater than zero, generally in MB units</t> 
<t>	Port transfer protocol</t> 
<t>1) Attribute name: exns_property: logi_port_transportprotocol</t> 
<t>2) Attribute meaning: the transmission protocol of the open port of the network device, for example: udp, tcp, etc.</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: no specific requirements</t> 
<t>	Service address</t> 
<t>1) Attribute name: exns_property: logi_url</t> 
<t>2) Attribute meaning: the access address provided by the network service</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: no specific requirements</t> 
		  </section>
		  <section title="Attributes of network performance">
			<t>The attributes of network performance are used to describe the different characteristics of capacity, efficiency and ability of resource entities to perform various logical domain network operations and activities, which can indirectly reflect the value and importance of resources in cyberspace.</t>
		  <t>	Backplane bandwidth</t> 
<t>1) Attribute name: exns_property: logi_backplane_bandwidth</t> 
<t>2) Attribute meaning: backplane bandwidth of the network device</t> 
<t>3) Data type: floating point number (XMLSchema.FLOAT)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: greater than zero</t> 
<t>	Packet forwarding rate</t> 
<t>1) Attribute name: exns_property: logi_forwarding_rate</t> 
<t>2) Attribute meaning: packet forwarding rate of network devices</t> 
<t>3) Data type: floating point number (XMLSchema.FLOAT)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: greater than zero</t> 
<t>	Forwarding delay</t> 
<t>1) Attribute name: exns_property: logi_forwarding_delay</t> 
<t>2) Attribute meaning: forwarding delay of network equipment</t> 
<t>3) Data type: floating point number (XMLSchema.FLOAT)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: greater than zero</t> 
<t>	QoS packet forwarding rate</t> 
<t>1) Attribute name: exns_property: logi_qosforwarding_rate</t> 
<t>2) Attribute meaning: qos packet forwarding rate of network devices</t> 
<t>3) Data type: floating point number (XMLSchema.FLOAT)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: greater than zero</t> 
<t>	Packet loss rate</t> 
<t>1) Attribute name: exns_property: logi_packet_ loss</t> 
<t>2) Attribute meaning: packet loss rate of network devices</t> 
<t>3) Data type: floating point number (XMLSchema.FLOAT)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: percentage</t> 
<t>	Throughput</t> 
<t>1) Attribute name: exns_property: logi_throughput</t> 
<t>2) Attribute meaning: throughput of network equipment</t> 
<t>3) Data type: floating point number (XMLSchema.FLOAT)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: greater than zero</t> 
<t>	Maximum bandwidth</t> 
<t>1) Attribute name: exns_property: logi_max_bandwidth</t> 
<t>2) Attribute meaning: the maximum bandwidth of the network device</t> 
<t>3) Data type: floating point number (XMLSchema.FLOAT)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: greater than zero</t> 
<t>	Maximum number of connections</t> 
<t>1) Attribute name: exns_property: logi_max_link</t> 
<t>2) Attribute meaning: the maximum number of connections of the network device</t> 
<t>3) Data type: integer (XMLSchema.INT)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: greater than zero</t> 
<t>	Link rate</t> 
<t>1) Attribute name: exns_property: logi_link_rate</t> 
<t>2) Attribute meaning: the amount of information transmitted on the link per unit time</t> 
<t>3) Data type: floating point number (XMLSchema.FLOAT)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: greater than zero</t> 
<t>	Transmission delay</t> 
<t>1) Attribute name: exns_property: logi_transmission_delay</t> 
<t>2) Attribute meaning: transmission delay of network equipment</t> 
<t>3) Data type: floating point number (XMLSchema.FLOAT)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: greater than zero</t> 
<t>	Operating mode</t> 
<t>1) Attribute name: exns_property: logi_working_mode</t> 
<t>2) Attribute meaning: working mode of network equipment</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: full or half duplex</t> 
		  </section>
		       <section title="Attributes of network topology">
			   <t>The attributes of network topology are used to describe self-formed, human-made or on-demand configured topology features consisting of multiple resource entities and links containing a certain structure. Such attributes usually reflect the state, development and law of the static and dynamic structure of corresponding cyberspace resources.</t>
		  <t>	Autonomous domain name</t> 
<t>1) Attribute name: exns_property: logi_as_name</t> 
<t>2) Attribute meaning: the naming of the autonomous domain of the entity</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: global autonomous domain</t> 
<t>	Autonomous domain number</t> 
<t>1) Attribute name: exns_property: logi_asn</t> 
<t>2) Attribute meaning: the autonomous system asn number of the entity</t> 
<t>3) Data type: number (XMLSchema.INT)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: Global Autonomous System ASN numbering table</t> 
<t>	Autonomous domain type</t> 
<t>1) Attribute name: exns_property: logi_asn_type</t> 
<t>2) Attribute meaning: the AS type of the autonomous system to which the entity belongs</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: type of autonomous domain</t> 
<t>	ISP</t> 
<t>1) Attribute name: exns_property: isp</t> 
<t>2) Attribute meaning: entity's Internet service provider</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: no specific requirements</t> 
<t>	Route prefix</t> 
<t>1) Attribute name: exns_property: logi_routedprefix</t> 
<t>2) Attribute meaning: the route prefix of the entity</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: Specification format conforming to IP plus mask</t> 
<t>	Router level</t> 
<t>1) Attribute name: exns_property: logi_router_level</t> 
<t>2) Attribute meaning: The level of the router in the network, for example: access level, aggregation level, backbone level, and so on.</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: no specific requirements</t> 
<t>	Number of network nodes</t> 
<t>1) Attribute name: exns_property: logi_nodenumber</t> 
<t>2) Attribute meaning: the number of nodes in the entity's network</t> 
<t>3) Data type: integer (XMLSchema.INT)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: no specific requirements</t> 
<t>	Number of network sides</t> 
<t>1) Attribute name: exns_property: logi_edgenumber</t> 
<t>2) Attribute meaning: the number of connected sides in the entity's network</t> 
<t>3) Data type: integer (XMLSchema.INT)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: no specific requirements</t> 
<t>	Center degree</t> 
<t>1) Attribute name: exns_property: logi_ centerdegree</t> 
<t>2) Attribute meaning: the central degree of the network segment</t> 
<t>3) Data type: integer (XMLSchema.INT)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: no specific requirements</t> 
<t>	Node degree</t> 
<t>1) Attribute name: exns_property: logi_nodedegree</t> 
<t>2) Attribute meaning: the node degree of the network segment</t> 
<t>3) Data type: integer (XMLSchema.INT)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: no specific requirements</t> 
<t>	AS boundary</t> 
<t>1) Attribute name: exns_property: logi_as_edge</t> 
<t>2) Attribute meaning: whether the router is an as border router</t> 
<t>3) Data type: Boolean (XMLSchema.BOOLEAN)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: no specific requirements</t> 
<t>	Country gateway</t> 
<t>1) Attribute name: exns_property: logi_ nationalgateway</t> 
<t>2) Attribute meaning: whether the network device is a country gateway</t> 
<t>3) Data type: Boolean (XMLSchema.BOOLEAN)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: no specific requirements</t> 
<t>	Segment address</t> 
<t>1) Attribute name: exns_property: logi_ segment_address</t> 
<t>2) Attribute meaning: address information of the network segment</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: no specific requirements</t> 
<t>	Segment mask</t> 
<t>1) Attribute name: exns_property: logi_ segment _mask</t> 
<t>2) Attribute meaning: mask information of the network segment</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: no specific requirements</t> 
<t>	Network segment router number</t> 
<t>1) Attribute name: exns_property: logi_ segment_router</t> 
<t>2) Attribute meaning: router number information of the network segment</t> 
<t>3) Data type: integer (XMLSchema.INT)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: no specific requirements</t> 
<t>	Network segment IP number</t> 
<t>1) Attribute name: exns_property: logi_ segment _num</t> 
<t>2) Attribute meaning: the number of IP addresses contained in the network segment</t> 
<t>3) Data type: integer (XMLSchema.INT)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: no specific requirements</t> 
<t>	Neighbor network segment</t> 
<t>1) Attribute name: exns_property: logi_ segment _ neighbor</t> 
<t>2) Attribute meaning: whether the router is an anonymous router</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: no specific requirements</t> 
<t>	Topology</t> 
<t>1) Attribute name: exns_property: logi_ topological</t> 
<t>2) Attribute meaning: network topology</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: bus type, ring, star type</t> 
		  </section>
     <section title="Attributes of network security">
	 <t>The attributes of network security reflect the ability of entity itself to the expected and unexpected response to information from the data under the condition of operation, the influence of the exchange and transfer the source and damage, in a certain limits to avoid its function of integrity, and availability is damaged, or their own responsible for generation and transmission or processing the confidentiality, integrity and availability of information related to the characteristics of the damage. These attributes represent the self-protection and information protection capabilities of entities in the logical domain of cyberspace.</t>
	  <t>	Encryption Algorithm</t> 
<t>1) Attribute name: exns_property: logi_ safe_ encryptionalgorithm</t> 
<t>2) Attribute meaning: encryption algorithm for data transmission</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: AES, DES, RSA</t> 
<t>	Key length</t> 
<t>1) Attribute name: exns_property: logi_ safe_ keylength</t> 
<t>2) Attribute meaning: key length of the encryption algorithm</t> 
<t>3) Data type: integer (XMLSchema.INT)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: 64, 128, 256</t> 
<t>	Key replacement time</t> 
<t>1) Attribute name: exns_property: logi_ safe_ keychangetime</t> 
<t>2) Attribute meaning: key replacement time</t> 
<t>3) Data type: date type (XMLSchema.DATETIME)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: meet the GB/T 7408-1994 standard specification</t> 
<t>	Key distribution mechanism</t> 
<t>1) Attribute name: exns_property: logi_ safe_ keydistribution</t> 
<t>2) Attribute meaning: key replacement time</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: no specific requirements</t> 
<t>	Authentication method</t> 
<t>1) Attribute name: exns_property: logi_ safe_ authenticationmethod</t> 
<t>2) Attribute meaning: the identity authentication method adopted by the security system</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: one-way, two-way</t> 
<t>	Authentication mechanism</t> 
<t>1) Attribute name: exns_property: logi_ safe_ authenticationmechanism</t> 
<t>2) Attribute meaning: the identity authentication mechanism adopted by the security system</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: password, certificate, bio, hybrid</t> 
<t>	Authentication requirements</t> 
<t>1) Attribute name: exns_property: logi_ safe_ authenticationrequire</t> 
<t>2) Attribute meaning: identity authentication requirements adopted by the security system</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: USBKey, digital certificate, trusted module</t> 
<t>	Certificate type</t> 
<t>1) Attribute name: exns_property: logi_ safe_certificatetype</t> 
<t>2) Attribute meaning: the type of identity authentication certificate adopted by the security system</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: X.509, LDAP</t> 
<t>	Access control type</t> 
<t>1) Attribute name: exns_property: logi_ safe_ accesscontroltype</t> 
<t>2) Attribute meaning: the type of access control adopted by the security system</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: MAC, DAC, RBAC, ABAC, IBAC</t> 
<t>	Security policy level</t> 
<t>1) Attribute name: exns_property: logi_ safe_ policylevel</t> 
<t>2) Attribute meaning: the policy level adopted by the security system</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: high, medium and low</t> 
<t>	Patch update time</t> 
<t>1) Attribute name: exns_property: logi_ safe_ patchupdatetime</t> 
<t>2) Attribute meaning: system patch update time</t> 
<t>3) Data type: date type (XMLSchema.DATETIME)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: meet the GB/T 7408-1994 standard specification</t> 
<t>	Patch installation</t> 
<t>1) Attribute name: exns_property: logi_ safe_ patchinfo</t> 
<t>2) Attribute meaning: system patch installation patch, including installed patches and no patches installed</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: no specific requirements</t> 
<t>	Patch source address</t> 
<t>1) Attribute name: exns_property: logi_ safe_ patchaddr</t> 
<t>2) Attribute meaning: the address of the system patch download</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: no specific requirements</t> 
<t>	Patch update mechanism</t> 
<t>1) Attribute name: exns_property: logi_ safe_ patchmethod</t> 
<t>2) Attribute meaning: the way the system patch is updated</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: subscription, push, offline</t> 
<t>	Firewall type</t> 
<t>1) Attribute name: exns_property: logi_ safe_ firewalltype</t> 
<t>2) Attribute meaning: the way the system patch is updated</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: operating system comes with, host firewall, no firewall</t> 
<t>	Intrusion detection type</t> 
<t>1) Attribute name: exns_property: logi_ safe_idstype</t> 
<t>2) Attribute meaning: type of intrusion detection adopted by the security system</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: None, HIDS, NIDS, IPS</t> 
<t>	Host monitoring type</t> 
<t>1) Attribute name: exns_property: logi_ safe_ monitortype</t> 
<t>2) Attribute meaning: Host monitoring type adopted by the security system</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: None, Behavior, Network, All</t> 
<t>	Security audit mechanism</t> 
<t>1) Attribute name: exns_property: logi_ safe_ audittype</t> 
<t>2) Attribute meaning: the type of security audit adopted by the security system</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: None, traffic, protocol, behavior</t> 
<t>	Security management port</t> 
<t>1) Attribute name: exns_property: logi_ safe_ adminport</t> 
<t>2) Attribute meaning: the management interface provided by the security system</t> 
<t>3) Data type: integer (XMLSchema.INT)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: 0-65535</t> 
<t>	Security management method</t> 
<t>1) Attribute name: exns_property: logi_ safe_ admintype</t> 
<t>2) Attribute meaning: the security management organization or company adopted by the security system</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: no specific requirements</t> 
<t>	Security management mechanism</t> 
<t>1) Attribute name: exns_property: logi_ safe_ adminmethod</t> 
<t>2) Attribute meaning: the security management mechanism adopted by the security system</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: peer, cascade, autonomous</t> 

	  </section>
		</section>
		   <section title="Cognitive domain attributes">
		   <t>The subject attributes in the cognitive domain are quite different from the physical domain and the logical domain, mainly reflecting the knowledge, thoughts, emotions and beliefs acquired, exchanged and formed by the projected entities in cyberspace in the form of virtual subjects in the cognitive domain. Due to the use of the diversity of the subject and the object information semantic complexity greatly deepened, and the related attributes with more categories, mainly includes the basic attributes of the virtual subject, the basic attributes of the projected entity, the behavioral attributes of the virtual subject, and the projection. The emotional attributes of the projected entity, the conceptual attributes of the projected entity, the attributes of the web service content, and the attributes of the data resource content, etc.</t>
						   <section title="Cognitive domain attributes">
						   <t>The basic attributes of the virtual subject are used to describe the effective and meaningful assets, status and activity information of the virtual subject only in the cyberspace category. This information is stored and maintained by various network services, and thus has the characteristics of volatility and variability.</t>
			   <t>	Virtual principal account</t> 
<t>1) Attribute name: exns_property: cogi_virtualsubject_id</t> 
<t>2) Attribute meaning: virtual subject account</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: required</t> 
<t>5) Range of values: no specific requirements</t> 
<t>	Virtual principal password</t> 
<t>1) Attribute name: exns_property: cogi_virtualsubject_password</t> 
<t>2) Attribute meaning: the password of the virtual subject's account</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: no specific requirements</t> 
<t>	Virtual subject location</t> 
<t>1) Attribute name: exns_property: cogi_virtualsubject_place</t> 
<t>2) Attribute meaning: the login location of the virtual subject</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: meet the GB/T 2659-2000 standard specification</t> 
<t>	Virtual body login time</t> 
<t>1) Attribute name: exns_property: cogi_virtualsubject_date</t> 
<t>2) Attribute meaning: login time of virtual subject</t> 
<t>3) Data type: date type (XMLSchema.DATETIME)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: meet the GB/T 7408-1994 standard specification</t> 
<t>	Virtual subject online time</t> 
<t>1) Attribute name: exns_property: cogi_virtualsubject_onelinetime</t> 
<t>2) Attribute meaning: online time of virtual subject</t> 
<t>3) Data type: date type (XMLSchema.DATETIME)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: meet the GB/T 7408-1994 standard specification</t> 
<t>	Virtual subject registration time</t> 
<t>1) Attribute name: exns_property: cogi_virtualsubject_registeddate</t> 
<t>2) Attribute meaning: registration time of virtual subject</t> 
<t>3) Data type: date type (XMLSchema.DATETIME)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: meet the GB/T 7408-1994 standard specification</t> 
<t>	Virtual principal name</t> 
<t>1) Attribute name: exns_property: cogi_virtualsubject_name</t> 
<t>2) Attribute meaning: the name of the virtual subject</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: no specific requirements</t> 
<t>	Virtual body type</t> 
<t>1) Attribute name: exns_property: cogi_virtualsubject_type</t> 
<t>2) Attribute meaning: type of virtual subject</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: no specific requirements</t> 
<t>	Virtual subject role</t> 
<t>1) Attribute name: exns_property: virtualsubject_function</t> 
<t>2) Attribute meaning: virtual subject works in virtual group</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: no specific requirements</t> 
<t>	Virtual subject activity</t> 
<t>1) Attribute name: exns_property: cogi_virtualsubject_activity</t> 
<t>2) Attribute meaning: the activity of the virtual subject in the virtual group</t> 
<t>3) Data type: floating point type (XMLSchema.FLOAT)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: no specific requirements</t> 
<t>	Virtual principal platform</t> 
<t>1) Attribute name: exns_property: cogi_virtualsubject_platform</t> 
<t>2) Attribute meaning: the platform where the virtual subject is located</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: no specific requirements</t> 
			   </section>
	  <section title="Basic attributes of the projected entity">
	  <t>The basic attributes of the projected entity are used to characterize the various characteristics of natural persons that exist in the physical world that participate in the activities of cyberspace, use the services of cyberspace, and manage the states of cyberspace. The basic attributes of the projected entity can guide and regulate the basic attributes of related virtual subjects.</t>
	  <t>	The name of the projection entity</t> 
<t>1) Attribute name: exns_property: cogi_mappingentity_name</t> 
<t>2) Attribute meaning: the name of the projection entity</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: no specific requirements</t> 
<t>	Projecting entity gender</t> 
<t>1) Attribute name: exns_property: cogi_mappingentity_sex</t> 
<t>2) Attribute meaning: the gender of the projected entity</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: male/female</t> 
<t>	Projection entity's ID number</t> 
<t>1) Attribute name: exns_property: cogi_mappingentity_id</t> 
<t>2) Attribute meaning: the document number of the projection entity</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: Code number specification for nationality</t> 
<t>	Projection entity occupation</t> 
<t>1) Attribute name: exns_property: cogi_mappingentity_profession</t> 
<t>2) Attribute meaning: the occupation of the projection entity</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: no specific requirements</t> 
<t>	The social level of the projected entity</t> 
<t>1) Attribute name: exns_property: cogi_mappingentity_sociallevel</t> 
<t>2) Attribute meaning: the social level of the projected entity</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: medium, low, high level</t> 
<t>	The age of the projected entity</t> 
<t>1) Attribute name: exns_property: cogi_mappingentity_age</t> 
<t>2) Attribute meaning: age of the projection entity</t> 
<t>3) Data type: integer (XMLSchema.INT)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: greater than zero</t> 
<t>	Nationality of the projected entity</t> 
<t>1) Attribute name: exns_property: cogi_mappingentity_nationality</t> 
<t>2) Attribute meaning: nationality of the projection entity</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: meet the GB/T 2659-2000 standard specification</t> 
<t>	The language of the projected entity</t> 
<t>1) Attribute name: exns_property: cogi_mappingentity_language</t> 
<t>2) Attribute meaning: common language of the projection entity</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: no specific requirements</t> 
<t>	Projecting entity accent</t> 
<t>1) Attribute name: exns_property: mappingentity_accent</t> 
<t>2) Attribute meaning: accent of the projected entity</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: no specific requirements</t> 
<t>	Projecting the skin's skin tone</t> 
<t>1) Attribute name: exns_property: cogi_mappingentity_ colour</t> 
<t>2) Attribute meaning: the skin color of the projected entity</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: no specific requirements</t> 
<t>	Projected entity</t> 
<t>1) Attribute name: exns_property: cogi_mappingentity_ posture</t> 
<t>2) Attribute meaning: the body state of the projected entity</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: no specific requirements</t> 
<t>	The health of the projected entity</t> 
<t>1) Attribute name: exns_property: cogi_mappingentity_ health</t> 
<t>2) Attribute meaning: the health of the projected entity</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: excellent / good / poor</t> 
<t>	Projecting entity intelligence</t> 
<t>1) Attribute name: exns_property: cogi_mappingentity_ intelligence</t> 
<t>2) Attribute meaning: the intelligence level of the projected entity</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: excellent / good / poor</t> 

	  </section>
	  	  <section title="Behavioral attributes of the virtual subject">
		  <t>The behavioral attributes of the virtual subject are used to describe the behavioral choices, behavioral rules, behavioral effects and other characteristics of the virtual subject when it participates in various activities in the cyberspace, and represent the trajectory and influence of the virtual subject in the cyberspace.</t>
<t>	Virtual subject access preferences</t> 
<t>1) Attribute name: exns_property: cogi_mappingentity_preference</t> 
<t>2) Attribute meaning: a frequently visited URL that characterizes a virtual subject</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: URL</t> 
<t>	Total number of tweets for virtual subjects</t> 
<t>1) Attribute name: exns_property: cogi_mappingentity_blog_num</t> 
<t>2) Attribute meaning: total number of tweets that represent virtual subjects</t> 
<t>3) Data type: integer (XMLSchema.INT)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: greater than zero</t> 
<t>	Original tweet proportion of virtual subject</t> 
<t>1) Attribute name: exns_property: cogi_mappingentity_blog_original</t> 
<t>2) Attribute meaning: the proportion of original tweets that characterize the virtual subject</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: percentage</t> 
<t>	Number of concerns of the virtual subject</t> 
<t>1) Attribute name: exns_property: cogi_mappingentity_blog_concerns</t> 
<t>2) Attribute meaning: the number of concerns that characterize the essay of the virtual subject</t> 
<t>3) Data type: integer (XMLSchema.INT)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: greater than zero</t> 
<t>	Number of fans of virtual subjects</t> 
<t>1) Attribute name: exns_property: cogi_mappingentity_blog_fans</t> 
<t>2) Attribute meaning: the number of fans who represent the virtual subject</t> 
<t>3) Data type: integer (XMLSchema.INT)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: greater than zero</t> 
<t>	Topic engagement of virtual subjects</t> 
<t>1) Attribute name: exns_property: cogi_mappingentity_blog_participation</t> 
<t>2) Attribute meaning: characterizing the topic participation of the virtual subject</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: strong, general, indifferent</t> 
<t>	Text usage preferences of virtual subjects</t> 
<t>1) Attribute name: exns_property: cogi_mappingentity_text_preference</t> 
<t>2) Attribute meaning: characterizing the text usage preferences of the virtual subject</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: URL</t> 
<t>	Average dynamic number of virtual subjects</t> 
<t>1) Attribute name: exns_property: cogi_mappingentity_dynamic_num</t> 
<t>2) Attribute meaning: the average dynamic number of the virtual subject</t> 
<t>3) Data type: integer (XMLSchema.INT)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: greater than zero</t> 
<t>	Number of comments by virtual subject</t> 
<t>1) Attribute name: exns_property: cogi_mappingentity_blog_comment</t> 
<t>2) Attribute meaning: the number of Weibo comments that represent the virtual subject</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: URL</t> 
<t>	The tweet of the virtual subject</t> 
<t>1) Attribute name: exns_property: cogi_mappingentity_blog_ praisenum</t> 
<t>2) Attribute meaning: the microblogging point number that represents the virtual subject</t> 
<t>3) Data type: integer (XMLSchema.INT)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: greater than zero</t> 
<t>	The number of tweets forwarded by the virtual principal</t> 
<t>1) Attribute name: exns_property: cogi_mappingentity_blog_forwardnum</t> 
<t>2) Attribute meaning: the number of tweets forwarded to the virtual subject</t> 
<t>3) Data type: integer (XMLSchema.INT)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: greater than zero</t> 	  
		  </section>
	  	  <section title="Emotional attributes of the projected entity">
		  <t>The emotional attributes of the projected entity are used to characterize the long-term, relatively stable inner emotional tendency and temperament characteristics of the projected entity formed in the growth and living environment, which can directly and indirectly affect the concept, view, thought and behavior of the projected entity in the cyberspace. The difference between emotional attributes and conceptual attributes is that emotional attributes are often contained by themselves, from the outside to the inside, while conceptual attributes are summarized from the inside to the outside for the characteristics of objects and objects.</t>
			<t>	Reflexive spirit of the projection entity</t> 
<t>1) Attribute name: exns_property: cogi_mappingentity_spirit</t> 
<t>2) Attribute meaning: the degree of rebellious spirit of the projected entity</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: strong, general, weak</t> 
<t>	Projection entity happiness</t> 
<t>1) Attribute name: exns_property: cogi_mappingentity_ happiness</t> 
<t>2) Attribute meaning: the degree of characterization of the happiness of the projected entity</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: strong, general, unhappy</t> 
<t>	Projection entity pride</t> 
<t>1) Attribute name: exns_property: cogi_mappingentity_ride</t> 
<t>2) Attribute meaning: the degree of characterization of the happiness of the projected entity</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: strong, general, inferior</t> 
<t>	Projection entity security</t> 
<t>1) Attribute name: exns_property: cogi_mappingentity_ safty</t> 
<t>2) Attribute meaning: the degree of security of the projected entity</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: strong, general, insecure</t> 
<t>	Projection entity</t> 
<t>1) Attribute name: exns_property: cogi_mappingentity_ belonging</t> 
<t>2) Attribute meaning: the degree of attribution of the sense of belonging of the projected entity</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: strong, general, no sense of belonging</t> 
<t>	Projection entity's sense of humor</t> 
<t>1) Attribute name: exns_property: cogi_mappingentity_ humor</t> 
<t>2) Attribute meaning: the degree of humor that characterizes the projected entity</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: humor, general, old-fashioned</t> 
<t>	Projection entity's internal and external directions</t> 
<t>1) Attribute name: exns_property: cogi_mappingentity_ internal</t> 
<t>2) Attribute meaning: the degree of internal and external characterization of the projected entity</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: introverted, general, outgoing</t> 
<t>	Projection entity's self-esteem</t> 
<t>1) Attribute name: exns_property: cogi_mappingentity_ selfrespect</t> 
<t>2) Attribute meaning: the degree of self-esteem of the projected entity</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: strong, general, no self-esteem</t> 
<t>	Projection entity self-confidence</t> 
<t>1) Attribute name: exns_property: cogi_mappingentity_ selfconfidence</t> 
<t>2) Attribute meaning: the degree of self-confidence that characterizes the projected entity</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: strong, general, no confidence</t> 
			</section>
			<section title="Conceptual attributes of the projected entity">
			<t>The conceptual attribute of the projected entity is used to describe the tensional views, opinions and choices of the projected entity for various objects, relationships, phenomena and laws in the real world, the virtual world and the spiritual world, which are the psychological basis for virtual subjects to carry out various activities in cyberspace. The difference between the conceptual attribute and the affective attribute is that the conceptual attribute must contain one or more object objects, which are concluded from the inner to the outer features, while the affective attribute is usually independent of the object objects, while the projected entity itself contains the mental state from the outer to the inner.</t>
			<t>	Projection entity patriotism</t> 
<t>1) Attribute name: exns_property: cogi_mappingentity_patriotism</t> 
<t>2) Attribute meaning: the degree of love of the motherland that represents the projection entity</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: fanaticism, affection, generality, indifference, disgust</t> 
<t>	The political claim of the projection entity</t> 
<t>1) Attribute name: exns_property: cogi_mappingentity_ political</t> 
<t>2) Attribute meaning: the political claim of the projection entity</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: no specific requirements</t> 
<t>	The ideology orientation of the projection entity</t> 
<t>1) Attribute name: exns_property: cogi_mappingentity_ ideology</t> 
<t>2) Attribute meaning: the ideology of the projected entity</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: no specific requirements</t> 
<t>	Party orientation of the projection entity</t> 
<t>1) Attribute name: exns_property: cogi_mappingentity_ party</t> 
<t>2) Attribute meaning: the party in which the projection entity participates</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: no specific requirements</t> 
<t>	Social group orientation of projection entities</t> 
<t>1) Attribute name: exns_property: cogi_mappingentity_ group</t> 
<t>2) Attribute meaning: social groups in which the projection entity participates</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: no specific requirements</t> 
<t>	Projection entity belief</t> 
<t>1) Attribute name: exns_property: cogi_mappingentity_ belief</t> 
<t>2) Attribute meaning: the belief of the projection entity</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: no specific requirements</t> 
<t>	Projection entity values</t> 
<t>1) Attribute name: exns_property: cogi_mappingentity_ values</t> 
<t>2) Attribute meaning: the belief of the projection entity</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: no specific requirements</t> 
<t>	Projection entity's outlook on life</t> 
<t>1) Attribute name: exns_property: cogi_mappingentity_ life</t> 
<t>2) Attribute meaning: the outlook of life of the projected entity</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: no specific requirements</t> 
			</section>
			   <section title="Attributes of the web service content">
			   <t>The attributes of the web service content are used to characterize the types, scopes, capabilities, mechanisms of resource entities to generate, receive, accommodate, transmit and provide information content at the cognitive level. As the carrier of the data resource, the attributes of the network service content determine the basic information of relevant forms, structures, uses and virtual subjects of the data resources on it.</t>
<t>	The name of the service content</t> 
<t>1) Attribute name: exns_property: cogi_networkservice_ name</t> 
<t>2) Attribute meaning: the name of the external service provided by the network service</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: no specific requirements</t> 
<t>	Service content function</t> 
<t>1) Attribute name: exns_property: cogi_networkservice_function</t> 
<t>2) Attribute meaning: external service function of network service</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: no specific requirements</t> 
<t>	Audience of service content</t> 
<t>1) Attribute name: exns_property: cogi_networkservice_ audience</t> 
<t>2) Attribute meaning: the audience of the external service provided by the network service</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: no specific requirements</t> 
<t>	Publisher of service content</t> 
<t>1) Attribute name: exns_property: cogi_networkservice_ publisher</t> 
<t>2) Attribute meaning: the publisher of the external service of the network service</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: no specific requirements</t> 
<t>	Editor of the service content</t> 
<t>1) Attribute name: exns_property: cogi_networkservice_ editor</t> 
<t>2) Attribute meaning: the editor of the external service of the network service</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: no specific requirements</t> 
<t>	Form of service content</t> 
<t>1) Attribute name: exns_property: cogi_networkservice_ type</t> 
<t>2) Attribute meaning: the form of external service provided by network service</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: no specific requirements</t> 
<t>	Service content release time</t> 
<t>1) Attribute name: exns_property: cogi_networkservice_ date</t> 
<t>2) Attribute meaning: the release time of the content of the network service</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: meet the GB/T 7408-1994 standard specification</t> 
		  
		  </section>
   <section  title="Attributes of the data resource content">
   <t>The attributes of the data resource content are used to characterize the various characteristics that the data resource can be recognized by other projected entities at the content level. It can be used to establish a wide range of correlations between content and content, between content and resources, and between content and projected entities/virtual subjects.</t>
   <t>	Content publisher</t> 
<t>1) Attribute name: exns_property: cogi_content_ publisher</t> 
<t>2) Attribute meaning: the content of the cloth</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: no specific requirements</t> 
<t>	Speed  of content</t> 
<t>1) Attribute name: exns_property: cogi_content_ speed</t> 
<t>2) Attribute meaning: the speed of content propagation</t> 
<t>3) Data type: floating point number (XMLSchema.FLOAT)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: no specific requirements</t> 
<t>	Emotional color of content</t> 
<t>1) Attribute name: exns_property: cogi_content_ emotion</t> 
<t>2) Attribute meaning: the emotional color conveyed by the content</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: no specific requirements</t> 
<t>	Content impact</t> 
<t>1) Attribute name: exns_property: cogi_content_ effect</t> 
<t>2) Attribute meaning: the social influence brought by the content</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: no specific requirements</t> 
<t>	Content evaluation</t> 
<t>1) Attribute name: exns_property: cogi_content_ evaluate</t> 
<t>2) Attribute meaning: evaluation of content</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: no specific requirements</t> 
<t>	Content operation form</t> 
<t>1) Attribute name: exns_property: cogi_content_ form</t> 
<t>2) Attribute meaning: the operating form of the content</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: no specific requirements</t> 
<t>	Legality of content</t> 
<t>1) Attribute name: exns_property: cogi_content_ legality</t> 
<t>2) Attribute meaning: whether the content complies with relevant laws and regulations</t> 
<t>3) Data type: Boolean (XMLSchema.BOOLEN)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: no specific requirements</t> 
<t>	Value orientation of content</t> 
<t>1) Attribute name: exns_property: cogi_content_ value</t> 
<t>2) Attribute meaning: content value orientation</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: no specific requirements</t> 
<t>	Content ethics</t> 
<t>1) Attribute name: exns_property: cogi_content_ ethics</t> 
<t>2) Attribute meaning: the ethical influence of content</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: no specific requirements</t> 
<t>	Field of content</t> 
<t>1) Attribute name: exns_property: cogi_content_ domain</t> 
<t>2) Attribute meaning: the domain of the content</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: no specific requirements</t> 
<t>	Political color of content</t> 
<t>1) Attribute name: exns_property: cogi_content_ political</t> 
<t>2) Attribute meaning: the political color of content</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: no specific requirements</t> 
<t>	Ideology of content</t> 
<t>1) Attribute name: exns_property: cogi_content_ ideology</t> 
<t>2) Attribute meaning: the ideology of content reaction</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: no specific requirements</t> 
<t>	Authenticity of content</t> 
<t>1) Attribute name: exns_property: cogi_content_ truth</t> 
<t>2) Attribute meaning: the authenticity of the content</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: no specific requirements</t> 

   </section>
		   </section>
		      <section  title="social domain attributes">
			  	<t>The social domain attribute is used to describe various social groups (especially virtual crowd) with strong sociality in the cyberspace, and to describe the new features that emerge after multiple virtual subjects gather into groups due to internal factors such as emotions and concepts, or external factors such as events and pressures.</t>		  
				      <section  title="Attributes of virtual crowd">
			 <t>The virtual crowd refers to a new type of organization with the same interest and similar ideas formed by the virtual network as the medium and relying on the network social media. It consists of two layers: one is the networking of the realistic group, which is the extension of the realistic group in the cyberspace; the second is the group born based on the network, that is, the group bound by and because of the network.</t>
<t>	Organization name of the virtual crowd</t> 
<t>1) Attribute name: exns_property: soci_virtualcrowd_ name</t> 
<t>2) Attribute meaning: the organization name of the virtual crowd</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: no specific requirements</t> 
<t>	Common interest of the virtual crowd</t> 
<t>1) Attribute name: exns_property: soci_virtualcrowd _ support</t> 
<t>2) Attribute meaning: the common interest of the virtual crowd, the source of formation</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: no specific requirements</t> 
<t>	Virtual crowd ID</t> 
<t>1) Attribute name: exns_property: soci_virtualcrowd _ id</t> 
<t>2) Attribute meaning: the unique ID of the virtual crowd in cyberspace</t> 
<t>3) Data type: integer (XMLSchema.INT)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: no specific requirements</t> 
<t>	Virtual crowd gathering place</t> 
<t>1) Attribute name: exns_property: soci_virtualcrowd _ place</t> 
<t>2) Attribute meaning: virtual crowd in the network gathering place, WeChat group / Weibo / forum / chat room / live room</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: no specific requirements</t> 
<t>	Virtual population connection strength</t> 
<t>1) Attribute name: exns_property: soci_virtualcrowd _ link</t> 
<t>2) Attribute meaning: the strength of the connection of the virtual crowd</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: compact, general, loose</t> 
<t>	Opinion leader of the virtual crowd</t> 
<t>1) Attribute name: exns_property: soci_virtualcrowd _ leader</t> 
<t>2) Attribute meaning: the leader of group thinking, behavior or speech</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: no specific requirements</t> 
<t>	Secondary leader of the virtual crowd</t> 
<t>1) Attribute name: exns_property: soci_virtualcrowd _ subleader</t> 
<t>2) Attribute meaning: the second-level leader of group thinking, behavior or speech</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: no specific requirements</t> 
<t>	Active time of the virtual crowd</t> 
<t>1) Attribute name: exns_property: soci_virtualcrowd _ activetime</t> 
<t>2) Attribute meaning: the usual time for group status update</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: meet the GB/T 7408-1994 standard specification</t> 
<t>	Offline activities of virtual people</t> 
<t>1) Attribute name: exns_property: soci_virtualcrowd _ Offline</t> 
<t>2) Attribute meaning: whether offline activities</t> 
<t>3) Data type: Boolean (XMLSchema.BOOLEN)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: no specific requirements</t> 
<t>	Virtual population mobility</t> 
<t>1) Attribute name: exns_property: soci_virtualcrowd _ mobility</t> 
<t>2) Attribute meaning: stability of group members, strong, medium and weak</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: no specific requirements</t> 
<t>	Virtual population vulnerability</t> 
<t>1) Attribute name: exns_property: soci_ virtualcrowd _ vulnerability</t> 
<t>2) Attribute meaning: the group members' thoughts are shaken, strong, medium and weak</t> 
<t>3) Data type: string (XMLSchema.STRING)</t> 
<t>4) Constraint: optional</t> 
<t>5) Range of values: no specific requirements</t> 
		
		</section>
		</section>

		
		</section>


   

     
   

   

   <section anchor="Acknowledgements" title="Acknowledgements">
<t>With gratitude, the authors would like to thank the support, encouragement, and help of China Electronic Technology Group Corporation thirtieth Research institute and Tsinghua.University. And we thanks to the following persons: Jilong Wang, Congcong Miao, Yujin Zhou,Jiang Zhang, Hui Yang, devoted their hardworking and effort.</t>
    
   </section>
    
   <!-- Possibly a 'Contributors' section ... -->

   <section anchor="IANA" title="IANA Considerations">
     <t>This memo includes no request to IANA.</t>
   </section>

   <section anchor="Security" title="Security Considerations">
     <t>This document only defines a framework for network resource property description. This document itself does not directly introduce security issues.</t>
   </section>
   
 </middle>
  
  
  

 <!--  *****BACK MATTER ***** -->

 <back>
   <!-- References split into informative and normative -->

   <!-- There are 2 ways to insert reference entries from the citation libraries:
    1. define an ENTITY at the top, and use "ampersand character"RFC2629; here (as shown)
    2. simply use a PI "less than character"?rfc include="reference.RFC.2119.xml"?> here
       (for I-Ds: include="reference.I-D.narten-iana-considerations-rfc2434bis.xml")

    Both are cited textually in the same manner: by using xref elements.
    If you use the PI option, xml2rfc will, by default, try to find included files in the same
    directory as the including file. You can also define the XML_LIBRARY environment variable
    with a value containing a set of directories to search.  These can be either in the local
    filing system or remote ones accessed by http (http://domain/dir/... ).-->

   <references title="Normative References">
     <!--?rfc include="http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml"?-->
    

     <reference anchor="RFC3275">
       <!-- the following is the minimum to make xml2rfc happy -->
       <front>
         <title>Extensible Markup Language) XML-Signature Syntax and Processing</title>

         <author initials="D." surname="Eastlake 3rd">
           <organization>Harvard University</organization>
         </author>

         <date month="March" year="2002" />
       </front>
       <seriesInfo name="RFC" value="3275" />
     </reference>
    
    
     <reference anchor="RFC3870">
       <!-- the following is the minimum to make xml2rfc happy -->
       <front>
         <title>Application/rdf+xml Media Type Registration</title>
         
         <author initials="A." surname="Swartz">
           <organization>RFC</organization>
         </author>
           
         <date month="September" year="2004" />
       </front>
       <seriesInfo name="RFC" value="3870" />
     </reference>
     
     <reference anchor="RFC3688">
       <!-- the following is the minimum to make xml2rfc happy -->
       <front>
         <title>The IETF XML Registry
         </title>
         
         <author initials="M." surname="Mealling">
           <organization></organization>
         </author>
         
         <date month="January" year="2004" />
       </front>
       <seriesInfo name="RFC" value="3688" />
     </reference>
     
     <reference anchor="RFC2396">
       <!-- the following is the minimum to make xml2rfc happy -->
       <front>
         <title>Uniform Resource Identifiers (URI): Generic Syntax
         </title>
         
         <author initials="T." surname="Berners-Lee">
           <organization></organization>
         </author>
         
         <date month="August" year="1998" />
       </front>
       <seriesInfo name="RFC" value="2396" />
     </reference>
     
     
     <reference anchor="RFC2119">
       <!-- the following is the minimum to make xml2rfc happy -->
       <front>
         <title>Key words for use in RFCs to Indicate Requirement Levels
         </title>
         
         <author initials="S." surname="Bradner">
           <organization></organization>
         </author>
         
         <date month="March" year="1997" />
       </front>
       <seriesInfo name="RFC" value="2119" />
     </reference>    
     
   </references>
   
   

  


   

   <!-- Change Log

v00 2006-03-15  EBD   Initial version

v01 2006-04-03  EBD   Moved PI location back to position 1 -
                     v3.1 of XMLmind is better with them at this location.
v02 2007-03-07  AH    removed extraneous nested_list attribute,
                     other minor corrections
v03 2007-03-09  EBD   Added comments on null IANA sections and fixed heading capitalization.
                     Modified comments around figure to reflect non-implementation of
                     figure indent control.  Put in reference using anchor="DOMINATION".
                     Fixed up the date specification comments to reflect current truth.
v04 2007-03-09 AH     Major changes: shortened discussion of PIs,
                     added discussion of rfc include.
v05 2007-03-10 EBD    Added preamble to C program example to tell about ABNF and alternative 
                     images. Removed meta-characters from comments (causes problems).

v06 2010-04-01 TT     Changed ipr attribute values to latest ones. Changed date to
                     year only, to be consistent with the comments. Updated the 
                     IANA guidelines reference from the I-D to the finished RFC.  -->
 </back>
</rfc>