Skip to content

Embedded integer doesn't get represented simply? #313

@garpinc

Description

@garpinc

I have the following rdf

{
	<http://pk1> a <http://cambridgesemantics.com/ontologies/2018/06/MetadataDictionary#KeySet> , <http://cambridgesemantics.com/ontologies/2018/06/MetadataDictionary#PrimaryKey> ;
		<http://cambridgesemantics.com/ontologies/2018/06/MetadataDictionary#priority> "6"^^<http://www.w3.org/2001/XMLSchema#int> .
	
	<http://pk2> a <http://cambridgesemantics.com/ontologies/2018/06/MetadataDictionary#KeySet> , <http://cambridgesemantics.com/ontologies/2018/06/MetadataDictionary#PrimaryKey> ;
		<http://cambridgesemantics.com/ontologies/2018/06/MetadataDictionary#priority> "6"^^<http://www.w3.org/2001/XMLSchema#int> .
	
	<http://testc1> a <http://cambridgesemantics.com/ontologies/2018/06/MetadataDictionary#ClassConcept> , <http://cambridgesemantics.com/ontologies/2018/06/MetadataDictionary#MetadataConcept> , <http://www.w3.org/2004/02/skos/core#Concept> ;
		<http://cambridgesemantics.com/ontologies/2018/06/MetadataDictionary#primaryKey> <http://pk1> , <http://pk2> .
}

When I run it through json ld via frame I get

{
  "@context" : "http://cambridgesemantics.com/ontologies/2018/06/MetadataDictionary/ClassConcept",
  "uri" : "http://testc1",
  "type" : [ "metaframe:ClassConcept", "metaframe:MetadataConcept", "skos:Concept" ],
  "primaryKey" : [ {
    "uri" : "http://pk1",
    "type" : [ "metaframe:KeySet", "metaframe:PrimaryKey" ],
    "metaframe:priority" : {
      "type" : "http://www.w3.org/2001/XMLSchema#int",
      "@value" : "5"
    }
  }, {
    "uri" : "http://pk2",
    "type" : [ "metaframe:KeySet", "metaframe:PrimaryKey" ],
    "metaframe:priority" : {
      "type" : "http://www.w3.org/2001/XMLSchema#int",
      "@value" : "6"
    }
  } ]
}

Which does reflect the rdf above... But although metaframe is defined in the @context somehow it remains in the property where the property name should be simply "priority". In addition I would expect it to be instead

"priority" : 6

instead of the type/value object..

Is this a bug?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions