search

UDT-ITF / website

Website for UDT-ITF API specifications
1 stars 0 forks source link

Do we need version numbers or are labels sufficient? #64

Open mjhawkins opened 10 months ago

mjhawkins commented 10 months ago

MH: It depends on whether we can foresee a need for a text collection to use both labels and versions to identify specific incarnations of the resource in conjunction. That is, l:main/v:1.0.0 - for the primary release version and l:crowdsourced/v:1.0.0 - for a different version of the text (say with some crowdsourced additions that the provider doesn't want to include within the main release but does want to make available in an explicit crowdsourced release). If that specific scenario isn't to be supported, there's no reason that the label couldn't be a version number. If we were to adopt the latter approach, should we call it a 'tag' just as Git does?