Comments on ADMS draft

Dear WG Members, 

Congrats on the hard work that you did for elaborating this draft of ADMS. 


Based on the experience that we gained by implementing ADMS in more than 
20 semantic asset repositories in Europe and beyond, we would like to 
contribute the following comments, which we hope that can improve further 
the quality of the model. 

Based on our experience in SEMIC, the distinction between 
SemanticAssetRepository and AssetRepository is in practice quite vague (it 
often does not exist). 
In the majority of cases, asset repositories contain different types of 
assets (e.g. semantic, technical and organisational). 
We would therefore propose renaming 'SemanticAssetRepository' to 
'AssetRepository'. 
A similar approach could be followed for SemanticAsset, i.e. renaming it 
to 'Asset'.

If adms:supportedschema refers to the data model that the repository uses 
for exporting its description metadata, then shouldn't the range be 
adms:SemanticAsset?

adms:relatedDocumentation and relatedWebpage can be perceived as 
overlapping. You could consider merging them into one property. 

Is it possible to make a reference at some point in the note to the 
controlled vocabularies and the reference implementation of ADMS on 
Joinup?

Some of the examples could be improved. For instance, it is a good 
practice to include a triple for the SemanticAssetRepository in the 
description of the asset and a triple for the SemanticAsset in the 
description of the distribution. 

Kind regards, 

Nikolaos Loutas
PwC | Principal Advisor
Direct: +32 2 7104619 | Mobile: +32 491 965851 | Fax: +32 2 7104069
Email: nikolaos.loutas@pwc.be
PwC Enterprise Advisory cvba/scrl
Firm legal information, click here


*Professional Mail*
------------------------------------------------------------------------------------------
This e-mail is intended only for the person to whom it is addressed.
If an addressing or transmission error has misdirected this e-mail,
please notify the author by replying to this e-mail. If you are not
the intended recipient you must not use, disclose, copy, print or
rely on this e-mail.
 
PwC may monitor outgoing and incoming e-mails and
other telecommunications on its e-mail and telecommunications systems.
------------------------------------------------------------------------------------------