Comment Details - National Information Standards Organization

#00103 Comment Details - canonical_cit-2010-09-22.pdf

Document Information
File Name	canonical_cit-2010-09-22.pdf	State	Draft
Date Added	2010-12-17 12:04:11	Revision Number	0
Submitter Name	Phil Norman	Size	no size

Comment Information
Summary	Community Profile including Canonical Citation	State (Disposition)	New (Unresolved)
Date Added	2011-03-13 06:14:35	Last Updated	2011-03-23 13:32:01
Submitter Name	Ann Apps	Assigned To	Unassigned
Company Name	UNAFFILIATED PARTICIPANTS COMPANY	Response	None
Interest Category	General Interest	Category	N/A
Origin	Member	Section, Page, Line	Section All
Item		Item Description

Submitter Comment
I think (if I remember correctly) that an existing Community Profile cannot be edited. Although simply including Canonical Citation in SAP1 seems the obvious route, this would in fact create a new Community Profile. Even if it is called SAP1 Version 2 it is still a new profile...

Submitter Comment

I think (if I remember correctly) that an existing Community Profile cannot be edited. Although simply including Canonical Citation in SAP1 seems the obvious route, this would in fact create a new Community Profile. Even if it is called SAP1 Version 2 it is still a new profile...

Developer Response
The Z39.88-2004 spec uses the phrase "the Committee envisions the Registry being under strict version control." Note that SAP1 is already in its second revision: 1) info:ofi/pro:sap1 (marked as "Deprecated") 2) info:ofi/pro:sap1-2004 This was a major change, though, that was required to accommodate the redefinition of Community Profiles in general: 1) info:ofi/pro http://www.openurl.info/registry/docs/xsd/info:ofi/fmt:xml:xsd:pro (marked as "Deprecated") 2) info:ofi/pro-2004 http://www.openurl.info/registry/docs/xsd/info:ofi/fmt:xml:xsd:pro-2004 IMO, the committee's "strict" stance on version control isn't practical for minor/optional additions. The situation is directly analogous to trying to coin new XML namespace and XML Schema URIs for minor/optional additions to XML. Programmers used to believe this was a good idea, but the cure was worse than the disease. In SAP1-2004, support for all metadata formats is optional: info:ofi/fmt:kev:mtx:journal info:ofi/fmt:kev:mtx:book info:ofi/fmt:kev:mtx:patent info:ofi/fmt:kev:mtx:sch_svc info:ofi/fmt:kev:mtx:dissertation My feeling is that the best solution in this case would be to add the new metadata formats to the SAP1-2004 spec and Community Profile and tag those additions as date-stamped amendments.

Developer Response

The Z39.88-2004 spec uses the phrase "the Committee envisions the Registry being under strict version control."

Note that SAP1 is already in its second revision:

1) info:ofi/pro:sap1 (marked as "Deprecated")
2) info:ofi/pro:sap1-2004

This was a major change, though, that was required to accommodate the redefinition of Community Profiles in general:

1) info:ofi/pro http://www.openurl.info/registry/docs/xsd/info:ofi/fmt:xml:xsd:pro (marked as "Deprecated")
2) info:ofi/pro-2004 http://www.openurl.info/registry/docs/xsd/info:ofi/fmt:xml:xsd:pro-2004

IMO, the committee's "strict" stance on version control isn't practical for minor/optional additions. The situation is directly analogous to trying to coin new XML namespace and XML Schema URIs for minor/optional additions to XML. Programmers used to believe this was a good idea, but the cure was worse than the disease.

In SAP1-2004, support for all metadata formats is optional:

info:ofi/fmt:kev:mtx:journal
info:ofi/fmt:kev:mtx:book
info:ofi/fmt:kev:mtx:patent
info:ofi/fmt:kev:mtx:sch_svc
info:ofi/fmt:kev:mtx:dissertation

My feeling is that the best solution in this case would be to add the new metadata formats to the SAP1-2004 spec and Community Profile and tag those additions as date-stamped amendments.