Namespaces. Version metadata in namespace?

Locked

Does a namespace need to contain version information?

Yes.
0
No votes
No.
8
89%
Neither (explained in a reply).
0
No votes
No vote.
1
11%
 
Total votes: 9

Message
Author
OnnoPaap
Posts: 189
Joined: Sun Jan 22, 2012 9:14 pm

Namespaces. Version metadata in namespace?

#1 Post by OnnoPaap »

The namespace method we got from ISO 15926-4 (and -6) and put in ISO 15926-8 carries version information.

Example (for dm:):

Code: Select all

http://standards.iso.org/iso/ts/15926/-8/ed-1/tech/reference-data/data-model#ClassOfActivity
This thread is about discussing the cons and pros of this type of namespace.

Given some facts (but we can discuss in this thread to add more):
  • A namespace does not need to be resolvable (produce a page when a browser points at it). We have technical solutions for relating a namespace to an endpoint address.
  • Metadata like version information can be expressed semantically, e.g. with the ClassOfClass relationship.
Without version information the example would look like this:

Code: Select all

http://standards.iso.org/iso/15926/-8/tech/reference-data/data-model#ClassOfActivity

HansTeijgeler
Posts: 283
Joined: Sun Jan 22, 2012 10:02 pm

Re: Namespaces. Version metadata in namespace?

#2 Post by HansTeijgeler »


OnnoPaap
Posts: 189
Joined: Sun Jan 22, 2012 9:14 pm

Re: Namespaces. Version metadata in namespace?

#3 Post by OnnoPaap »

I voted no because for me there is another reason: versions in name spaces would cause differences in namespaces where there should not exist a difference.

Sorry for the "no vote". I could not undo the vote I made in my admin ident, so made it no vote.

Locked