Changes between Version 9 and Version 10 of CMDI 1.2/Resource proxies/Element


Ignore:
Timestamp:
01/22/14 12:11:35 (10 years ago)
Author:
twagoo
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • CMDI 1.2/Resource proxies/Element

    v9 v10  
    7575  [[twagoo|Twan]]: That's true, a component does not define the specification of a full resource ''per se''. My point is that, I think, elements never do/can/should. If an element describes a property of a resource, there will always be component higher up in the tree that selects the resource. Even with bad modeling, I think that would be hard to avoid but maybe someone can provide a counterexample.
    7676
    77 Components that are ''profiles'' on the other hand, do represent a holistic description of the resource as a whole, and I think it is preferable to  reserve the ResourceProxyList in a CMDI file for resources/files that actually constitute the ''described resource''. Other relevant resources (documentation, reviews, publications, a.o.) should be referenced from appropriate parts of the metadata instance. If such resources only can be referenced from components, one would have decide this at model time, which perhaps is no big deal? Especially if there is a risk of increased malpractice attached to allowing it for elements, too.       
     77Components that are ''profiles'' on the other hand, do represent a holistic description of the resource as a whole, and I think it is preferable to  reserve the ResourceProxyList in a CMDI file for resources/files that actually constitute the ''described resource''. Other relevant resources (documentation, reviews, publications, a.o.) should be referenced from appropriate parts of the metadata instance. If such resources only can be referenced from components, one would have decide this at model time, which perhaps is no big deal? Especially if there is a risk of increased malpractice attached to allowing it for elements, too.   
    7878
    79 Discuss the topic in general below this point
     79  [[twagoo|Twan]]: I completely agree with your point that only described resources should be referenced from the resource proxy list! Other kinds of references would be profile specific and obviously can only be achieved by means of elements and/or attributes. Yes this has to be decided at model time, and I am not sure if that could be an issue - I guess not really.
     80  In any case, the crucial point is that this is both conceptually and technically a different kind of referencing. Maybe you do a agree that ''described resources'' should be referable from the component level only while other kinds of referencing (typically through an element of type ''anyURI'') should be allowed occur in arbitrary places in component and profile specifications?
     81
     82  It's good to be aware that this topic often leads to confusion; we have seen several cases where !ResourceProxies were interpreted as the preferred location to store ''any'' external reference, described resource or otherwise. We should probably think about ways to make the semantics of the resource proxy list clearer to prevent this.
     83