Profile field includes version as # and profile is url (?)

[rufuspollock]

Extend profile field to include version of the profile using # e.g.

profile:data-package#v1.0

Also consider explicit urls for profile schema:

profile: url-to-schema

cf ropensci-archive/datapkg#12 (comment)

[ezwelty]

I really think this should be a url-or-path, and nothing more. A url allows custom profiles and skips the fragile step of parsing "data-package#v1.0" to a url, and path allows the profile to be included within the data package.

I liked the suggestion of this being called schema, since that's what's being pointed to.
edit: Oops, sorry, schema is already a data resource property, so having it mean two different things would be confusing.

[rufuspollock]

@ezwelty really like the suggestion and you've grokked why we don't use schema (which would anyway be ambiguous over data schema vs metadata schema).

[pwalsh]

@rufuspollock I much prefer the solution I have for versions, scheduled for discussion for v1.1, here:

• Adding a version to profile attribute (or doing this via a "spec" namespace) #444 (comment)

As for URL to schema, I was supporting this already in rc1:

• https://github.com/frictionlessdata/specs/blob/master/sources/dictionary/common.yml#L18

[rufuspollock]

@pwalsh another reason why you and I having regular chats is a "good idea" (tm) 😉

Again the question of "normalized" form i.e. two properties vs all in one string is there.

Anyway I'm going to close this as DUPLICATE in favour of #444.