ADMS Issues 09 February 2012 Proposed Proposed Category JIRA Description Action Resolution

Joinup issues ISACV-229 Publish specification in more accessible format than PDF Accept Move to Joinup issues ISACV-234 Don't ask for participation in survey for every anonymous download Accept Move to Joinup issues

Editorial issues Simple text and diagram suggestions ISACV-187 UML diagram for customization may be confusing Accept Remove diagram. ISACV-224 Check spelling of "Licence" throughout Accept Align spelling. ISACV-236 Add column data type to tables in 5.4 and 5.5 Accept Add columns. ISACV-256 Improve terms and definitions Accept Check, align, add clarifications. ISACV-261 Change "eGovernment Data" to "eGovernment Primary Resources" Accept Change phrase. ISACV-262 Ordering of properties Reject ISACV-245 Align element names in mapping sheet with specifications Accept Align names. ISACV-266 Some relationships in the model diagram are not clearly visible Accept Redraft diagram. ISACV-269 Textual changes in section 5.6 Accept Change text.

ISACV-212 Consider renaming release into artefact Decide Change name to "Artefact". ISACV-222 Status "Published" may be confusing Decide Change name to "Completed".

Clarifications ISACV-235 Dates and version numbers on ADMS examples are confusing Accept Add clarifications. ISACV-255 Better define what material ADMS can be used for Accept Add clarifications. ISACV-259 Better define responsibility of Publisher Accept Add clarifications.

General feedback ISACV-110 To provide further comments on ADMS use cases Keep Provide feedback. ISACV-120 To verify list of Asset Types in mapping exercise and public comment Keep Provide feedback.

Use cases ISACV-258 Questioning assignment of importance to attributes in Use case Accept Add clarifications.

Conceptual model Granularity ISACV-157 Granularity of an asset Accept Add relationship Included Asset to Asset ISACV-215 Granularity and asset-asset relationships Accept Idem.

Concepts/classes ISACV-159 Generalize the concept of coverage Accept No action. ISACV-183 ExampleAsset seems redundant Accept Remove concept Example Asset, make relationship sample Asset-to-Asset ISACV-184 Replace concept Included Item by a basic concept Item Accept Rename concept Included Item to Item ISACV-243 What is the exact idea behind the "Included item" relationship? Accept Add clarifications. ISACV-264 What is meant by Included Item? Accept Idem.

ISACV-200 Define Status as a list of codes, not URIs Decide Propose not to change; current model allows use of other, local, Status codes ISACV-202 Allow multiple file representations in Release Decide Propose not to change ISACV-208 Asset Identifier as a concept based on UN/CEFACT Identifier.Type Decide Propose not to change ISACV-216 Add temporal coverage Decide Propose to add; possibly re-use from elsewhere Properties and relationships ISACV-145 To add a maintenance and versioning attribute for ADMS Repository Accept Add attribute Supported Schema to Repository ISACV-155 Why not have a version-class covering all version information? Reject ISACV-220 Cardinality of subject and domain Accept Keep both optional, no change ISACV-268 How is URI of Example Asset different from the Asset itself? Obsolete Covered by issue 183 ISACV-179 Make the publisher, subject and domain links mandatory to allow (more) support for the explore and identify use cases Obsolete Covered in issues 220 (domain and subject) and 190 (publisher) ISACV-180 Include contact information of the Publisher Accept Add concept Contact Information and add relationsip Contact to Asset ISACV-190 Clarify the current optional asset:Publisher Attribute with the mandatory information on Text, ID AND Code Accept Make Publisher mandatory, Publisher Type optional ISACV-197 ADMS - Asset:DateOfCreation AND Asset:DateOfLastModification - consider refinement from Date to Timestamp or to Datetime Accept Change Dates to TimStamp, Data Type Date and Time

New attributes ISACV-203 Provide attribute to indicate that one file format is normative Decide Propose to add ISACV-204 Distinguish between logical/semantic inclusion and convenience packaging for Release Decide Combine with issue 209: add relationship Representation Language to Release ISACV-209 IANA MIME types are insufficient to derive the representation language Decide Combine with issue 204: add relationship Representation Language to Release ISACV-214 Add reverse property of RepositoryOrigin Decide Propose to add relationship Included Asset to Repository ISACV-219 Do Releases point to assets also? Decide Propose to add relationship Parent Asset to Release ISACV-221 Distinguish between human and machine-generated translations of text Decide Propose to reject ISACV-233 Clarification of "Label" or addition of "Description" attribute for concepts that have "Label" Decide Propose to add property ISACV-244 Add attribute Version Notes to Asset Decide Propose to add property ISACV-265 Need for more specific relationship between assets Decide Propose to keep and ask for specific proposals

Cardinalities ISACV-217 Cardinality of IDs Decide Propose to implement as proposed ISACV-237 Make Language of the Asset mandatory? Decide Propose to reject; not applicable to Assets that contain no text ISACV-250 Date of Creation and Date of Modification of Assets Decide Propose to keep Creation optional and Modification mandatory ISACV-271 Relax constraints on cardinalities of Next and Previous Version Decide Propose cadinality [0..*] for both Next and Previous Version

Usage of existing attributes ISACV-263 ID for Asset independent of specific version Decide Propose to reject ISACV-267 Why is Date of Creation for Repository relevant? Decide Propose to remove Date of Creation from Repository

Vocabularies These issues are about including additiona suggestions and can be taken care of in the editorial process ISACV-175 Do not forget French Cecill licence Accept Add to examples in section 6 ISACV-185 Add ISO 3166 country codes to suggestions for controlled vocabularies for geographic coverage Accept Add to examples in section 6 ISACV-218 URIs for languages at lexvo.org Accept Add to examples in section 6 ISACV-240 NTU (list of statistical units aligned with political entities) as an alternative to NUTS Accept Add to examples in section 6 ISACV-241 Where is the code list for RFC 5646? Accept Add to examples in section 6 ISACV-242 Use of controlled vocabulary for Publisher Accept Add to examples in section 6 ISACV-251 Add ISO 3166 country codes to suggestions for controlled vocabularies for geographic coverage Accept Add to examples in section 6

Additional vocabularies ISACV-209 IANA MIME types are insufficient to derive the representation language Decide Propose to add vocabulary for Representaion Language ISACV-213 Enable repository owners to express "Domain" and "Asset Type" as they have it in their repositories Decide Propose to allow use of local vocabularies

Additional terms ISACV-252 Add Publisher Types Decide Propose to add suggested types ISACV-260 Publisher Type has very limited set Decide Propose to add suggested types

Problems with vocabularies ISACV-232 ADMS relies on vocabularies from others; this brings issues of persistence and referential integrity Decide Propose to move this discussion to next phase ISACV-210 Geographic coverage - NUTS codes are not URI-based Decide Propose to move this discussion to next phase ISACV-239 IANA MIME types not suitable Decide Propose to move this discussion to next phase ISACV-257 NUTS, DBPedia and FAO Geopolitical Ontology not suitable for Geographic Coverage Decide Propose to reject issue

Asset Types ISACV-226 Selected comments on Asset Type Decide Propose to move this discussion to next phase ISACV-270 Comments on Interoperability level and Asset Type vocabularies Decide Propose to move this discussion to next phase URI issues ISACV-199 The URI element does not always seem useful and perhaps should not be mandatory in the XML schema. Decide Open discussion ISACV-211 What are ADMS' requirements for URIs Decide Open discussion

Schemas RDF issues ISACV-68 To see how the name space document of the ADMS will be published Keep Waiting for decision ISACV-188 Equivalencing ADMS terms with terms in existing namespaces Accept Check options and add equivalences ISACV-223 Missing domain declarations in RDF schema file Accept Add missing declarations ISACV-227 Make sample Asset a subproperty of dcat:dataset Accept Make subproperty assertion ISACV-228 Spatial coverage seems to be missing from RDF version Reject dcterms:spatial is included

XML issues ISACV-201 Use XSD to validate code lists Keep Waiting for comment

Licence issues ISACV-174 Licence Vocabulary and Licence Type Keep Waiting for expert advice ISACV-186 Use of Creative Commons ccREL vocabulary Keep Waiting for expert advice ISACV-225 Do not use "legal document" as characterisation of Licence Keep Waiting for expert advice ISACV-248 Where to get the license information from? Keep Waiting for expert advice

Guidance ISACV-205 Provide guidance how to model difference between "next" process stage versions and "next" functional versions Keep Discuss separately with standards bodies (W3C, OASIS) ISACV-231 How to model Assets that are specification documents Keep Discuss separately with standards bodies (W3C, OASIS)

Mapping and implementation issues ISACV-172 Different line feeds in descriptions. Keep Move to CESAR forum ISACV-173 XML unfriendly tags in description fields Keep Move to CESAR forum ISACV-189 What mechanism is ADMS going to use to enable finding of assets in a Web site? Keep Move to CESAR forum ISACV-198 How do I find the list of assets when I discover a new Website? Keep Move to CESAR forum ISACV-238 Assigning Assets to domains not always possible Keep Move to CESAR forum ISACV-246 How much information to export and when? Keep Move to CESAR forum ISACV-247 Where to slice the asset and the release concept out of your source repository? Keep Move to CESAR forum ISACV-249 How to control the access to the exported RDF file? Keep Move to CESAR forum

Future issues ISACV-182 Consider relevance of CKAN/TheDataHub work Keep Establish contact ISACV-253 Take deeper look at existing frameworks, schemas et al for further development of ADMS Keep Move to next phase ISACV-254 Consider use cases for statistics and metrics Keep Move to next phase ISACV-230 Lost in semantic or lost semantic? Reject