hannesN / onotoa

a visual editor for the Topic Maps Constraint Language.
0 stars 0 forks source link

Generate easier to identify item identifier of schema #191

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Generate a new schema with Onotoa
2. Export schema
3. Import schema in Onotoa

What is the expected output?
Like Topic Types the schema instance should have an easy to read and identify 
item identifier. Maybe something like schema name + version (see other issue 
for implementation of version information of schema).

What do you see instead?
Same cryptic identifier like for all other topic type instances. Hard to 
identify while reading xtm, ctm exports. 

What version of the product are you using?
applies to all versions
On what operating system?
10.6.4 x64

Please provide any additional information below.

Original issue reported on code.google.com by morten.k...@whu.edu on 8 Nov 2010 at 5:32

GoogleCodeExporter commented 9 years ago
Why is the import in your stps needed?

Original comment by h.niederhausen@googlemail.com on 8 Nov 2010 at 5:34

GoogleCodeExporter commented 9 years ago
Please clarify "stps" :)

Original comment by morten.k...@whu.edu on 8 Nov 2010 at 5:40

GoogleCodeExporter commented 9 years ago
Sorry, meant steps.

Original comment by h.niederhausen@googlemail.com on 8 Nov 2010 at 5:43

GoogleCodeExporter commented 9 years ago
I usually export from Onotoa to XTM21 to work with the file within RTM. I use 
Maiana as a tool to check if my RTM code returns correct values.

Having a clearer schema item identifier would make it easier to identify during 
debugging and so on.

Original comment by morten.k...@whu.edu on 8 Nov 2010 at 5:45

GoogleCodeExporter commented 9 years ago
This issue was closed by revision 69443d1611.

Original comment by h.niederhausen@googlemail.com on 9 Nov 2010 at 4:19

GoogleCodeExporter commented 9 years ago
The ItemIdentifier is now: http://onotoa.topicmapslab.de/schema/{version}
if no version was set it ends with schema

Original comment by h.niederhausen@googlemail.com on 9 Nov 2010 at 4:20