Skip to content

Commit

Permalink
update 2.1.1
Browse files Browse the repository at this point in the history
  • Loading branch information
EmielPwC committed Jan 31, 2024
1 parent 7892d55 commit aea7b4d
Show file tree
Hide file tree
Showing 8 changed files with 763 additions and 3,547 deletions.
488 changes: 230 additions & 258 deletions releases/2.1.1/context/core-person-ap.jsonld

Large diffs are not rendered by default.

488 changes: 230 additions & 258 deletions releases/2.1.1/context/core-person-ap_en.jsonld

Large diffs are not rendered by default.

13 changes: 7 additions & 6 deletions releases/2.1.1/index.html
Original file line number Diff line number Diff line change
Expand Up @@ -228,6 +228,7 @@
<section id="abstract">
<h2>Abstract</h2>
The Core Person Vocabulary is a simplified, reusable and extensible data model that captures the fundamental characteristics of a Person.
</section>


<section id="specintro">
Expand Down Expand Up @@ -555,7 +556,7 @@ <h3 id="Address">
<br/><br/>
Many datasets that include address data as one piece of information about something else are likely to have that data in simpler formats. These might be tailored to the specific need of the dataset, follow a national norm, or make use of a standard like vCard.
<br/><br/>
To provide maximum flexibility in the Core Vocabulary, whilst remaining interoperable with INSPIRE Address Guidelines (which EU Member States are obliged to use), the Core Location Vocabulary provides the extra property of full address and makes use of INSPIRE's addressID.
To provide maximum flexibility in the Core Vocabulary, whilst remaining interoperable with <a href="https://joinup.ec.europa.eu/collection/inspire/solution/inspire-data-specifications-addresses-guidelines-v301">INSPIRE Address Guidelines</a> (which EU Member States are obliged to use), the Core Location Vocabulary provides the extra property of full address and makes use of INSPIRE's addressID.


</td>
Expand Down Expand Up @@ -1320,7 +1321,7 @@ <h3 id="Identifier">

<tr id="Identifier.identifies"
typeof="rdfs:Property"
resource="http://www.w3.org/ns/adms#identifies"
resource="http://data.europa.eu/m8g/identifies"
class="class mandatory">
<td>
<a href="https://github.com/SEMICeu/Core-Person-Vocabulary/issues/new?title=Issue%20for%20identifies%20in%20Identifier&body=Explain%20your%20issue%20for%20https://semiceu.github.io/Core-Person-Vocabulary/releases/2.1.1/%23Identifier.identifies" target="_blank" rel="noopener noreferrer" >
Expand All @@ -1329,9 +1330,9 @@ <h3 id="Identifier">
</a>
</td>
<td>
<a href="http://www.w3.org/ns/adms#identifies"
<a href="http://data.europa.eu/m8g/identifies"
data-toggle="tooltip"
data-content="http://www.w3.org/ns/adms#identifies"
data-content="http://data.europa.eu/m8g/identifies"
data-placement="right">
identifies</a>
</td>
Expand Down Expand Up @@ -3440,7 +3441,7 @@ <h3>Lexicalisation rules</h3>
SEMIC uses and will use the RDFS lexicalisation for all of its specifications. More specifically:
<ul>
<li> rdfs:label is used to provide a human-readable version of a resource's name.</li>
<li> The usage of certain resource can be clarified in vann:usageNote.</li>
<li> The usage of certain resource can be clarified in a skos:usageNote.</li>
</ul>

</section>
Expand Down Expand Up @@ -3779,7 +3780,7 @@ <h2>Quick Reference of Classes and Properties</h2>
<td><div class="shorten">http://www.w3.org/ns/adms#Identifier</div></td>
<td></td>
<td><a href="#Identifier.identifies">identifies </a></td>
<td><div class="shorten">http://www.w3.org/ns/adms#identifies</div></td>
<td><div class="shorten">http://data.europa.eu/m8g/identifies</div></td>
</tr>


Expand Down
Loading

0 comments on commit aea7b4d

Please sign in to comment.