View unanswered posts | View active topics It is currently Sat Dec 07, 2019 7:18 am



Reply to topic  [ 28 posts ]  Go to page 1, 2, 3  Next
 p7tpl file generation 
Author Message

Joined: Sun Jan 22, 2012 9:14 pm
Posts: 189
We had a discussion in the ISO 15926-9 team, about implementation of First Order Logic script.
We found that it was a problem that there is no strict way of relating FOL script to base/core templates.

We want to propose the following solution:
  • The p7tpl.owl file that is attached to part 8 already uses a template for metadata related to base templates, called p7tm:TemplateDescription. For convenience, here you can download the part 8 attachments:
    Attachment:
    ISO15926-8.RDF.zip [108.73 KiB]
    Downloaded 198 times
  • We want to add the relationship to the FOL as a new role in p7tm:TemplateDescription
  • There are some other updates we made to the p7tpl.owl. Here is an example file with only 1 base template.
    Attachment:
    example_p7tpl_generated.zip [1.44 KiB]
    Downloaded 209 times
  • The link for downloading the template specs to consolidated OWL will generate this new p7tpl.owl. So (Victor) be careful, the base namespace in this file will be changed to the p7tpl name; in our proposal.


Mon Nov 05, 2012 2:29 pm
Profile

Joined: Sun Jan 22, 2012 9:14 pm
Posts: 189
I have changed the download program over to the new template spec consolidated OWL xml structure which has p7tpl as base namespace.

I expect that Victor Agroskin and Peter Denno will have to check their programs.

Hans mentioned that each template spec has a new URI every time you open the list page.

That is not true. There was a fake get variable added called cachebuster e.g.
Code:
http://15926.org/templatespecs/CL-ACTIV-01.xml?cachebuster=0.34720700%201352379877


This cachebuster was only added because the template spec xml would not refresh after there was a change made. If you are referring to a spec from a web page, you can do it with and without cachebuster. The result is the same as it is a fake variable.
Code:
http://15926.org/templatespecs/CL-ACTIV-01.xml


Thu Nov 08, 2012 1:09 pm
Profile

Joined: Mon Feb 27, 2012 11:01 pm
Posts: 282
Location: Moscow, Russia
Don't understand what has changed yet, but I've strong suspicions it is nor Part 8 anymore. Me software can not see any templates in a new file :-(


Mon Nov 12, 2012 10:17 am
Profile WWW

Joined: Mon Feb 27, 2012 11:01 pm
Posts: 282
Location: Moscow, Russia
Onno,

What exactly is the reason for changing full namespaces to

xmlns:p7tpl="http://standards.iso.org/iso/ts/15926/-8/ed-1/tech/reference-data/p7tpl#" xmlns:p7tm="http://standards.iso.org/iso/ts/15926/-8/ed-1/tech/reference-data/p7tm#"

instead of

xmlns:p7tpl="http://standards.iso.org/iso/ts/15926/-8/ed-1/tech/reference-data/templates#" xmlns:p7tm="http://standards.iso.org/iso/ts/15926/-8/ed-1/tech/reference-data/template-model#"

What are other changes? Can you make a list of changes?


Mon Nov 12, 2012 10:43 am
Profile WWW

Joined: Mon Feb 27, 2012 11:01 pm
Posts: 282
Location: Moscow, Russia
Namespace change is really a problem once you have at least some data already distributed. It requires a lot of reasons really! What is the intended procedure of namespace change?

The name http://standards.iso.org/iso/ts/15926/- ... ate-model# is in Part 8 samples and there are many copies of p7tpl.owl distributed.

The namespace for templates themselves is also a problem - there are many data samples, I think.


Mon Nov 12, 2012 10:59 am
Profile WWW

Joined: Mon Feb 27, 2012 11:01 pm
Posts: 282
Location: Moscow, Russia
One last point. I'm against usage of main template namespace (in whatever form) for 15926.org export, as long as templates there are not verified and in some form approved by MMT SIG.

Please consider return to templates-test/templates#


Mon Nov 12, 2012 11:07 am
Profile WWW

Joined: Mon Feb 27, 2012 11:01 pm
Posts: 282
Location: Moscow, Russia
Why p7tpl:valFOLCode ?

Why not p7tm:valFOLCode ?


Mon Nov 12, 2012 11:19 am
Profile WWW

Joined: Sun Jan 22, 2012 10:02 pm
Posts: 283
Because it has nothing to do with p7tm :)


Mon Nov 12, 2012 12:38 pm
Profile

Joined: Mon Feb 27, 2012 11:01 pm
Posts: 282
Location: Moscow, Russia
Hans,

You probable mean that valFOLCode is a universal role belonging to all templates - as its name and namespace suggest indeed?

Then it has a proper place among n-ary relationship participants. These are listed in <owl:Class rdf:about="IdentificationOfClass"> as an intersection of restrictions, not in <p7tm:TemplateDescription rdf:ID="TemplateDescription_of_IdentificationOfClass">.

In template description <p7tm:TemplateDescription rdf:ID="TemplateDescription_of_IdentificationOfClass"> we have just "attributes", all defined by p7tm metamodel.

Either it is indeed p7tpl:valFOLCode and should be somehow placed in n-ary relationship without disturbing the structure of existing OWL definitions (I'm not sure it's possible). Or it is an attribute and should have a name p7tm:valFOLCode.


Mon Nov 12, 2012 1:00 pm
Profile WWW

Joined: Sun Jan 22, 2012 10:02 pm
Posts: 283
You are right.
p7tpl imports p7tm, and not the other way around,
Let's put it (valFOLCode) in p7tm.


Mon Nov 12, 2012 3:54 pm
Profile
Display posts from previous:  Sort by  
Reply to topic   [ 28 posts ]  Go to page 1, 2, 3  Next

Who is online

Users browsing this forum: No registered users and 1 guest


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
cron
eXTReMe Tracker
Powered by phpBB® Forum Software © phpBB Group
Designed by ST Software.