responsibility 2.0 about mdjson-schemas HOT 11 CLOSED

Remove partyType.

from mdjson-schemas.

roleExtent should be an array.

from mdjson-schemas.

Replace start and end date with temporalExtent.

from mdjson-schemas.

partyType has been removed.

from mdjson-schemas.

I had limited the role extent to one object since I did not allow the expression of a full EX_Extent. The full EX_Extent would permit descriptive, graphic, vertical, as well as temporal extents to be defined. But technically this is an array in ISO. I have made the change per your request but have not opened the mdJson for other than temporal extents.

from mdjson-schemas.

Why don't we just use timePeriod instead of roleExtent? The use of extent is confusing. In fact, I would suggest dropping the use of extent anywhere we're restricting the type of extent - we don't need to wrap them in an additional layer. Just add the geographic, vertical, or temporal extent properties directly to the object in question.

from mdjson-schemas.

Just add the geographic, vertical, or temporal extent properties directly to the object in question.

Unless we're allowing all three.

from mdjson-schemas.

Fair enough. If we are going to call it timePeriod it may as well be the full timePeriod. I changed roleExtent to timePeriod.

from mdjson-schemas.

"timePeriod" should be an array, right? Example shows it an an object. Also see here.

from mdjson-schemas.

Yep, right you are. I missed it since "responsibility" with "extent" is a new construct in -1. So, I had not tested yet. I'll patch it now. If fact, I think I'll make it a "temporalExtent" array.

from mdjson-schemas.

I changed "timePeriod" out for the full "extent". Not only does this match the ISO 19115-1 standard, it was getting confusing limiting extent type to "timePeriod" when there were different use cases for responsibility.

from mdjson-schemas.