Page 748 - Shaping smarter and more sustainable cities - Striving for sustainable development goals
P. 748

subset of XAS. XAS and XAR differ because XAR does not contain data as contents. All transactions
            in this infrastructure utilize the XAS and its subset, XAR. XAS is designed according to Extensible
            Markup Language (XML). Figure 8.4.2 lists an example of D‐XAS. It includes the information to enable
            anonymization,  including  combinations  of  the  sensitive  attribute  names  and  quasi‐identifiers,
            permitted anonymization methods and levels, and data attributes such as created date, updated
            date and history, ownership, copyrights, comments, and others. Figure 8.4.3 lists an example of a P‐
            XAR. It does not contain raw data; it only declares the required anonymization methods and levels.
            To enable masking or generalization processes, it can define the delimiter for distinguishing data
            sections.  In  this  example,  "BirthDay"  is  split  utilizing  the  '‐'  character.  During  the  anonymizing
            process, the character is used to define the generalization boundary. If the data employs a general
            and standardized format, for example, BirthDay should be separated by '‐' it can generalize the data
            entry by referring to the default rule. As an additional feature, the data provider may publish data
            samples without data publishing limits to publicize the data's availability. This open information is
            termed "open attribute." This open attribute can be declared in the data entry.

                                 1 <?xml version="1.0" encoding="utf‐8"?>
                                 2 <?xml‐anonymize type="text/xas" href="p‐xar.xas"?>
                                 3 <list>
                                 4      <rdf:RDF   xmlns:rdf="http://www.w3.org/1999/02/22‐rdf‐syntax‐ns#"
                               xmlns:v="http://www.w3.org/2006/vcard/ns#">
                                 5   <v:Kind rdf:about = "http://foo.com/me/hogehoge">
                                 6    <v:fn>Hoge Foo</v:fn>
                                 7    <v:bday>1980‐01‐01</v:bday>
                                 8    <v:hasTelephone>
                                 9     <rdf:Description>
                               10      <rdf:value>+81‐45‐566‐1454</rdf:value>
                               11      <rdf:type rdf:resource="http://www.w3.org/2006/vcard/ns#Work"/>
                               12      <rdf:type rdf:resource="http://www.w3.org/2006/vcard/ns#Voice"/>
                               13     </rdf:Description>
                               14    </v:hasTelephone>
                               15    <v:hasAddress>
                               16     <rdf:Description>
                               17      <v:street‐address>123‐45 Hoge Village</v:street‐address>
                               18      <v:locality>FooCity</v:locality>
                               19      <v:postal‐code>5555</v:postal‐code>
                               20      <v:country‐name>Japan</v:country‐name>
                               21     </rdf:Description>
                               22    </v:hasAddress>
                               23   </v:Kind>
                               24  </rdf:RDF>
                               25  <OfficeScale>100ha</OfficeScale>
                               26  <PowerConsumption>10kWh</PowerConsumption>
                               27
                               28      <rdf:RDF   xmlns:rdf="http://www.w3.org/1999/02/22‐rdf‐syntax‐ns#"
                               xmlns:v="http://www.w3.org/2006/vcard/ns#">
                               29   <v:Kind rdf:about = "http://foo.com/me/db">

                               Fig. 8.4.2 D‐XAS Example (Extract)








            738                                                      ITU‐T's Technical Reports and Specifications
   743   744   745   746   747   748   749   750   751   752   753