Skip to content
This repository has been archived by the owner on Feb 12, 2022. It is now read-only.

AMF does not translate default type for RAML data types #69

Open
sichvoge opened this issue May 22, 2017 · 0 comments
Open

AMF does not translate default type for RAML data types #69

sichvoge opened this issue May 22, 2017 · 0 comments
Labels

Comments

@sichvoge
Copy link
Contributor

sichvoge commented May 22, 2017

In RAML data types, the default type for any types is string. For example, the following type definitions are equivalent:

types:
  AddressData:
    properties:
      address_country:
      address_locality:
      address_region:
      postal_code:
      street_address:
types:
  AddressData:
    properties:
      address_country: 
        type: string
      address_locality:
        type: string
      address_region:
        type: string
      postal_code:
        type: string
      street_address:
        type: string

AMF does not correctly correlate and assigns the default type, and only leaves the value for the type empty. This is a snippet from the JSON-LD shape:

...
      {
        "@id": "file://#/definitions/AddressData/property/address_locality",
        "@type": [
          "shacl:PropertyShape",
          "shacl:Shape"
        ],
        "raml-shapes:propertyLabel": "address_locality",
        "shacl:maxCount": 1,
        "shacl:minCount": 1,
        "shacl:path": {
          "@id": "http://raml.org/vocabularies/shapes/anon#address_locality"
        }
      }
...
@sichvoge sichvoge added the bug label May 22, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

1 participant