get-type gives me a term which is annotated with Use(Def(URI...)) instead of Use(Task(...)). Trying to obtain a property via the term/def/uri fails.

Am I missing something or is this not yet supported by NaBL? In the later case, is there a workaround that I can use for the time being?

Thanks.

Submitted by Oskar van Rest on 22 January 2014 at 08:40

On 22 January 2014 at 11:31 Gabriël Konat commented:

How do you try to obtain the property? Show me the full code.


On 22 January 2014 at 11:48 Oskar van Rest commented:

I tried the following variants:

get-type; get-property(|NablProp_datatypeTerm())
get-type; get-annos; Hd; ?Use(<id>); get-property(|NablProp_datatypeTerm())
get-type; get-annos; Hd; ?Use(Def(<id>)); get-property(|NablProp_datatypeTerm())

Also get-type gives:

"Year"{ Use(Def(
                URI(
                  Language("Flujo")
                , [ID(NablNsDatatype(), "Year", Unique("/home/oskar/repos/flujo.sdf3/org.flujo.textual/examples/parsing.fml/0")), ID(NablNsDomain(), "Flujo-Parsing-Test", NonUnique())]
                )
              ))
            }

On 22 January 2014 at 11:55 Gabriël Konat commented:

In that case get-property will look into the index for that property, it should automatically find the URI inside the Use(Def(..)). Can you check the index to confirm that the URI of "Year" has a NablProp_datatypeTerm() property?


On 22 January 2014 at 12:09 Oskar van Rest commented:

I had a better look at my code and found out it was failing elsewhere. Now all variants work. Sorry for the trouble.


On 22 January 2014 at 12:09 Oskar van Rest closed this issue.

Log in to post comments