Changes between Version 4 and Version 5 of CMDI 1.2/Schema sanity/Namespaces


Ignore:
Timestamp:
01/08/14 10:50:54 (10 years ago)
Author:
oschonef
Comment:

Some input for discussion

Legend:

Unmodified
Added
Removed
Modified

  • CMDI 1.2/Schema sanity/Namespaces

    v4 v5  
    3535==== Discussion ====
    3636
    37 Discuss this solution proposal in this section
     37[[oschonef|Oliver (IDS)]]: NACK: CLARIN is about standards, interfaces and sustainability; this solution utilizes OAI-PMH in non obvious means and therefore violates CLARIN's principles. We should not do this.
     38
    3839
    3940=== Second solution: profile specific metadataPrefixes ===
    … …  
    6162==== Discussion ====
    6263
    63 Discuss this solution proposal in this section
     64[[oschonef|Oliver (IDS)]]: NACK: This is rather a crude hack than a solution, because it (again) utilizes OAI-PMH in non obvious means. We should not do this.
     65
    6466
    6567=== Third solution: up to the centers ===
    … …  
    8587==== Discussion ====
    8688
    87 Discuss this solution proposal in this section
     89[[oschonef|Oliver (IDS)]]: NACK: Mixed compliance within CLARIN is a recipe for disaster in a (near|distant) future. We should definitely not do this.
     90
     91
    8892
    8993=== Fourth solution: CMD envelop and payload specific schemas and namespaces ===
    … …  
    185189==== Discussion ====
    186190
    187 Discuss this solution proposal in this section
     191[[oschonef|Oliver (IDS)]]: This is better than solution 1-3, but still has the issue of using XML namespaces in non obvious ways. The XML namespace specification section 3 [http://www.w3.org/TR/xml-names/#ns-decl Declaring Namespaces] states the following on uniqueness:
     192> The namespace name, to serve its intended purpose, SHOULD have the characteristics of uniqueness and persistence.
     193If we use the same namespace name (= URI) for different schemas, we are violating the XML namespace specification. We should not do this.
     194
    188195
    189196=== Fifth solution: profile specific payload namespaces ===
    … …  
    252259==== Discussion ====
    253260
    254 Discuss this solution proposal in this section
     261[[oschonef|Oliver (IDS)]]: Even though this solution has the largest impact on centres, it is (IMHO) the best solution, because it is most standards compliant and allows (if multiple ID issue is soluved properly) smooth integration with OAI-PMH. The longer, we postpone this solution, the larger the pain for the centers will become, so we better make that decision now and be done with it.
     262
    255263
    256264== Tickets ==