Some remarks I have found in version V1.2 of 2010-06-16, that are still in this draft version and maybe are now better solved too:

-P. 8: 1.1.2: Services

oTable:

Additional extent information for the dataset:  INSPIRE field: Part B.5.1

Lineage:  INSPIRE field: not applicable to services

P. 9 – 3 records above the end of the page: Part B 1.6 Coupled Resource  Comments field: Conditional (instead of optional) in INSPIRE

-P. 50: 3.2 Resource MetadataSet:

oFigure “property instances”:

+ linkage [0..1]: URL …………. (instead of [1]), whilst this field is conditional

-P. 51: 3.3 Identification Section:

oFigure “property instances”:

+ language [0..*]: LanguageCode …………. (instead of [1..*]), whilst this field is conditional

+ extent [0..*]: TM_Primitive…………. (instead of [1]), whilst this field is conditional

-P. 53: 3.4.1 Lineage:

oFigure “property instances”:

+ extent [0]: ………….  shall be not any restriction  means no extent-information? Is this correct?

-P. 53: 3.4.2 Conformity:

oFigure “property instances”:

+ measureIdentification [1]: …………. this is extra foreseen here and not mentioned earlier

Then some suggestions of me to give extra clarifying examples in the draft version v0.2:

-P. 25 TG Recommendation 9:

oWhy do we say so?  Because of tracking the different versions of data and its metadata?

  • + give an example of this too

-P. 292.2.6 Coupled Resource:

oWe implement the link as a GetRecordsByID operation instead of the GetRecords operation, because not every CSW supports the GetRecords with on operatesOn.

Overall it is better I think if we support one approach better than the other, because of higher interoperability. (Even so for the Constraints information).

-P. 54: Specification: Example:  Nothing mentioned about the language  see f.e. TG Recommendation 13.

oIt would be better to mention this here too if you can choose your own language.

And I found sometyping errors too in the draft version v0.2:

-P. 56: - 2.9:

oline 20: ISO 19115 since the use of UseLimitation is used here  ISO 19115 since the use ofthe element UseLimitation is used here

  • A metadata record that is using the implementation based on 2.9.3 and 2.9.4 is identified by its reference in otherRestrictions to the thecodelist in INSPIRERegistry…

-P. 63: - Example:

- …/LimitationsOnPublicAccess//NoLimitations”>  one / to many

At least: missingelements in data quality:

Is it possible the element DQ_UsabilityElement is forgotten?  It is recommended for Buildings and Sea Regions themes?

1